To be able to implement the process specified in the ES Repository in a specific system landscape, you must first configure it.
In this section it is assumed that the components of your process communicate with each other using an Integration Server or an Advanced Adapter Engine. You specify during the configuration which of these Integration Brokers you want to implement.
You execute the following tasks for the configuration:
Define Collaboration Profile
You initially model the units that are to be addressed as the sender or receiver of messages in the communication profile. You define communication parties and communication components for this purpose. To define the technical communication paths for the communication party and the communication components you define communication channels. You configure the adapters for inbound and outbound processing in the communication channels.
You execute these tasks in the SLD and the Integration Directory.
More information: Define Collaboration Profile
Configuring Communication
In this step you basically define how messages are processed by the Integration Server or Advanced Adapter Engine and how they are forwarded on to the receiver systems involved. In detail, you specify:
The inbound processing of the message at the Integration Server or Advanced Adapter Engine
The routing of the message from the Integration Server or Advanced Adapter Engine to the receiver systems and interfaces involved
The outbound processing of the message
Security settings for exchanging messages (for example, message encryption)
The exact procedure is determined by whether you use the Integration Server or Advanced Adapter Engine for processing messages.
More information:
Publishing services for calling the Integration Broker to the Services Registry
Using the configuration of the inbound processing you define how the message calls the Integration Broker as a service. To make it easier for the senders of messages (service consumer) to call the Integration Broker, you can publish the relevant configuration objects for each of them to the Services Registry.
More information:
Publishing Sender Agreements to the Services Registry (for communication using the Integration Server)
Publishing Integrated Configuration to the Services Registry (for communication using the Advanced Adapter Engine)
For more information about the Integration Directory, see Integration Directory.
To configure the integration of external business partners based on industry standards, orientate yourself according to the procedure described above. There are additional concepts and tasks for the B2B integration.
More information: Configuring B2B Integration
You can integrate smaller business partners and subsidiaries using the SAP Partner Connectivity Kit (PCK). In the PCK, you can configure the required process integration content and the technical adapters.
More information: Working with PCK
Example
For a configuration example, see Configuration Example for Message Exchange.
To be able to implement the following special application cases, you must take the procedure described above into account and some other additional activities. These are described below.
Implementing and Executing XML Validation
More information: XML Validation