Setting Destinations to UDDI Server and Classification Service

Use

You need to set the destinations to UDDI server and the classification service manually only if one or more of the following applies:

You use a non-SAP UDDI server.
You have an AS ABAP release in your system environment that is a lower version than 7.0 SP14 (for SAP NetWeaver 7.0 versions) or 7.1 SP04 (for SAP NetWeaver 7.1 and later versions).

Prerequisites

The user account you use should be assigned to the SAP_JAVA_WS_ADMIN_TEC role. For more information, see Authorizations .

Procedure

Managing Destination Templates

To access SAP NetWeaver Administrator, open a browser and enter the following address: http://[host]:[port]/nwa
Choose SOA Technical Configuration Destination Template Management.

Creating Destination to the UDDI Server

When you want to use a non-SAP UDDI server, use an older release version of AS ABAP, or use any version of Visual Composer, you need to create the following destination:
- Destination Type : WSDL
- Destination Name : UDDI_DESTINATION
- URL : http://[host]:[port]/uddi/wsdl/uddi_v3_service.wsdl
  
  The URL used as an example is valid for the SAP UDDI server. If you are using a non-SAP UDDI server, the URL would be different.
- For authentication, select HTTP Authentication , and then choose User ID/Password (Basic) .
- Enter a user ID and password.
  
  Make sure the user account you provided is assigned to the UDDI_Admin and SERVICES_REGISTRY_READ_WRITE roles.
Note

Consider that when using the UDDI_DESTINATION destination you cannot use the role-based access control feature of Services Registry and cannot apply usage profiles.
When you want to use role-based access, you need to create the following destination:
- Destination Type : WSDL
- Destination Name : UDDI_DESTINATION_V11
- URL : http://[host]:[port]/uddi/wsdl/uddi_v3_service.wsdl
  
  The URL used as an example is valid for the SAP UDDI server. If you are using a non-SAP UDDI server, the URL would be different.
- Authentication: select HTTP Authentication , and then select Logon Ticket .
Note

When both UDDI_DESTINATION and UDDI_DESTINATION_V11 destinations are present, the latter takes precedence for SR 1.1.
When you want to connect to a non-SAP UDDI server using the AuthToken authentication mechanism, you need to create the following destination:
- Destination Type : WSDL
- Destination Name : UDDI_DESTINATION_AUTH_TOKEN
- URL : http://[host]:[port]/uddiat/wsdl/uddi_v3_service_authtoken.wsdl
  
  The URL used as an example is valid for the SAP UDDI server. If you are using a non-SAP UDDI server, the URL would be different.
- For authentication, select HTTP Authentication , and then choose User ID/Password (Basic) .
- Enter a user ID and password.
  
  Make sure the user account you provided is assigned to the UDDI_Admin and SERVICES_REGISTRY_READ_WRITE roles.
Note

The UDDI_DESTINATION_AUTH_TOKEN destination is used only as a holder of the credentials of the user used in get_AuthToken request. It is mandatory to perform all of the following additional configurations:
- UDDI_DESTINATION_AUTH_TOKEN must be used along with one of the above described destinations, UDDI_DESTINATION or UDDI_DESTINATION_V11.
- These destinations should have the same endpoint URL as the UDDI_DESTINATION_AUTH_TOKEN destination, for example: http://[host]:[port]/uddiat/wsdl/uddi_v3_service_authtoken.wsdl
- These destinations should have authentication method set to None.

Creating Destination to the Classification Service

Create a new destination with the following properties:

Destination Type: WSDL
Destination Name: CLASSIFICATION_DESTINATION
URL: http://[host]:[port]/ClassificationService/CS?wsdl
Authentication: HTTP Authentication
Select User ID/Password (Basic)
Enter a user ID and password
If this user is not an administrator, assign the roles UDDI_Admin and SERVICES_REGISTRY_READ_WRITE.

Result

After changing the destination to the UDDI server and the classification service, you need to restart the AS Java engine. The destination of the SAP UDDI server and the classification service must point to the same AS Java.