Configuring Message Processing
You can configure how a message is processed on the Integration Server.
The configuration objects that result from your entries are either created or are modified, depending on whether they already exist or not. You can always see which configuration step you are currently working on from the progress display in the frame next to the input fields in the configuration wizard.

The tool for configuring message processing is also known as the configuration wizard.
You can use this tool when you want to configure a single communication step. If you want to configure an entire integration scenario, use the integration scenario configurator.
You can call the configuration wizard as follows:
·
In the Integration
Builder (Integration Directory) main menu bar, choose Tools
®
Configuration Wizard (
).
·
Open a configuration
scenario and choose Configuration Wizard (
) in
the menu bar of the object editor in the Display/Edit Scenario editor.
You can choose between the following communication scenarios with the configuration wizard:
Possible Communication Scenarios
Communication Scenario |
Use |
Internal Communication
|
Select this option to configure the communication between the services of the internal system landscape (business systems, integration processes, and business services without parties). |
Partner Communication
|
Select this option if external partners are involved in message exchange (as senders or receivers or both). Senders and receivers can be · External business partners · Services of the internal system landscape |
You can choose between the following communication scenarios on the initial screen of the configuration wizard. Select the relevant icon to begin configuring the scenario.
This section gives an overview of the specifications you must make in the individual configuration steps. The configuration wizard provides instructions for each step of the configuration procedure.
In this configuration step you specify the message expected by the Integration Server.
The data you must enter varies depending on the communication scenario:
· Internal Communication
In internal communication, you must specify the sender of the message. The sender can be a business system (service), integration process (service), or a business service. The services must not be assigned to a communication party. You must also specify an adapter type for inbound processing.
· Partner Communication
In partner communication, you specify whether the message originates from the (internal) system landscape or from an external business partner (external source). Use the relevant radio button to make your selection.
If the message originates from the internal system landscape, then you specify the sender in the same way as for the Internal Communication communication scenario.
If the message originates from an external source (external business partner), then the entries you must make vary depending on the adapter type you have selected.
¡ If you have selected the adapter type XI, you must specify the header of the expected message on the subsequent screen. You must also specify the agency and schema for the sender and receiver parties so that the party can be identified uniquely. For more information, see: Identifiers. If the identifiers are new, in the subsequent dialog, assign both the sender and receiver parties to a communication party that is defined in the Integration Directory. The configuration objects work with this ”normalized” party identifier.
¡ If you have selected the adapter type RNIF, specify the header of the RNIF (RosettaNet Implementation Framework) message.
¡ If you have selected the adapter type IDoc, specify the header of the IDoc message.
¡ For all other adapter types, specify the party, service, and inbound interface for the sender and receiver of the message.
Using the inbound and outbound message data that you have entered for the sender and receiver (and inbound interface), the system produces a key for the receiver determinations, interface determinations and collaboration agreements (see: Creating an Object).
The configuration objects are produced based on the other entries that you make in the configuration wizard.
If a corresponding configuration object already exists in the Integration Directory for the entries you have made, then it is reused and enhanced; if not, a new configuration object is created.
Note the following information about the various object types:
· Interface Determinations
In the configuration wizard, you can specify whether a mapping is to be used. The selected interface mapping is then assigned to the interface determination, which is taken from the specified key.

The results of the configuration wizard vary depending on whether an interface determination exists in the Integration Directory for the information that has already been specified (sender, receiver, and interface mapping):
If an interface determination doesn't already exist, the system creates a new generic interface determination once the configuration wizard is finished, based on the entries you have made.
If a (generic) interface determination already exists, the system creates a new specific interface determination once the configuration wizard is finished, based on the entries you have made. The interface determination only applies for the sender/receiver pair that you have specified in the configuration wizard.
If a (specific) interface determination already exists that exactly matches what you have entered in the configuration wizard, then this interface determination is used.
For more information, see: Generic Definition of Interface Determinations.
· Collaboration Agreements
Certain adapter types do not require sender agreements. If this is the case, the relevant steps in the configuration wizard are skipped.
Once you have made all your entries, choose Finish.
The following is documented in the configuration wizard log:
· Which new objects have been created and which reused
· Further information
For example, you are informed that you can define receiver determination conditions in a new or reused object.