Generating Configuration Objects 

Purpose

Based on the information saved in the integration scenario, the assigned services, and the configured connections, it is possible to determine the receiver determinations, interface determinations and collaboration agreements. If these objects already exist, they will be reused and enhanced as required. Otherwise they will be created.

Prerequisites

·        The component view can be configured.

·        Services have been assigned for at least two application components.

·        A sender/receiver relation has been activated for at least one connection.

Process Flow

To start the generation of configuration objects, in the Configuration Steps menu bar, choose the step Generation.

You can make the settings for generation in the Create Configuration Objects dialog.

When generating configuration objects, only connections that satisfy the following conditions will be included:

·        Sender and receiver services have been assigned

·        A least one sender/receiver relation has been activated

You can terminate generation of configuration objects at any point. To do so, in the Generation Progress or Simulation Progress dialogs, choose Cancel or close the dialog. The current generation step is canceled and the generation log is then displayed. Note that objects that have already been generated are not automatically deleted when you cancel the generation process in this way.

Generating Receiver Determinations

The outbound interface of a connection and the sender services assigned to the relevant application component make up the key for the required receiver determinations. For each sender, the integration scenario configurator searches in the Integration Directory for a receiver determination with a matching key.

·        If an appropriate object is not found, the system creates a new receiver determination with the required receivers and adds it to the scenario.

·        If the system finds a receiver determination with an appropriate key, then this is used for the connection and is added to the scenario.

If the receiver determination found lacks any receivers that you require, you can enhance the object to include these receivers.

SAP recommends that you check the conditions for the individual receivers of the connection afterwards. The newly created receiver determinations do not contain a specific condition. This means that the assignment to the relevant receivers is <TRUE>.

Generating Interface Determinations

The outbound interface and the activated sender/receiver relations of a connection form the key for the required interface determinations. For each sender/receiver relation in the connection, the integration scenario configurator searches in the Integration Directory for the most specific interface determination with a matching key (see Generic/Specific Definition of Configuration Objects).

·        If the system doesn't find a matching object, then it creates a new interface determination (with the inbound interface and mapping from the connection) and adds it to the configuration scenario.

·        If the system finds a matching interface determination, this it uses it and adds it to the scenario, regardless of the individual inbound interface entries and mapping entries for the object.

If there is no matching entry for the inbound interface and mapping from the connection, how the generation process continues depends on whether you permitted the changing of interface determinations in the generation settings:

·        Changes to interface determinations are not permitted

If no matching entry exists for the inbound interface and mapping from the connection, this is indicted in the generation log. The interface determination is not modified or enhanced automatically. This avoids unexpected side effects in other scenarios, which use the same interface determination. You must make any required changes or modifications to interface determinations manually. The generation log contains information about such modifications.

·        Changes to interface determinations are permitted

The interface determination is modified or enhanced automatically.

This may have an effect on other configuration scenarios that use the same interface determination.

If a new or reused interface determination is assigned multiple inbound interfaces, you must check the conditions of the individual interfaces afterwards. The new interface determination does not contain any specific conditions in this case. This means that the assignment to the relevant inbound interfaces and interface mappings is <TRUE>.

Generating Collaboration Agreements

The outbound/inbound interface and the sender/receiver relations of a connection form the key for a sender agreement/receiver agreement. The integration scenario configurator generates collaboration agreements with a communication channel for this combination of key attributes. If a collaboration agreement already exists for a combination of outbound/inbound interface and sender/receiver relation, then this is reused.

Otherwise, you must create a new communication agreement. Unlike with other object types, there can be no conflicts with existing collaboration agreements when you generate collaboration agreements. Conflicts are avoided by including existing collaboration agreements in the input help when assigning communication channels.

Only the communication channels are entered in the generated collaboration agreements. You create the relevant security settings and the header mapping (for receiver agreements) manually after generation.