Maintaining UDDI Registries 

Use

You can publish released Web Services in UDDI Registries. These UDDI Registries must be defined in the SAP System.

Procedure

To define a UDDI Registry for publication of Web services from the SAP System:

...

       1.      Open the transaction SUDDIREG.

       2.      Choose Display  ® Change, followed by New Entries.

       3.      Enter the required data.

In the Version field, enter the supported version of the UDDI specification. This is currently version 2.0.

In the fields Inquire API Destination and Publish API Destination, enter the name of the destinations. They are maintained as HTTP Connections to External Servers in the transaction SM59. The destinations must reference the URLs of the Inquire and Publish APIs for the UDDI Registry.

Example:

SAP UDDI Test Registry (Web page: http://udditest.sap.com):

URL, Inquire API:  http://udditest.sap.com/ UDDI/api/inquiry/

URL, Publish-API:  https://udditest.sap.com/ UDDI/api/publish/

You must maintain two destinations to search for and publish each Web service in UDDI Registries. Generally, the addresses of the UDDI API are specified in the documentation for the UDDI Registry. The SAP UDDI Registry (http://uddi.sap.com) includes the destinations, for example, under UDDI@SAP Developer Information.

To publish a Web service in a UDDI Registry, you need a user. You can apply for this user on the UDDI Registry Web page. You must have created a business entity under this user account in the UDDI Registry.

The entries in the User, password, and Default Business Entity fields are optional. If you do not enter a user and password, a dialog box appears requesting this information when the Web service is published in the appropriate registry.

If you enter the password when setting up a UDDI Registry in the SUDDIREG transaction, it is then stored, unencrypted, in the database. According to the UDDI specification, the password must be transferred in plain text within an XML document. This would mean that an encrypted password would have to be decrypted. At present, however, the mechanism for doing this cannot be made available, for security reasons.

       4.      Call transaction SM59 and enter the destination as an HTTP connection to the external server. Maintain the target system settings.

For more information on maintaining destinations, see the Destination Types in the documentation on RFC Programming in ABAP.

The Web service should be published using an HTTPS connection, in accordance with the UDDI specification. To do this, activate the security option SSL on the Logon/Security tab.

 

See also:

Creating a Web Service Definition (Publishing a Web service definition in the UDDI as a tModel)

Administration for the SOAP Runtime (Publishing a Web Service as a business service)

UDDI as a Source for a WSDL Documents (Proxy Generation)