Show TOC

Creating and Configuring Web Service ProvidersLocate this document in the navigation structure

Use

When you provide Web services using the Integration Server (IS) as a broker between the provider and the consumer side, the communication flow goes through different stages. To invoke a Web service method on the provider side, the IS sends a relevant message request to the service provider. Initially the request sent from the IS is an XI-specific message. However, the Java Proxy Runtime (JPR) transmits the message to the Web service runtime and the Web service runtime in turn converts the message to a SOAP message and thus makes it comprehensible to the Java Web service.

The figure below describes the different stages of the communication flow from the request of the IS to the provider side.

Each XI message that comes from the IS comprises payload, attachments, and specific XI data. The Java Web service runtime uses the payload to create the relevant SOAP message which invokes the business methods on the Web service. It also uses SAP-specific application program interfaces to retrieve the attachments, and to expose the specific XI data from the request (XI-specific message) to the provider.

Procedure

Create an inbound proxy. In this case, the IS can be viewed as a service consumer.

  1. Create a synchronous or an asynchronous Java Web service provider (inbound proxy) for brokered communication.

    Creating Web Service Providers for Brokered Communication

  2. Extend the inbound proxy capabilities by using the application program interfaces for inbound proxy communication.

    Application Program Interface for Inbound Proxy Communication