Blogs

SAP ES Explorer vs. SAP Connector for Microsoft .NET Rima Rudnik-Sirich   Business Card Company: SAP Posted on May. 25, 2009 01:08 AM in Interoperability .NET, Service-Oriented Architecture

Subscribe Print Permalink Share

In the end of 2008, SAP has released ES Explorer for .NET tool. This tool is a successor of SAP connector for Microsoft .NET (NCo) as the connectivity tool between SAP back-end systems and the Microsoft. NET platform.

 

What does ES Explorer for .NET do ?
1. It succeeds SAP Connector 2.0 for .NET
2. It enables connectivity between the Microsoft .NET platform and SAP back-end systems based on SOA architecture
3. It is a development tool for Microsoft Visual Studio 2005 and 2008

 

What doesn't ES Explorer for .NET do ?
1. It doesn't replace SAP Connector 2.0 for .NET
2. It doesn't enable connectivity between the Microsoft .NET platform and SAP back-end systems based on SAP Remote Function Calls (RFC)
3. It is not a migration tool from Microsoft Visual Studio 2003 to Microsoft Visual Studio 2005 and 2008
 

Which design time connectivity solutions do the Microsoft Visual Studio 2005 and 2008 developers have ? 
1. Developers that are interested to continue to work with SAP back-end systems based on RFC can use a solution based on backward compatability and described in the following paper
2. Developers that are ready to migrate their SAP back-end to SOA architecture can take advantage of ES Explorer for .NET

Rima Rudnik-Sirich   is a software engineer in SAP NetWeaver R&D organization

Comment on this weblog

Showing messages 1 through 7 of 7.
Titles Only	Main Topics	Oldest First

• SAP ES vs. VS WS
  2010-03-11 08:16:22 Peter VanVleet Business Card [Reply]
  
  Does the SAP ES perform any additional functions than if we use the Visual Studio (VS) Web Services feature directed at a specific WS on an SAP box? I realize ES handles the UDDI-level identification of a WS, but if we aren't using UDDI and are just targeting the consumption of a WAS-hosted WS, does ES provide anything else functionally in VS than just using the VS provided 'Add Web Reference...'? For example, are the proxies generated the same? Is the VS VB coding done any differently in terms of interacting w/the proxies and/or data structures? I'm just trying to understand what the value-add is of the SAP ES vs. what VS already provides.

  
  Thanks

  • SAP ES vs. VS WS
    2010-03-17 05:37:44 Rima Rudnik-Sirich  Business Card [Reply]
    
    Hello Peter,

    
    ES Explorer for .NET implementation of "Add SAP Enterprise Service" is based on Visual Studio "Add Web Service" feature. However, if you would try to use "Add Web Service" feature directly it would not work. ES Explorer for .NET performs an automatic conversion of WSDL from SAP (Document style) to Microsoft (RPC style) standard.

    
    Hope it answers your question.
    Best Regards,
    Rima

• SOA Architecture vs RFC
  2009-07-08 14:29:41 Mario Morales Business Card [Reply]
  
  How can I tell if my back end systems supports SOA? Our backend system is ECC 6.0. Does SOA involve configuring ECC 6.0? or is it natively supported with little or no effort on configuration.
  • SOA Architecture vs RFC
    2009-07-14 01:33:17 Rima Rudnik-Sirich  Business Card [Reply]
    
    Hello Mario,

    
    In order to work with ES Explorer for .NET you need:
    1. a Services Registry shipped with SAP Netweaver CE 7.1 or SAP Netweaver PI 7.1
    2. expose BAPIs as Webservices and publish them to Services Registry

    
    Best Regards,
    Rima

    • SOA Architecture vs RFC
      2009-07-14 07:29:31 Mario Morales Business Card [Reply]
      
      Thanks! I'm clear now.

• Support for WCF publishing/NCo work around
  2009-06-17 12:37:18 Fakher Halim Business Card [Reply]
  
  Rima,
  1. Can we publish WCF service with ES Explorer 1.1?
  2. Does SAP connector for Microsoft .NET (NCo) now support VS 2005 and VS 2008, or we are still stuck with first designing in VS2003, and then doing the work around, as cited in the paper you referred?
  
  • Support for WCF publishing/NCo work around
    2009-06-18 00:55:59 Rima Rudnik-Sirich  Business Card [Reply]
    
    Hello Halim,

    
    1. Unfortunately, ES Explorer for .NET doesn't support publishing WCF service.
    2. SAP Connector for .NET doesn't support Visual Studio 2005 and 2008. The way to use it in Visual Studio 2005 and 2008 is to do a workaround desribed in the referred paper.

    
    Regards,
    Rima