Show TOC

Procedure documentationCreating WsActionInboxConnector Proxy Locate this document in the navigation structure

 

To connect and consume the ActionInboxConnectorWS Web service of the remote provider, you need to create and deploy the WsActionInboxConnector proxy on the consumer system.

Prerequisites

To create the WsActionInboxConnector proxy, you have to meet the following prerequisites:

  • You have registered the provider system as an item provider for the Universal Worklist.

  • You know the alias for the provider that you specified when registering the provider system in the Universal Worklist.

  • You know the hostname and port of the provider.

Procedure

  1. Create the deployable proxy.

    1. In the SAP NetWeaver Developer Studio, create a Web service proxy project named tc~kmc~km.appl.ui~aibproxy.

    2. Create the proxy definition by specifying the parameters as follows:

      • In the Package input field, enter com.sap.netweaver.bc.uwl.core.connect.wsaib.proxy.

      • In the Proxy Name input field, enter ActionInboxConnectorWSProxy.

      • For Select WSDL Source, choose Local File System or URL.

      • For the WSDL URL, use the following pattern: http://<Provider_hostname>:<Provider_HTTP_port>/ActionInboxConnectorWS/Config1?wsdl.

    More information: Creating a Deployable Proxy

  2. Before deploying the proxy, configure the logical port.

    To do so, open the logical port and change the settings as follows:

    • In the Target Address input field enter the WSDL URL using the following pattern:http://<Provider_hostname>:<Provider_HTTP_port>/ActionInboxConnectorWS/Config1?style=document.

    • In the Local Port Name input field, enter the previously defined alias of the provider system.

      More information: Setting up the WsActionInboxConnector in the Universal Worklist

    • On the Security tab page, choose Use SAP Logon Ticket for the authentication method.

    Note Note

    You must add and configure a new logical port for each provider system you want to connect to.

    You may want to keep the project for future use. Thus you do not have to configure the already existing ports again when adding a new provider system.

    In this case, you only need to add a logical port for the new provider.

    End of the note.

    More information: Configuring Logical Ports

  3. Build and deploy the proxy.

    Select the name of the proxy and choose Build EAR from the context menu. When the EAR file is generated, select it and choose Deploy from the context menu.

    SAP NetWeaver Developer Studio deploys the Web service proxy locally or on a remote system depending on the settings specified in   Window   Preferences   SAP J2EE Engine  .