The objective of this post to demonstrated all the relevant common ESR objects required to establish a simple PI mapping. This simple PI mapping will map source message with 2 fields (firstname and lastnam) to target message (fullname).
Here are brief explanation and my views for each ESR object types:
Object Type | Object Name |
---|---|
Data Types | Represent the underlying basic data structure of message The elements of data types can be primitive type like string, integer, or nested another data types |
Message Types | Represent the message structure to be used in message mapping One message type can consist of multiple data types |
Service Interfaces | Represent the message types with direction The direction can be Outbound,Inbound or Abstract |
Message Mapping | Represent collection of rules to transform source message type to target message type Input is source message type(s), output is target message type(s) |
Operation Mapping | Represent a single unit of transformation consist of service interfaces and message mapping(s) Number of message mapping can be single, multiple or none |
For this example, below are the ESR objects involved:
Object Type | Object Name |
---|---|
Data Types | DT_FIRSTNAME_LASTNAME DT_FULLNAME |
Message Types | MT_FIRSTNAME_LASTNAME MT_FULLNAME |
Service Interfaces | SI_FIRSTNAME_LASTNAME_OUT SI_FULLNAME_IN |
Message Mapping | MM_FIRSTNAME_LASTNAME_TO_FULLNAME |
Operation Mapping | OM_FIRSTNAME_LASTNAME_TO_FULLNAME |
Source data type and target data type:


Source message type and target message type:


Outbound service interface and Inbound service interface:


Message mapping using concat function to combine two strings, separated by a blank character:

Test run the mapping, input “John” as first name, “Locke” as last name. The result string is “John Locke”

Operation mapping:

Pingback:Handle Empty Context with mapWithDefault – Integration Learn