Generated Objects

Use

The following objects are generated (depending on the type of connection):

Connection Type	Generated Objects (Generation Scope)	Manual Editing Required
Connection Without Mapping (No PI runtime component involved in the message processing)	Direct Connection	Check the adapter-specific attributes
Connection with or Without Mapping (dual-stack message processing where Integration Engine is invovled)	Receiver Determination	Check the conditions
Interface Determination	Check the conditions
Collaboration agreement	Security Settings Header mapping

You can define the generation scope using the following functions in the application toolbar of the model configurator:

Generate All Connections for Direct Communication

Direct connections are generated for all connections without a mapping (no collaboration agreements).
Generate All Connections for Integration Server Communication

Collaboration agreements are generated for all connections (no direct connections).

Generating Direct Connections

The outbound interface of a connection and the sender and receiver communication components assigned to the relevant process component form the key for the required direct connections. The system searches in the Integration Directory for a direct connection with a matching key.

If the system cannot find such an object, it creates a new direct connection and adds it to the configuration scenario.
If the system finds a direct connection with a matching key, then this is used for the connection and is added to the configuration scenario. If this direct connection contains a communication channel or an interface that does not match the settings you have made in the model configurator, this is noted in the generation log.

Generating Receiver Determinations

The outbound interface of a connection and the sender communication components assigned to the relevant process component form the key for the required receiver determinations. The system searches in the Integration Directory for a receiver determination with a matching key for each sender.

If the system cannot find such an object, it creates a new receiver determination with the required receivers and adds it to the configuration scenario.
If the system finds a receiver determination with a matching key, then this is used for the connection and is added to the configuration scenario.

If any required receivers are missing in the receiver determination found, the object is enhanced to include these receivers.

Recommendation
We recommend that you check the conditions for the individual receivers of the connection afterwards. The newly created receiver determinations do not contain a specific condition.

Generating Interface Determinations

The outbound interface and the activated sender/receiver relations of a connection form the key for the required interface determinations. The system searches in the Integration Directory for the most-specific interface determination with the matching key for each sender/receiver relation of the connection.

For more information, see: Generic/Specific Definition of Configuration Objects

If the system cannot find an object with a matching key, 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 an interface determination with a matching key, it uses it and adds it to the configuration scenario, regardless of the individual inbound interface entries and mapping entries for the object.

If the system finds an interface determination with a matching key, but the key does not match the inbound interface or mapping from the connection, then how generation continues depends on whether you permit changes to interface determinations in the generation settings.

Changes to interface determinations are not permitted

If an interface determination with a matching key exists, but the key does not match the inbound interface or mapping from the connection, this is indicated by the generation log. The interface determination is not modified or enhanced automatically. This avoids unexpected side effects in other configuration scenarios that use the same interface determination. You must make any required changes or modifications to interface determinations manually. The generation log contains information to help you make these modifications.
Changes to interface determinations are permitted

The interface determination is modified or enhanced automatically.

If a new or reused interface determination is assigned multiple inbound interfaces, you must check the conditions of the individual inbound interfaces afterwards. The new interface determination does not contain any specific conditions in this case. This can cause problems in existing configuration scenarios because the inbound interface is no longer unique.

Generating Collaboration Agreements

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

Otherwise, a new collaboration agreement is created. Unlike with other object types, conflicts with existing collaboration agreements do not occur when collaboration agreements are generated. Conflicts are avoided because existing collaboration agreements are taken into account when assigning communication channels using the input help.

Only the communication channels are entered in the generated collaboration agreements. You create security settings manually after generation.