Show TOC

Procedure documentationSetting Up the Connection to the Services Registry Locate this document in the navigation structure

 

To be able to publish services, the provider system must be connected to Services Registry. You only need to set up this connection once for each client in a system.

Procedure

To create a connection between the provider back-end system and the Services Registry, perform the following steps for each client.

  1. From the SOA Manager main screen, go to the Application and Scenario Communication tab.

  2. Choose Single Service Administration.

  3. Locate the consumer proxy

    CO_SERVICES_REGISTRY_FLAT_SI

    The recommended consumer proxy to configure the connection to the Services Registry. CO_SERVICES_REGISTRY_FLAT_SI is the interface between the ABAP back-end system and the Services Registry system, and contains the appropriate authentication information.

    CO_ESREGISTRY_WSSI

    This consumer proxy was used in previous versions.

  4. Select the proxy and choose Apply selection.

    Information about the proxy definition is displayed.

  5. Go to the Configurations tab.

  6. Choose Create Logical Port.

    A dialog box is displayed.

    Note Note

    Make a note of the logical port that you create, so that you can later assign it to the Services Registry.

    End of the note.

  7. Specify the following information:

    • A unique logical port name (IN UPPERCASE).

    • Select Manual Configuration.

  8. Choose Apply Settings.

    An overview of the configuration information is displayed for the new logical port.

  9. Go to the Consumer Security tab and specify a user and password.

  10. Go to the Transport Settings tab

  11. Specify the URL access path.

    You may need to request the URL from your Services Registry administrator.

    Note Note

    If you created the logical port for the consumer proxy CO_SERVICES_REGISTRY_FLAT_SI, use the access path /ServicesRegistryFlatSiService/ServicesRegistryFlatSiPort.

    If a logical port was created for the consumer proxy CO_ESREGISTRY_WSSI, use the access path /ESRegistryWS/BasicAuthConfig?style=document.

    End of the note.

  12. For Computer name of Access URL, specify the Services Registry server name.

    For example, services.reg.example.corp.

  13. If needed, specify a user and a password in the fields User Name for Proxy Access and Password of Proxy User.

  14. Save.

Customizing the Services Registry Settings

  1. From the SOA Manager main screen, go to the Technical Configuration tab.

  2. Choose System Global Settings.

  3. Go to the Services Registry tab.

  4. Add the Services Registry.

    Choose Insert Row or Append Row, specify a meaningful name and specify version 1.1.

  5. Specify the proxy name and the logical port that you created earlier.

  6. Enter X in the Primary column.

    Each time a provider is configured, its endpoints are published implicitly to the primary Services Registry.

    Set Schedule Publication to NO or to YES and specify a date and a time. If regular publishing is active, services are published in accordance with the active publication rules. To define publication rules, choose   Application and Scenario Communication   Publication Rules  

  7. Go to the Reverse Proxy Settings tab.

    Choose Insert Row or Append Row, and specify the symbolic name of the reverse proxy to use for publishing.

    More information: Configuring Reverse Proxies

  8. Save.

    The connection to the Services Registry is now set up.

Publishing Service Documentation Links

When you publish a Web service, you can also include a documentation link. A documentation server path prefix must first be active in the provider system. To configure and activate a documentation server path prefix, use transaction WSDOCU_SERVER. Here, you can optionally specify a software component if there are multiple documentation servers configured for different software components.

When a documentation server path prefix has been configured and activated, a documentation URL is automatically set up for each service definition and published in the Services Registry when a Web service is published.

Example Example

A documentation link looks like this:

http://main.wdf.sap.corp:1080/socoview/get_bpp_docu.asp?SC-NAME=SAP_BASIS&SC-VERSION=711&TYPE=ifmoper&NAME=FlightSeatAvailabilityQuery_In&NAMESPACE=http://sap.com/xi/XI/Demo/Airline

The parameters used are as follows:

SC-NAME — Software component name

SC-VERSION — Software component version

TYPE — Object type

NAME — Name of object

NAMESPACE — Namespace of object

End of the example.

More Information

Configuring Reverse Proxies