Try OpenEdge Now
skip to main content
Managed Adapters Guide
JMS Managed Adapter : Working with the JMS Adapter : Defining mapping with the Mapping Configurator

Defining mapping with the Mapping Configurator

When the JMS Adapter configuration, inputs, and outputs are defined, the mapping to actual dataslots is performed through the Mapping Configurator. The Mapping Configurator may look differently, depending on the way you configured the JMS Adapter. Generally, for a send/receive configuration, the Mapping Configurator has an Incoming Message tab, an Outgoing Message tab, and a Runtime Setup tab that allows you to map such additional parameters as Correlation ID and, optionally, other parameters that had been left empty during JMS Adapter configuration.
The Outgoing Message mapping tab includes two tabs used to map dataslots or constant values into the outgoing message body (payload) fields and header. Note that in order to generate the message successfully, you must map all of the fields in the Outgoing Message tab. Otherwise, the message cannot be constructed properly and you may get an error message while executing the JMS Adapter.
Similarly, the Incoming Message mapping tab also includes two tabs, where data from the response payload and header is mapped back to dataslots.
The last tab–Runtime Setup,–includes any additional run-time configuration that may be needed.
One such parameter is the Correlation ID. In certain situations (as described in the next section), the Correlation ID may need to be obtained from a dataslot, or the automatically generated ID may need to be stored in a dataslot for future use. You can define this mapping in the Runtime Setup tab.