Page tree
Skip to end of metadata
Go to start of metadata



How to Set up a Connection and Publication to the Services Registry

This article explains how to set up a connection to a Services Registry and publish Web services there.


The Services Registry provider interface is configured as described in How to set up ABAP Services Registry.

You need the following role to be able to set up a connection and publication to Services Registry:


More information: SAP Note 1318883 (Introduction of new authorizations in Web Service)


Perform the following steps:

1. Start SOA Manager.  

Use the transaction code SOAMANAGER .

SOA Manager is a WebDynpro ABAP application. For this reason, its ICF node needs to be active. You can use transaction SICF to check that the ICF node for SOA Manager (/sap/bc/webdynpro/sap/appl_soap_management) is active.
More information: SAP Note 1124553

2. From the main screen of SOA Manager, go to the Services Registry tab.

3. Choose Services Registry Consumer Settings.

4. Go to the Services Registry connections tab and Choose Create to establish a new connection to Services Registry .

Wizard will start to ask you for the input.

5. Specify a Services Registry name and select the Primary flag if this is the main Services Registry in your Landscape. Choose Next.

Services Registry name SR_CENTRAL is taken here as an example. Services Registry name has is an example of a name and may describe the location or purpose.

6. Configure the following fields and choose Finish. A new connection will be generated with the help of specified fields.

* Choose the consumer proxy CO_SERVICES_REGISTRY_FLAT_SI for the field consumer proxy.
* Specify the logical port (e.g. LP_SR_CENTRAL) to be generated.

* Specify the server and port of the Services Registry system.

* Specify the path where Services Registry APIs are deployed.

Format for Java based Services Registry: '/ServicesRegistryFlatSiService/ServicesRegistryFlatSiPort'.

Format for ABAP based Services Registry(SR) assuming SR Provider Interface is configured with simplified Web service configuration Tool:'/sap/bc/srt/scs/sap/servicesregistryflatsi?sap-client=<Client>'. Here <Client> is the ABAP Client number of SR System.


* Specify a valid user and password available in the Services Registry system responsible for the publication.

* Specify a reverse proxy in case the Services Registry lies outside your system landscape and Web service consumers are accessing Web services through reverse proxy.

If the Services Registry lies on Java Stack, the above-mentioned user should have sufficient roles to be able to publish services as described in the documentation under

7. Already generated connection be be tested either by choosing Ping or by Update Cache 

Publication rule for this connection and an assignment needs to be created for this connection as described below.

Ping will fail in case of older releases of Java Services Registry even though the connection might be in healthy state. Update Cache should always be successful.

8. Choose Create on the publication rule tab on the Services Registry Consumer Settings UI. Specify a Rule name along with description. 

9. Specify the objects which need to be published in the Services Registry. Web Service internal names or classifications can be defined here. Choose Save to persist the publication rule.

As an example, we have a rule (SR_RULE) where all Web Services with their name starting with 'Z*' and classified with the classification 'LifecycleStatus' = 'Released'  is part of one rule.

Multiple publication rules can be maintained within this UI. Patterns can be used for the object names or classifications.

10. Choose the _Assignments tab to activate an assignment between publication rule and a Services Registry{_} .

Assignments are automatically generated with inactive status.  

Active assignments will decide the content to be publihsed in the Services Registry.

11. Choose Synchronize to start the publication.

12. Publication can be triggered in following ways.

* It can be immediate, delayed or periodic.
* Force Publication flag will republish all the Web services and also remove invalid Web service and bindings in the Services Registry.
* Publication can also be started only for specific Services Registry by mentioned it's name 

Background job 'SRT_SR_PUBLICATION_SYNC' will be started and will process all the active publication rules associated to Services Registries.


You have now setup a connection to Services Registry and started the publication based on publications rules.

More Information

SAP Note 1319742  - Services Registry Publication

  • No labels