SAP NetWeaver PI supports connectivity between the Web service provider and the Web service consumer.
The Web service provider and consumer can communicate based on one of the following patterns:
Mediated (or “Brokered” ) Communication
Between Web service provider and consumer SAP NetWeaver PI is interconnected as integration middleware.
In this case, the mediation capabilities of SAP NetWeaver PI can be used for routing and mapping.
To configure this kind of communication, you can use communication channels with either adapter type SOAP or WS (for connectivity with applications based on Web Services Reliable Messaging (WS-RM)).
Note that the SOAP adapter does not support WS-RM, but does provide proprietary means to deliver messages according to the Qualities of Service Exactly One and Exactly Once in Order .
The adapter that you can use depends on the installation option. For example, if you have installed the Advanced Adapter Engine Extended then you can use the communication channel with adapter type SOAP which runs on the Advanced Adapter Engine (but not adapter type WS ).
The Web service provider and consumer communicate with each other directly.
The following figure illustrates the two different communication types:
To develop and configure Web service scenarios, you generally adhere to the following procedure:
Mediated (or Brokered) Communication“Brokered”
Web Service Provider
When you set up and configure this part of the communication, the Integration Server (or Advanced Adapter Engine) can be viewed as Web service consumer.
Design the inbound service interface in the Enterprise Service Repository (ES Repository).
Configure the inbound service interface in the Integration Directory.
Create the Web service (inbound proxy).
Configure the Web service.
Web Service Consumer
When you set up and configure this part of the communication, the Integration Server (or Advanced Adapter Engine) can be viewed as Web service provider.
Design the outbound service in the Enterprise Service Repository.
Configure the outbound service interface in the Integration Directory.
Create a Web service-deployable proxy and a client application.
Configure the Web service consumer.
For information on how to perform the individual tasks (for example, service interface design) in detail, see the corresponding section under Developing and Configuring Integration Scenarios for the corresponding installation option.
As an example for an end-to-end procedure for the cases the Web service provider and consumer are based on AS Java, see section below.
More information: Setting Up Direct Communication
Mediated Communication Between Provider and Consumer (Based on AS Java)
The following sections provide specific information on how to develop and configure Web service consumers and providers based on Application Server Java in order to communicate in the scenarios described above:
End-to-end procedure for developing and configuring Web service provider and consumer in order to communicate with an Integration Server: Web Service Providers and Consumers for Brokered Communication
End-to-end procedure for developing and configuring Web service provider and consumer if the interface pattern XI 3.0-Compatible is selected: Creating and Configuring XI 3.0-Compatible Web Service Providers