Brokered Services 

Use

In the simplest case, you want to use the Integration Server to exchange messages between two systems that both support proxy generation. To do this, you create data types, (fault) message types, and message interfaces directly in the ES Repository. Since service interfaces comply with accepted standards, we recommend that you use this approach for new developments.

The procedure described here concentrates on the necessary technical steps of development and does not take design guidelines into account.

Prerequisites

You have two applications and you want to use the outside-in approach to enable them to exchange messages. The service interfaces are in different products and different software component versions. We will refer to them as CONSUMER and PROVIDER.

More information: Organization of ESR Content

Procedure

1. Model the Inbound Service Interface

       1.      First model the objects of the service that is to be called at the provider.

...

       1.      Create an inbound service interface in the software component version PROVIDER. Select the interface pattern appropriate to the usage.

Enhanced communication scenarios using the Integration Server support the interface patterns Stateless (XI 3.0-Compatible), Stateless, and TU&C/C.

       2.      Create the operations required for your service at the inbound service interface. Service interfaces with the interface pattern Stateless (XI 3.0-Compatible) only support one operation.

       3.      First determine whether message types and data types already exist for the operations you have created (for example, by using the search help). If necessary, create new message types and data types in the software component version PROVIDER.

       4.      Reference from the operations to the respective message type and from the message type to the data type.

       5.      To handle application-specific errors that occur on the inbound side, you can use fault messages (optional). Check whether a corresponding fault message type already exists; if necessary, create a new fault message type in the software component version PROVIDER and reference it from the related operations.

2. Model the Outbound Service Interface

       6.      Service interfaces can only be delivered as a whole (that is, including all referenced objects). Because of this, the operations of the required outbound service interface in the software component version CONSUMER cannot reference the interface objects of the software component version PROVIDER. Therefore, you must copy the objects.

       7.      Copy the inbound service interface from the software component version PROVIDER to the software component version CONSUMER with all dependent objects.

       8.      Reclassify the inbound service interface in the software component version CONSUMER as an outbound service interface.

       9.      Make sure that the XML namespace of the respective (fault) message type that is referenced by the respective operation of the outbound service interface matches the XML namespace of the corresponding (fault) message type of the inbound service interface. More information: XML Namespaces.

More information: Service Interface.

Result

You have created an outbound service interface and an inbound service interface, each with one or more operations. By using proxy generation, you can generate proxy objects in ABAP or Java to implement the communication between these two interfaces using the proxy objects.