Configuration 

Purpose

You use the Integration Builder to configure business processes that are based on the cross-component exchange of messages. You can reproduce the “choreography of the messages“ that you have defined in a Business Scenario in the productive system landscape and define the message flow between the participating business systems. This enables you to gather together all the information in the Integration Directory that is required to process messages at runtime.

Prerequisites

To be able to access the information required for configuration, note the following:

·        Ensure that your system landscape is described in the System Landscape Directory

·        Ensure that the relevant Business Scenarios, interfaces, and mappings are defined in the Integration Repository.

Process Flow

The following steps are usually carried out in the configuration phase:

...

       1.      Hopefully, you have already defined a Business Scenario at design time and have therefore outlined all the cross-component communication steps of your business process where messages are exchanged (see Designing Business Scenarios).

       2.      The process of identifying the receivers of all the messages involved is defined when you configure routings. The routing relation determines the possible receivers that the messages of a particular outbound interface for a sender system are to be forwarded to. You also have the option of specifying further conditions in the routing relation regarding the forwarding of the message to the receiver.

       3.      To map the data structures on the sender and receiver side by using mappings, you must define mapping relations. In a mapping relation, an outbound interface is assigned an inbound interface on the receiver side and an interface mapping from the Integration Repository (see: Defining Mapping Relations).

       4.      For technical receiver identification to take place, you must specify technical access data about the receiver systems, for example, the physical address. You define the information required here when you define end points. Different end point types are used depending on whether adapters are implemented on the receiver side for message processing, and if so, which particular adapters.

       5.      You can also specify logon data for receiver systems to keep control of system access at the message receiver. Whether logon data is used, and if so, how, depends on the end point type.

Configuration objects are assigned to a particular combination of sender and receiver systems and interfaces in each case. When defining mapping relations, end points, and logon data you can use placeholders to replace the business systems and interfaces. This enables you to make the range in which the configuration objects are valid very flexible (see Default Procedure).