Need to integrate SAP with .NET applications. Is .NET Connector the best choice? What about NetWeaver? Simply looking to push data to and pull data from SAP.
需要将SAP与.NET应用程序集成。 .NET Connector是最佳选择吗?那么NetWeaver呢?只需将数据推送到SAP并从中提取数据。
8 个解决方案
#1
4
I haven't used the NetWeaver objects, so I can't say much about that, but I can say that the .Net connector does a pretty good job of proxying the SAP BAPIs for use in .Net. A few additional comments:
我没有使用NetWeaver对象,所以我不能说太多,但我可以说.Net连接器在代理SAP BAPI以便在.Net中使用时做得非常好。一些额外的评论:
- Drawback - AFAIK, you're stuck with developing your proxies in VS2003
- Drawback - the documentation of the BAPIs is pretty slim. I spend a lot (I mean a lot) of time in SE37 inside SAP looking at the RFC documentation and stepping through the functions
- Positive - it took me a while to realize that you could rename and remove parameters and rename methods in VS2003 before building the proxy
- Drawback - if you do the above-mentioned renaming you need to redo it every time you repopulate the RFC from the SAP server (like if your SAP developer makes changes to a BAPI)
缺点 - AFAIK,你坚持在VS2003中开发代理
缺点 - BAPI的文档非常简洁。我在SE37里面花了很多时间(我的意思是很多)来查看RFC文档并逐步完成这些功能
肯定 - 我花了一些时间才意识到你可以在构建代理之前重命名和删除VS2003中的参数并重命名方法
缺点 - 如果您执行上述重命名,则每次从SAP服务器重新填充RFC时都需要重做(例如,如果SAP开发人员对BAPI进行了更改)
Overall, complicated functions are difficult with the .Net Connector (I just spent 3 weeks getting customer creation and modification working), but simple functions are pretty transparent, and if you have an ABAP developer available to you on the SAP side and can develop custom BAPIs it works really well.
总的来说,.Net连接器很难实现复杂的功能(我只花了3周的时间让客户创建和修改工作),但简单的功能是非常透明的,如果您在SAP端有一个ABAP开发人员可以开发自定义BAPI它运作得很好。
#2
2
SAP .Net Connector is okay but it only supports Visual Studio 2003, but they haven't updated it in a while.
SAP .Net Connector是可以的,但它只支持Visual Studio 2003,但它们暂时没有更新。
There is another product called SAP Explorer and Proxy Generator that I've used to connect to SAP from VS2005. It uses version 1.1 of the SAP .Net Connector to do all the dirty work, so I copied and pasted the contents of the SAP .Net Connector 2.0 folder into the SAP Explorer folder to get it to use the newer version of the proxy libraries (this added support for case-sensitive passwords). I haven't tried it in VS2008 yet, but I suspect it will still work.
还有另一个名为SAP Explorer和Proxy Generator的产品,我用它从VS2005连接到SAP。它使用SAP .Net Connector 1.1版来完成所有脏工作,因此我将SAP .Net Connector 2.0文件夹的内容复制并粘贴到SAP Explorer文件夹中,以使其使用较新版本的代理库(这增加了对区分大小写的密码的支持)。我还没有在VS2008中尝试过,但我怀疑它仍然有用。
SAP Explorer is certainly a nice replacement for the SAP product, but it doesn't look like it's been updated recently.
SAP Explorer当然是SAP产品的一个很好的替代品,但它看起来并不像最近更新过的那样。
#3
2
I understand that Web Services is the way to go to achieve Netweaver / .Net integration. This is why the .Net Connector has not been updated from VS2003 days.
我知道Web Services是实现Netweaver / .Net集成的方法。这就是为什么.Net Connector没有从VS2003天更新的原因。
#4
1
There's a new version available from the guys at Aconcagua IT, with better prices and more flexible options than other competitors.
Aconcagua IT公司提供新版本,价格更优惠,选项比其他竞争对手更灵活。
Visual Studio 2008 and Visual Studio 2005 versions available: http://www.aconcaguait.com/explorerproxygen2008.php or
Visual Studio 2008和Visual Studio 2005版本可用:http://www.aconcaguait.com/explorerproxygen2008.php或
VS2008 version includes support for the latest librfc32.dll (password lenght, case-sensitive, etc.)
VS2008版本包括对最新的librfc32.dll(密码长度,区分大小写等)的支持
Worth a look.
值得一看。
#5
1
As written above, SAP proposes to go the SOA road, which means to use the SOAP tool chain instead of the RFC tool chain (.Net RFC connector, ...).
如上所述,SAP建议走SOA路,这意味着使用SOAP工具链而不是RFC工具链(.Net RFC连接器......)。
For .Net that means to use the WCF functionality and connect it with the SAP backend, hence using SOAP on both sides: find your business needs in one of the many SOA services delivered by SAP (ES Wiki on SDN) or create a service of your own and create the client side functionality based on the proxy generated from the services WSDL file via WCF's svcutil.
对于.Net而言,这意味着使用WCF功能并将其与SAP后端连接,因此在两端都使用SOAP:在SAP提供的众多SOA服务(SDN中的ES Wiki)中找到您的业务需求,或者创建服务您自己的,并根据通过WCF的svcutil从服务WSDL文件生成的代理创建客户端功能。
As a bonus, doing this is not dependent from any Visual Studio version, csc and svcutil on the command line is just enough.
作为奖励,这样做不依赖于任何Visual Studio版本,命令行上的csc和svcutil就足够了。
#6
1
http://tools.rafaelc.net/default.aspx?id=72
I have used this tool to integrate SAP (Generate BAPI and CBO proxies) with the B2B process that I developed for one of world's top blue chip consumer electronics company. His efforts are well appreciated and it is completely FREE.
我使用这个工具将SAP(生成BAPI和CBO代理)与我为世界*蓝筹消费电子公司之一开发的B2B流程集成在一起。他的努力得到了很好的赞赏,而且完全免费。
#8
0
We have bought "SAP Explorer and Proxy Generator for VS 2008" and we have been disappointed, because this tool has not worked well. So far, we still await a solution to the problems (from Aconcagua). Unfortunately we had to re-generate proxies in VS2003 with the free version of the SAP Connector, and then use them in VS2008.
我们已经购买了“用于VS 2008的SAP Explorer和代理生成器”,我们很失望,因为这个工具效果不佳。到目前为止,我们仍在等待问题的解决方案(来自阿空加瓜)。不幸的是,我们不得不在VS2003中使用免费版本的SAP Connector重新生成代理,然后在VS2008中使用它们。
#1
4
I haven't used the NetWeaver objects, so I can't say much about that, but I can say that the .Net connector does a pretty good job of proxying the SAP BAPIs for use in .Net. A few additional comments:
我没有使用NetWeaver对象,所以我不能说太多,但我可以说.Net连接器在代理SAP BAPI以便在.Net中使用时做得非常好。一些额外的评论:
- Drawback - AFAIK, you're stuck with developing your proxies in VS2003
- Drawback - the documentation of the BAPIs is pretty slim. I spend a lot (I mean a lot) of time in SE37 inside SAP looking at the RFC documentation and stepping through the functions
- Positive - it took me a while to realize that you could rename and remove parameters and rename methods in VS2003 before building the proxy
- Drawback - if you do the above-mentioned renaming you need to redo it every time you repopulate the RFC from the SAP server (like if your SAP developer makes changes to a BAPI)
缺点 - AFAIK,你坚持在VS2003中开发代理
缺点 - BAPI的文档非常简洁。我在SE37里面花了很多时间(我的意思是很多)来查看RFC文档并逐步完成这些功能
肯定 - 我花了一些时间才意识到你可以在构建代理之前重命名和删除VS2003中的参数并重命名方法
缺点 - 如果您执行上述重命名,则每次从SAP服务器重新填充RFC时都需要重做(例如,如果SAP开发人员对BAPI进行了更改)
Overall, complicated functions are difficult with the .Net Connector (I just spent 3 weeks getting customer creation and modification working), but simple functions are pretty transparent, and if you have an ABAP developer available to you on the SAP side and can develop custom BAPIs it works really well.
总的来说,.Net连接器很难实现复杂的功能(我只花了3周的时间让客户创建和修改工作),但简单的功能是非常透明的,如果您在SAP端有一个ABAP开发人员可以开发自定义BAPI它运作得很好。
#2
2
SAP .Net Connector is okay but it only supports Visual Studio 2003, but they haven't updated it in a while.
SAP .Net Connector是可以的,但它只支持Visual Studio 2003,但它们暂时没有更新。
There is another product called SAP Explorer and Proxy Generator that I've used to connect to SAP from VS2005. It uses version 1.1 of the SAP .Net Connector to do all the dirty work, so I copied and pasted the contents of the SAP .Net Connector 2.0 folder into the SAP Explorer folder to get it to use the newer version of the proxy libraries (this added support for case-sensitive passwords). I haven't tried it in VS2008 yet, but I suspect it will still work.
还有另一个名为SAP Explorer和Proxy Generator的产品,我用它从VS2005连接到SAP。它使用SAP .Net Connector 1.1版来完成所有脏工作,因此我将SAP .Net Connector 2.0文件夹的内容复制并粘贴到SAP Explorer文件夹中,以使其使用较新版本的代理库(这增加了对区分大小写的密码的支持)。我还没有在VS2008中尝试过,但我怀疑它仍然有用。
SAP Explorer is certainly a nice replacement for the SAP product, but it doesn't look like it's been updated recently.
SAP Explorer当然是SAP产品的一个很好的替代品,但它看起来并不像最近更新过的那样。
#3
2
I understand that Web Services is the way to go to achieve Netweaver / .Net integration. This is why the .Net Connector has not been updated from VS2003 days.
我知道Web Services是实现Netweaver / .Net集成的方法。这就是为什么.Net Connector没有从VS2003天更新的原因。
#4
1
There's a new version available from the guys at Aconcagua IT, with better prices and more flexible options than other competitors.
Aconcagua IT公司提供新版本,价格更优惠,选项比其他竞争对手更灵活。
Visual Studio 2008 and Visual Studio 2005 versions available: http://www.aconcaguait.com/explorerproxygen2008.php or
Visual Studio 2008和Visual Studio 2005版本可用:http://www.aconcaguait.com/explorerproxygen2008.php或
VS2008 version includes support for the latest librfc32.dll (password lenght, case-sensitive, etc.)
VS2008版本包括对最新的librfc32.dll(密码长度,区分大小写等)的支持
Worth a look.
值得一看。
#5
1
As written above, SAP proposes to go the SOA road, which means to use the SOAP tool chain instead of the RFC tool chain (.Net RFC connector, ...).
如上所述,SAP建议走SOA路,这意味着使用SOAP工具链而不是RFC工具链(.Net RFC连接器......)。
For .Net that means to use the WCF functionality and connect it with the SAP backend, hence using SOAP on both sides: find your business needs in one of the many SOA services delivered by SAP (ES Wiki on SDN) or create a service of your own and create the client side functionality based on the proxy generated from the services WSDL file via WCF's svcutil.
对于.Net而言,这意味着使用WCF功能并将其与SAP后端连接,因此在两端都使用SOAP:在SAP提供的众多SOA服务(SDN中的ES Wiki)中找到您的业务需求,或者创建服务您自己的,并根据通过WCF的svcutil从服务WSDL文件生成的代理创建客户端功能。
As a bonus, doing this is not dependent from any Visual Studio version, csc and svcutil on the command line is just enough.
作为奖励,这样做不依赖于任何Visual Studio版本,命令行上的csc和svcutil就足够了。
#6
1
http://tools.rafaelc.net/default.aspx?id=72
I have used this tool to integrate SAP (Generate BAPI and CBO proxies) with the B2B process that I developed for one of world's top blue chip consumer electronics company. His efforts are well appreciated and it is completely FREE.
我使用这个工具将SAP(生成BAPI和CBO代理)与我为世界*蓝筹消费电子公司之一开发的B2B流程集成在一起。他的努力得到了很好的赞赏,而且完全免费。
#7
#8
0
We have bought "SAP Explorer and Proxy Generator for VS 2008" and we have been disappointed, because this tool has not worked well. So far, we still await a solution to the problems (from Aconcagua). Unfortunately we had to re-generate proxies in VS2003 with the free version of the SAP Connector, and then use them in VS2008.
我们已经购买了“用于VS 2008的SAP Explorer和代理生成器”,我们很失望,因为这个工具效果不佳。到目前为止,我们仍在等待问题的解决方案(来自阿空加瓜)。不幸的是,我们不得不在VS2003中使用免费版本的SAP Connector重新生成代理,然后在VS2008中使用它们。