Web Service Consumers for Brokered Communication

Design the service in the Enterprise Service Repository.

In the Enterprise Service Builder, design an outbound service interface. The outbound service interface comprises the interface pattern stateless , operations, message types, data types, and fault types. For more information, see Service Interface , Interface Pattern , Message Type , and Fault Message Type .

Configure the service interface in the Integration Directory.

In the Integration Builder, create the following components to configure the service interface communication between the consumer system and the IS:

• Create a sender communication component to define details about outbound processing and enable communication between the Web service client and the IS.

• Create a sender communication channel.

  In particular, you can use a communication channel to define the type and configuration of the adapter used during outbound processing. For more information, see Defining Communication Channels .

• Create sender agreement and interface determination.

  A sender agreement contains a reference to a communication channel. For more information, see Defining Sender Agreements and Defining an Interface Determination .

  Optionally, you can create a sender party. For more information, see Defining Communication Parties .

Create a Web service deployable proxy and a client application in SAP NetWeaver Developer Studio:

1. Import the WSDL document from the Enterprise Service Repository. For more information, see Importing WSDL Documents in the SAP NetWeaver Developer Studio .

2. Generate a deployable proxy based on the WSDL document of the relevant outbound service interface modeled in the Enterprise Service Repository. For more information, see Creating Web Service Proxies .

3. Create a client application that uses the deployable proxy you generated. Consider the following options:

   • When using synchronous communication, in the consumer application you should specify a URL to the Web service, a user name, and a password to the PI Adapter Engine.

     You can construct a URL to the Web service using the following pattern: http://[Adapterengine_Host]:[Port_Number]/XISOAPAdapter/MessageServlet?channel=[Sender_Party]:[Sender_Service]:[Sender_Channel]

     For more information, see Configuring the Sender SOAP Adapter .

   • When using asynchronous communication, in the consumer application you specify username and password to the PI Adapter Engine.

   For more information, see Creating Web Service Client Applications .

4. Deploy the Web service consumer on the application server. For more information, see Building, Publishing and Removing Published Java EE Applications .

Configure the Web service consumer.

1. In the Integration Builder, configure the sender communication channel you created in step 2 above.

   The sender communication channel is a target URL that points to the URL of the Web service. You construct the target URL by using the following pattern:

   • When using synchronous communication, use http://[AdapterEngine_Host]:[Port_Number]/XISOAPAdapter/MessageServlet?channel=[Sender_Party]:[Sender_Service]:[Sender_Channel] .

   • When using asynchronous communication, use http://[Host]:[Port]/[Service_Access_Path]?wsdl&mode=ws_policy .

2. In SAP NetWeaver Administrator, create a runtime configuration (known as logical port ) of the Web service consumer.

   You can create a logical port based on a WSDL URL that determines the destination to which the Web service consumer sends its requests. In this case, the destination is the IS. Therefore, you have to create the logical port based on the WSDL URL that you obtained from the Integration Directory at a previous step. The logical port you create also contains the runtime configuration settings, such as username and password, or WS-RM parameters, which the Web service consumer uses.

   For ore information about configuring Web service consumers, see Configuring Individual Web Service Clients and Configuration of Individual Web Services and Web Service Clients .