In a mediated communication step of an integration scenario, the sender normally uses a data format and structure for sending out a message that is different to the one that the receiver can handle. Therefore, the data structure and format used by the sender must be transformed into the structure and format that the receiver can handle. This type of transformation is called mapping . You specify the corresponding transformation rules in the ES Repository - in the form of mapping objects.
More information: Mapping Objects
Defining Mappings
These are the steps to define a mapping:
Tasks at Design Time
Implement the mapping using one of the available kinds of mapping programs.
For an overview of the supported types of mapping programs, see Mapping Programs
The ES Repository provides a graphical editor to design mappings intuitively. Mappings designed with the graphical editor are called message mappings .
More information:
In the ES Repository, create an operation mapping for a pair of source and target interface operation.
More information:
Assign the mapping program to the operation mapping.
Activate the mapping objects you have created.
Tasks at Configuration Time
To configure mapping, you need to select an operation mapping from the ES Repository for a specific communication step. You do this in the Integration Directory in an interface determination or in integrated configuration object depending on the chosen connectivity option.
More information: Defining an Interface Determination
Defining the Integrated Configuration
To specify the mapping, choose the Receiver Interfaces tab.
Applying Advanced Mapping Techniques
More information: Applying Advanced Mapping Techniques
Processing Mappings at Runtime
The Process Integration runtime executes the mappings configured in the Integration Directory at runtime after receiver identification has taken place. If no mapping is required for a connection then the Process Integration runtime skips the mapping step.