Web Service Providers for Brokered Communication

Design the service interface in the Enterprise Service Repository (ES Repository).

In the Enterprise Service Builder, design an inbound service interface. The inbound service interface comprises 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 provider system and the IS:

• Create a receiver communication component to define details about inbound processing and enable communication between the Web service provider and the IS.

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

• Create receiver determination and receiver agreement.

  A receiver agreement contains a reference to a communication channel. You define a receiver agreement between a sender and a receiver for an inbound interface. For more information, see Defining a Receiver Agreement and Defining Receiver Determinations .

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

Create the Web service (inbound proxy) in SAP NetWeaver Developer Studio:

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

2. Create an outside-in Web service based on the WSDL document of the relevant inbound Service Interface modeled in the ES Repository.

   The Web service framework generates the skeleton of the implementation bean containing the Web service methods' declarations for the operations in the WSDL document. For more information about creating an outside-in Web service, see Creating Outside-In Web Services .

3. Provide an implementation of the business methods of the Web service.

4. Only for asynchronous Web services, add the following WS-RM-related annotation in the source code: @RelMessagingNW05DTOperation(enableWSRM=true)

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

Configure the Web service.

• In the Integration Builder, configure the receiver communication channel you created in step 2 above. The receiver communication channel is a target URL that points to the URL of the Web service.

  For asynchronous Web services, you can construct the target URL using the following pattern: http://[Host]:[Port]/[Service_Access_Path]?wsdl&mode=ws_policy

• In SAP NetWeaver Administrator, create a runtime configuration (called service endpoint) of the Web service.

  It contains the relevant runtime settings, such as authentication level, with which you want to provide the Web service.

  For more information about configuring the Web service in the SAP NetWeaver Administrator, see Configuring Individual Web Services and Configuration of Individual Web Services and Web Service Clients .