Configuring Destinations for WS Callable Objects 

Use

Before you can expose a Web service (WS) as a callable object, you have to create and configure the destination that points to the location of the service.

Destinations are required for all Web services that need authentication.

Prerequisites

·        You have access to the SAP NetWeaver Administrator of your Application Server (AS) Java.

·        You know the name of the application server that holds the Web service information (WSIL or WSDL file).

·        In case you use a UDDI Services Registry (SR), you must know the connection properties for the systems that host the UDDI server, the classification service, and the SR itself.

Procedure

...

       1.      Start the SAP NetWeaver Administrator and navigate to SOA Management → Technical Configuration → Destination Template Management.

       2.      Choose Create Destination.

       3.      In the Destination Name input field, enter a name for the destination.

       4.      From the Destination Type dropdown box, select the type of destination:

Destination Type	Configuration and Examples
WSDL	In the URL field, enter the direct link to the servlet that generates the WSDL file. http://<host>:<port>/<name of service> http://localhost:53000/GPRuntimeFacadeWS/GPProcessExposing?wsdl
WSIL	In the URL field, enter the direct link to the servlet that generates the WSIL file. http://<host>:<port>/<location of service> http://localhost:50000/gpcore/GPProcessDiscoveryWSIL/inspection.wsil
Services Registry	This type of destination is used to configure the UDDI Services Registry. Depending on the system that hosts the SR (Java or ABAP), you have to specify relevant connection details and security options.

       5.      From the Authentication dropdown box, choose HTTP Authentication.

       6.      Select UserID/Password (Basic) and choose Details.

You may need to configure different types of authentication for the different ways a Web service is accessed (metadata retrieval or invocation). For example, you may use both basic HTTP authentication and X.509 Client certificate. In this case, you must create two separate destinations:

■       For the metadata information (WSDL)

■       For the location of the Web service (WSIL). It is used as an endpoint for invocation.

       7.      Enter the appropriate User ID and Password.

       8.      Choose Save.

For more information about:

●      UDDI Services Registry, see Configuring the Services Registry.

●      Web service configuration, see Creating Web Service Physical Destinations.

Result

You can now use the destination in Guided Procedures to create a callable object of type Web Service.

More information: Exposing Web Services as Callable Objects

Example

Guided Procedures offers its own Web services for starting processes and completing actions. To be able to use them, you have to configure destinations of type WSIL:

●      GPProcessDiscovery Web services

URLs: http://<host>:<port>/gpcore/GPProcessDiscoveryWSIL/inspection.wsil

http://<host>:<port>/gpcore/GPProcessDiscoveryActiveWSIL/inspection.wsil

More information: Consuming the GPProcessDiscovery Web Services

●      GPActionDiscoveryWSIL service

URL: http://<host>:<port>/gpcore/GPActionDiscoveryWSIL/inspection.wsil

More information: Consuming the GPActionDiscoveryWSIL Web Service