Skip to Content
avatar image
Former Member

SAP .NET connector or Web Services to connect .NET application?

Copied over from ABAP, General

Hi Folks,

My first ever post on the forum, so please forgive me if I am going over very old ground for most of you.

For the last 7 years my company has maintained a series of interfaces between a .NET application and our SAP system using the SAP .NET Connector. Even though we have now moved to Visual Studio 2010 I still need to build our connection object - that makes RFC calls to a remote SAP client - in Visual Studio 2003.

Now, whilst this works well, I don't believe that it can be a sustainable solution.

I have looked at a number of sites on the subject and I have seen posts stating that it is recommended that .NET developers implement web services to connect to SAP.

On the other hand, I have noticed that there is a version 3 of the SAP .NET Connector.

My question is, therefore, which should we use?

Best Regards,

David Brower

Glasgow, Scotland

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Jul 05, 2011 at 01:13 PM

    I just wondered is it possible to create a SAP proxy in Visual Studio 2010 with the .NET Connector 3.0 just as it was possible in Visual Studio 2003?

    Edited by: David Brower on Jul 5, 2011 3:13 PM

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi David,

      Sorry for the delayed reply, the 'functionality' is still there but it works quite differently in NCo 3.0.

      In NCo 3.0 there is no differentiation between design-time & runtime so you won't need to generate proxies anymore. Dynamic calls are introduced with NCo 3.0 therby loose coupling the SAP backend & Visual Studio (inherently that also means removing the Visual Studio dependance).

      You should go through the documentation carefully (especially the overviews - it has major differences between the releases), there are some significant changes between NCo 2.0 and NCo 3.0:

      [https://service.sap.com/connectors]

      Regards, Trevor

  • avatar image
    Former Member
    Jul 01, 2011 at 08:17 AM

    Hi David,

    I would say that it depends mostly from the culture of your .NET developpers. If they know SAP technology, RFC is very reliable and has better performance than Web Services.

    SAP Web services are great when the team from the external system don't know SAP technology and don't want to learn the "complicated proprietary stuff".

    Regards,

    Olivier

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi David,

      This just re-iterates what I've said above.

      The statement you've highlighted below is in the context of SAP Enterprise Services, not RFC's. So SAP recommends using the Enterprise Service Explorer tool for .NET to SAP Webservice / Enterprise Service communication as a best practice. You would still need to manage your RFC historical communication & the Enterprise Service Explorer tool can't do that for you.

      Also, please note, the Enterprise Service Explorer tool is only a mechanism relevant for design-time activities. It gives you a view (or metadata if you like) of the Enterprise Services available on SAP for consumption. This would allow you to generate your .NET proxies using this metadata from an Eclipse based IDE (in this case NWDS). You would then call the webservice endpoint at runtime from .NET.

      The point I'm trying to make it that the ES Explorer tool is helpful at design-time for SAP webservices / Enterprise Services) while the SAP.NET Connector also works for runtime RFC communication. You can use them together for both webservice & RFC communication.

      Regards, Trevor

  • avatar image
    Former Member
    Jul 05, 2011 at 01:13 PM

    I just wondered is possible to create a SAP proxy in Visual Studio 2010 with the .NET Connector 3.0?

    Add comment
    10|10000 characters needed characters exceeded