微软和SAP
多年来，我一直使用旧的“SAP DCOM 连接器”在基于 Microsoft 的应用程序和 SAP 之间进行通信。不幸的是，SAP 多年来不再支持这种古老但良好且高性能的技术。因此我想要并且必须迁移到另一种更新的技术。
首先是“SAP Connector for .NET 2.0”。乍一看，这似乎是一个很好的替代品。但此连接器只能与 .NET 1.1 一起使用（也有与 .NET 2.0 一起使用的解决方法），并且将来不会进一步开发。为你的SAP感到羞耻！ SAP表示，未来我们应该使用Visual Studio的“Enterprise Services Explorer”。但该技术仅适用于ECC6.0，不适用于4.6C。这就是重点。我需要一种现代技术，可用于 4.6C 和 ECC6.0！
于是我做了一些调查，发现了“Theobald-Software”的产品“ERPConnect”。它看起来真的很不错，而且他们有一个又好又便宜的许可模式。该产品的第一个问题是，不允许向客户提供基于ERPConnect的应用程序的源代码。这很奇怪，因为客户通常也会购买应用程序源的权利。第二个问题是，该产品不是来自SAP，也没有经过SAP 认证。许多客户不想要第三方的产品。
所以现在我的问题是：是否有进一步的可能性将 Microsoft World 与 SAP World 连接起来？有人知道上述方法的替代方法吗？特别是我需要使用 RFC 的替代方案。
For many years I have used the old "SAP DCOM Connector" to communicate between Microsoft based applications and SAP. Unfortunately this old but good and performant technology is no longer supported by SAP since years. Therefore I want and must migrate to another newer technology.
First there is the "SAP Connector for .NET 2.0". At first glance it seems to be a good replacement. But this connector can only used with .NET 1.1 (with a workaround also with .NET 2.0) and there is no further development in the future. Shame on you SAP !! SAP says, in the future we should use the "Enterprise Services Explorer" for Visual Studio. But this technology is only available for ECC6.0 and not for 4.6C. And that's the point. I need a modern technology, which is available for 4.6C and ECC6.0 !!
So I did some investigations and discovered the product "ERPConnect" from "Theobald-Software". It looks really nice and they have a good and cheap license model. The first problem with this product is, that it is not allowed to give the source code of applications, which are based on ERPConnect, to the customer. That's strange, because often customers also buy the rights for the application sources. The second problem is, that this product is not from SAP and is also not certified from SAP . Many customers don't want a product from a third party.
So now my question is: are there further possibilities to connect the Microsoft World with the SAP World and does somebody know alternatives to the above mentioned methods ? Especially I need alternatives for using RFCs.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（9）
好消息：
SAP 已发布 SAP .NET Connector 3.0 版本。它将支持当前的 Windows 版本（Windows XP 32 位、Windows 2003 32/64 位 (x64)、Windows Vista 32/64 位 (x64)、Windows 2008 64 位 (x64) 和更高版本的 Windows 7）以及最新版本-日期 Microsoft .NET 运行时版本（2.0、3.0 和 3.5）。
请参阅http://wiki.sdn.sap.com/wiki/显示/ABAPConn/ABAP+Connectivity+Home
和 http://service.sap.com/connectors
Great News:
SAP has announced release 3.0 of the SAP .NET Connector. It will support current Windows releases (Windows XP 32 Bit, Windows 2003 32/64 Bit (x64), Windows Vista 32/64 Bit (x64), Windows 2008 64 Bit (x64) and later Windows 7) as well as up-to-date Microsoft .NET Runtime versions (2.0, 3.0 and 3.5).
See http://wiki.sdn.sap.com/wiki/display/ABAPConn/ABAP+Connectivity+Home
and http://service.sap.com/connectors
我之前有使用 SAP .NET Connector 开发基于 .NET 2.0 的应用程序的经验。问题是，我正在调用 BAPI 函数来代替 RFC，我不确定如果这对你有影响的话就足够了，但 SAP .NET 连接器对我来说就像一个魅力。我正在从生产服务器访问一些内部数据，并使用 ASP.NET 授权用户。
简而言之，SAP .NET 连接器不是一个太糟糕的选择。
I have a prior experience to develop .NET 2.0 based applications with SAP .NET Connector. The thing is, I was calling a BAPI function in place of RFC, I'm not sure enough if that makes difference for you but SAP .NET connector worked like a charm for me. I was accessing some internal data from a production server and implemented role based security using ASP.NET to authorize the users.
In short, SAP .NET connector is not a too bad choice.
几年前我参与的一个项目也使用了 SAP Connector。然而，为了系统互操作性，我现在会选择 WCF。
我知道有时这可能很困难，但这是最好的方法。
I was working on a project couple of years ago that also used the SAP Connector. However, for system interoperability i would go for WCF these days.
I know this can be hard sometimes, but thats the best way tbh.
Connector 通过 RFC，为您提供大量现成的内置 BAPI 和功能模块。这意味着您只需在服务器端做很少的工作即可实现您的目标，只要您有适合您需求的功能，您也可以自己做。话虽如此，越来越多的人转向 Web 服务，这需要在服务器端进行更多工作（将功能模块转换为 Web 服务），但更可重用，HTTP 友好等等......
选择你的毒药;-)
Connector goes through RFC which gives you tons of ready built-in BAPIs and function modules. That means you need little work on server side for your goals as long as you have a function suitable for your needs, also you can do of your own. Said this, more and more people are movig to web services, which requires more work on server side ( convert function modules to web services ) but are more reusable, HTTP friendly and so...
Pick your poison ;-)
您最大的问题是连接到 SAP 4.6C。 SAP 4.6C 的扩展维护已于 2009 年底到期，这就是 SAP 不再继续开发 SAP Connector for .NET 2.0 的原因。
从 Basis Release 2004 开始，您可以使用事务 SOAMANAGER 将任何支持 RFC 的功能模块公开为 Web 服务。
您可以继续使用 SAP Connector for SAP 4.6C。或者，如果您有 PI (XI) 系统，您可以通过 PI 构建一个接口，并将其作为 Web 服务公开给 .NET 世界。
Your single biggest problem is going to be connecting to SAP 4.6C. Extended maintenance for SAP 4.6C has expired at the end of 2009, which is why SAP is not continuing development of the SAP Connector for .NET 2.0
As of Basis Release 2004s you can expose any RFC-enabled Function Module as a webservice using transaction SOAMANAGER.
You could continue to use the SAP Connector for SAP 4.6C. Alternatively if you have a PI (XI) system you could build an interface via PI and expose that as a webservice to the .NET world.
我知道一个叫做 Duet 的产品，这个产品似乎是 SAP .NET 连接器开发中止的根源。还可以将 excel 2007 与 SAPGUI 中提供的 SAP ocx 组件一起使用。
I know about a product called Duet, this product seemed to originate the discontinuation of SAP .NET connector development. It is also possible to use excel 2007 with SAP ocx components that are available in the SAPGUI.
还有另一个产品，看起来很有趣：Sitrion Service Studio
http://www.sitrion.com/products/ServiceStudio/fordevelopers.aspx
也许这是 ErpConnect 的一个很好的替代方案。 Sitrion 已获得 SAP 认证。但我不知道该产品的许可费用。
There is another product, which looks interesting: Sitrion Service Studio
http://www.sitrion.com/products/ServiceStudio/fordevelopers.aspx
Meybe this is a good alternative for ErpConnect. Sitrion is SAP certified. But I don't know the licence costs for there product.
如果您的 SAP 系统的基础版本为 6.40 或更高版本，您可以在 SAP 系统中创建 Web 服务并直接从移动应用程序调用它们，而无需 .NET 连接器。
If your SAP System's basis release is 6.40 or above, you can create web services in SAP system and call them directly from Mobile apps without a .NET connector need.
有没有人考虑过 Biztalk Adapter 服务包，它支持版本 4.6c，有每个处理器的许可证，您可以将 RFC 公开为服务 (WCF) 并在任何应用程序中使用它。
Has any one considered Biztalk Adapter service pack , it supports version 4.6c , there is a per processor license , you can expose RFC's as Service (WCF) and use it in any application.