Skip to Content

SAP has developed a new interoperability tool, the SAP Enterprise Services Explorer for Microsoft .NET. This new tool extends the reach of SAP enterprise services by making them available for the .NET developer community. It is integrated with the Services Registry to allow easy access to SAP enterprise services from Microsoft Visual Studio.

 

The Services Registry, which is shipped as part of SAP NetWeaver Process Integration 7.1 and SAP NetWeaver Composition Environment 7.1, is a UDDI v3-compliant registry for enterprise services. It is located centrally within an SOA landscape and contains information about services provided in that landscape, with references to the service-relevant WSDL metadata and to the locations of the service endpoints. The registered services are classified using semantic-rich classification systems to enable browsing of services by semantic category. Using an integrated set of tools for accessing the Services Registry, developers can easily find services to build consumer applications. To make all enterprise services available centrally, the services can be published from ABAP or Java back-ends, from the Enterprise Services Repository or the PI Integration Directory. On the consumer side, the Services Registry can be accessed directly from Web Dynpro, Visual Composer and BPM. The new SAP Enterprise Services Explorer for Microsoft .Net complements these query and publish options.

 

Technically, the SAP Enterprise Services Explorer is an add-in to Visual Studio, which means it can be easily installed to access any version of the Services Registry. It is a design-time tool that supports all types of .NET applications and languages. You can use this tool primarily to discover SAP enterprise services and import them into MS Visual Studio as well as publish .NET-based services to the Services Registry. This supports interoperability at every phase of the service development cycle, from service provisioning to service consumption across multiple platforms.

 

A sneak preview of SAP Enterprise Services Explorer for Microsoft .NET is available here.

After installation you can access to the full documentation included in the Visual Studio help.

The full version will be available with SAP Enhancement Package 1 of SAP NetWeaver Composition Environment 7.1. The new tool can be used with any version of the Services Registry – both with Process Integration and Composition Environment.

For a detailed description of functions and features click here.

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Bernd Eckenfels
    Is it also useable with other UDDI Registries?

    I am still not sure why SAP has its own categorisation service. Isnt it possible to have any number of hierachies within UDDI attached to objects?

    Greetings
    Bernd

    (0) 
    1. Susanne Rothaug Post author
      Hello Bernd,

      The SAP Enterprise Services Explorer doesn’t work on UDDI level directly. Instead it works with the Services Registry-specific Web services, which means that it cannot be used on other UDDI-based registries.
      As to the SAP categorisation service: the UDDI taxonomies are not sufficient for semantically classifying enterprise services and creating new company-specific classifications.

      Best regards,
      Susanne

      (0) 
  2. Bernd Eckenfels
    Is it also useable with other UDDI Registries?

    I am still not sure why SAP has its own categorisation service. Isnt it possible to have any number of hierachies within UDDI attached to objects?

    Greetings
    Bernd

    (0) 
    1. Susanne Rothaug Post author
      Hi Mario,

      The ES Explorer requires a 7.1 Enhancement Package 1 Services Registry. This could be the Services Registry of SAP NetWeaver Process Integration 7.1 EHP1, or the Services Registry of SAP NetWeaver Composition Environment 7.1 EHP1.
      The services inside the Services Registry, i.e. those to be discovered and consumed with MS Visual Studio, can also come from a 7.0 system.

      Best regards,
      Susanne

      (0) 

Leave a Reply