Configuring Logical 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 logical destination that points to the location of the service.

Logical destinations are required for all Web services that need authentication. For example, you can use an ABAP Web service only through a predefined logical destination.

Prerequisites

·        You have access to the Visual Administrator tool.

For more information, see Visual Administrator.

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

For more information about consuming a Web service, WSIL and WSDL generation, see:

Consuming the GPProcessDiscovery Web Services

Consuming the GPActionDiscoveryWSIL Web Service

Procedure

...

       1.      Start the Visual Administrator and navigate to Cluster → <System ID> → Server → Services → Web Services Security.

       2.      On the Runtime panel, in the Web Services list, navigate to Web Service Clients → sap.com → Dynamic WSProxies.

       3.      Choose Create …

       4.      In the name input field, enter a name for the logical destination. For example, Exposing.

       5.      In the URL input field, enter the name and port of the machine where the WSIL file is stored:

http://<host>:<port>/

Replace <host> with the host name of where your application server resides, and <port> with the server’s port for HTTP communications.

http://localhost:53000/

http://usciq6d.wdf.sap.corp:50077/

       6.      From the Authentication dropdown box, choose BASIC and enter the appropriate Username and Password.

Make sure that you have assigned the portal role GP Administrator to the user that accesses the Web service.

More information: Portal Roles

       7.      For ABAP Web services you should also enter:

¡        System ID – for example, Q6D

¡        Client – for example, 505

¡        Language – for example, EN

       8.      Choose Save.

       9.      In addition to this logical destination, you have to create a second one that holds information about the location of the servlet generating the WSIL file.

In the destinations list in GP design time, these two destinations are displayed as one.

   10.      To do this, repeat steps 3 through 8.

For the second destination:

¡        In the name input field, enter a name in the format <name of first logical destination>_METADATA.For example, Exposing_METADATA.

To ensure the correct detection of logical destinations in GP, you should strictly follow this naming convention.

¡        In the URL input field, enterthe direct link to the servlet that generates the WSIL file, depending on the type of services you want to use:

J2EE Web services	http://<host>:<port>/gpcore/<name of service>/inspection.wsil For the GPProcessDiscoveryWSIL service, enter http://<host>:<port>/gpcore/GPProcessDiscoveryWSIL/inspection.wsil For the GPActionDiscoveryWSIL service, enter http://<host>:<port>/gpcore/GPActionDiscoveryWSIL/inspection.wsil http://localhost:53000/gpcore/GPActionDiscoveryWSIL/inspection.wsil
ABAP Web services	http://<host>:<port>/sap/bc/srt/wsil?sap-client=<client> http://usciq6d.wdf.sap.corp:50077/sap/bc/srt/wsil?sap-client=505

Result

You can now use these logical destinations in Guided Procedures to create a callable object of type Web Service.

See Exposing Web Services as Callable Objects.