Setting Up the Connection to the Services Registry 
To be able to publish services, the provider system must be connected to a Services Registry. You only need to set up the connection to a Services Registry 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 consumer.
From the SOA Manager main screen, go to the Technical Administration tab.
Choose Global System Settings.
Go to the Services Registry tab.
Choose New to create a new connection.
NoteTo change the settings of an existing connection, choose Edit. To delete an existing connection, Choose Delete.
End of the note.Specify a Services Registry.
The Services Registry name has to be written as a single word, for example, ERP_REGISTRY.
To make this the primary Services Registry, select Primary.
Each time a provider is configured, its endpoints are automatically published to the primary Services Registry.
Choose Next.
Choose a proxy class to use for communication with the Services Registry.
You can choose either of the following:
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.
The service path is determined automatically based on the proxy class name.
Specify a logical port.
Use uppercase characters for the logical port name.
NoteMake a note of the logical port that you create, so that you can later assign it to the Services Registry.
End of the note.Specify the Services Registry server and the server port number.
For example, services.reg.example.corp.
NoteThe default server port is 80.
End of the note.Specify a user with valid publication authorization and a password for the Services Registry system.
Choose Next.
Specify the Reverse proxy name.
Using reverse proxies is optional.
Select Schedule Publication.
To publish all the Web services, select Yes.
To publish only selected Web services, select No.
To build a list of services, go to the Service Administration tab and choose Publication Rules.
If Schedule publication is set to Yes, specify a publication date, a publication time, and the publication job frequency. If these values are not specified, the system uses the default values.
Choose Finish.
A logical port is now created for the specified proxy, and the system is prepared to be able to connect to a services registry. You can use Ping to test this connection at a later time.
NoteOn the Java side, some additional configuration steps need to be made where service registry is installed and available. More information: Configuring the Services Registry
End of the note.
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
Below is an example of a documentation link:
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 |