Configuration
Purpose
At configuration time you set up a collaborative process for a specific system landscape. The configuration data is structured, organized, and saved in the Integration Directory in the form of configuration objects.
The Integration Directory is structured around the cross-system task areas.
Task Area and Structure of the Integration Directory
Task |
Relevant Configuration Objects |
Configure the collaboration profile ● Specification of potential senders and receivers of messages and description of their technical options for exchanging messages. ● In cross-company processes: Specification of the business partners involved (as communication parties) and their services for communication. ● In internal company processes: Specification of the business systems and integration process involved (as services) that communicate with each other by exchanging messages. ● Specification of the technical communication paths (adapter configuration in the communication channel object). |
Communication Party (party for short) |
Configure collaboration agreements ● Definition of the communication channels to be used by particular senders and receivers to exchange messages ● Specification of security settings for message security |
|
Configure logical routing ● Definition of routing rules for forwarding messages |
Configuration objects are identified uniquely by an object key. In configuration objects, the object key is dependent on the object type.
The following figure illustrates how the various different configuration objects relate to each other.
Relationship Between Objects in the Integration Directory
Process Flow
● If you have defined an integration scenario for your collaborative process, configure the collaborative process on the basis of this integration scenario (see Configuring Integration Scenarios).
● If you have not defined an integration scenario, you can use the configuration wizard to help you configure individual communication steps.
● You also have the option of doing the configuration manually and defining all the configuration objects separately. This is the most time-consuming alternative, however.
● You can test the configuration.
The basic procedure for configuration varies from case to case. For more information, see:
● Configuring Internal Company Processes
● Configuring Cross-Company Processes
Result
All the information that you create in the Integration Directory at configuration time is available in the caches of the Integration Engine (and the Adapter Engines, if these are involved) for message processing at runtime.