Try OpenEdge Now
skip to main content
Managed Adapters Guide
Sonic ESB Managed Adapter : Working with Sonic ESB Adapter : Defining the dataslot mapping

Defining the dataslot mapping

After configuring the Sonic ESB Adapter, you must define the mapping of your process dataslots to the request and response (if defined) messages. The Dataslot Mapping dialog box displays the mapping parameters depending on the selected message type in the Sonic ESB Adapter Configurator dialog box.
The Request Message tab and the Response Message tab (available only if response message is enabled) contains the following tabs:
*Properties: Contains the input and output property names, which you can map to Source and Target dataslots respectively (as listed in Table 19).
Note: For property type "string," if the mapped CHARACTER dataslot value is null, the property is not included in the request message.
*Body: Available for Multipart, Text, and XML messages.
*For Multipart messages, the tabs contain the message parts, which you can map to Source or Target dataslots.
*For Text and XML messages, the tabs contain the input.message.body and output.message.body parameters, which you can map to Source and Target dataslots respectively.
You do not need to map all the properties and parts (or body) of request and response messages with a dataslot. Those unmapped parameters do not carry any value for request message and their values are ignored for the response message.