Brokered Service-Based Integration 

In this variant, you enhance point-to-point Web service calls by using the Integration Broker as a broker between the Web service client and the service provider. The following figure illustrates that the Integration Broker can forward the Web service call to services from various different systems in a heterogeneous system landscape.

 

In addition to a service that a provider has published as a Web service, you can use the brokered service-based integration variant to call services of a non-SAP or legacy SAP system that cannot otherwise be made available as Web services directly (for example, because they do not support the SOAP protocol). By using a mapping, the Integration Broker can also call such services whose interface signature is not identical to that of the Web service call. To determine the receiver, you use the routing functions of the Integration Broker.

Required or Optional Installable Units

To use this IT scenario you require the following installable units:

System with activated usage types:

●     Process Integration (PI)

●     AS Java

●     AS ABAP

For more information about the required system landscape, see the Master Guide.

IT Processes of the Scenario Variant

This scenario variant comprises the following IT processes:

Process	What You Should Know…
Service Consuming	To execute a service of another system, the application calls a proxy in the application system. The result of the call is that the application system sends a message to the Integration Broker.
Service Brokering	The Integration Broker processes the messages according to a central configuration, which defines the routing and, if applicable, any mappings. You also have the option of processing the message by using an integration process.
Service Providing	The service provider receives the message and calls the service. The receiver sends the response to the request to the Web service client by using the Integration Broker.