Skip to Content

Prototype for MS-Office Add-In Integrating SAP Web-Services Part II – Working with the Services Registry API

h2. Introduction   This is the second part of my blog on experiences with the integration of web services into MS Word  (Prototype for MS-Office Add-In Integrating SAP Web-Services) via the SAP Services Registry. This part deals mostly with the usage of the Services Registry API (“SR API”), which allows a developer to determine web service properties dynamically at runtime.  h2. What is the Services Registry?  “SAP Services Registry (SR) is a part of SAP NetWeaver Composition Environment 7.1 (CE), a UDDI-compliant registry of service definitions available in the repository. It provides API for search and discovery of services, as well as for publishing custom services in the registry, and supports the Web Service Definition Language (WSDL) standard.” (see: {code:html}Anne Tarnoruder: “Introducing SAP Enterprise Services Explorer for Microsoft .NET”{code})  h2. Determining the URL to the Services Registry API The first challenge when working with the SR API is how to determine the URL to the API. The SR API is called “ServicesRegistrySi” and needs to be configured in the SR itself. To determine the URL to the service you can either search for this service in the SR itself or you have to contact your system administrator to tell you the correct settings.  In the SAP Services Registry, the API cannot be found via searching the SR, but is publicly available in the SDN on the page “{code:html}ES Workplace Configuration{code}”. The settings for theES Workplace Services Registry are:  URL to API:  ( user name: sruser 0.2. password: eswork123 If you are working with a customer SAP Services Registry, start it and search for “ServicesRegistrySi” in the SR itself or the SAP NetWeaver WS Navigator. You will get a result table with something like this (example from SAP internal system):Search results in SR for SR API
Be the first to leave a comment
You must be Logged on to comment or reply to a post.