ISV的可选SAP集成实践？-OptionalSAPintegrationpracticeforanISV?

We are a smaller ISV company that develop a product that often end up depending on SAP integration when installed in customer environments.

我们是一家规模较小的ISV公司，开发的产品在客户环境中安装时通常最终取决于SAP集成。

We're now looking for the optimal way of integration our product with SAP - in the most standard way possible. We need a solution that will work for most possible customer with least amount of work (some of the really don't have their own SAP resources).

我们现在正在寻找以最标准的方式将我们的产品与SAP集成的最佳方式。我们需要一个能够为大多数客户提供最少工作量的解决方案（其中一些实际上没有自己的SAP资源）。

We need to receive some basic information such as customers, addresses, stock items. We also need to send invoice information to SAP for further processing there.

我们需要接收一些基本信息，如客户，地址，库存物品。我们还需要将发票信息发送给SAP，以便在那里进一步处理。

After some reading here for example it looks like NetWeaver and PI is the best way to go. Doesn't that however require a lot of development on the clients PI side to expose and call the correct services? How can that be solved?

经过一些阅读后，例如NetWeaver和PI看起来是最好的方式。然而，这不是需要在客户PI侧进行大量开发来公开和调用正确的服务吗？怎么解决这个问题？

Another question is if it's normal for all SAP customer to even have NetWeaver? I need my solution to work for all our customer and some are kind of mid-sized SAP customers with smaller SAP installations.

另一个问题是，如果所有SAP客户都拥有NetWeaver是正常的吗？我需要我的解决方案为我们所有的客户工作，有些是具有较小SAP安装的中型SAP客户。

If PI isn't the way to go what are my options and what are the pro and cons?

如果PI不是我可以选择的方式，有什么利弊？

Update 2010-12-30 - requirements. Some requirements that we need to fulfill are:

更新2010-12-30 - 要求。我们需要满足的一些要求是：

• .NET based solution on our product side of the solution (for example WCF).
• 基于.NET的解决方案在我们解决方案的产品方面（例如WCF）。
• Not use an expensive integration platform like BizTalk etc. We need a standard solution based on for example AppFabric and WCF.
• 不使用像BizTalk等昂贵的集成平台。我们需要一个基于AppFabric和WCF的标准解决方案。
• Handle both batch updates (like customer batches etc) but also response/request like calls.
• 处理批量更新（如客户批次等）以及响应/请求等呼叫。

2 个解决方案