Metadata mapping for split file content
Last updated
Last updated
When splitting file contents into JMS messages, file metadata can be propagated as JMS Headers and JMS Properties.
A subset of system metadata can be automatically mapped to JMS Properties. Custom metadata can be mapped to JMS Headers and/or to JMS Properties.
This subset of system metadata can be automatically mapped to JMS Properties:
DFIID, Filename, Virtual Path, VFS
To map system metadata to JMS Properties, when configuring the output contract action, set the toggle to on.
The DFIID, Filename, Virtual Path and VFS subset of system metadata will appear as Properties in the JMS provider.
Custom metadata can be mapped to JMS Headers and/or to JMS Properties.
To map metadata to JMS Headers, note that:
The file metadata name must be JMS_header_<name>.
<name> must be one of the following:
JMSCorrelationId
JMSDeliveryMode
JMSDeliveryTime
JMSDestination
JMSExpiration
JMSMessageID
JMSPriority
JMSRedelivered
JMSReplyTo
JMSTimestamp
JMSType
E.g., JMS_header_JMSCorrelationId = 1234 sets the JMSCorrelationId header to 1234
To map metadata to JMS Properties, note that:
The file metadata name must be JMS_property_<customName>
E.g., JMS_property_orderId = 1234
To set custom metadata to JMS Headers and/or JMS Properties, a specific workflow must be designed and a Mediation contract must be set to use the workflow.
The workflow must have as many Set Metadata service tasks as the metadata that will be associated with the file and with queue messages.
In the workflow above, the SetJMSCorrIdMetadata service task sets the JMS_header_<name> metadata where <name> must be one of the options listed above.
The SetJMSCorrIdMetadata service task shown above is configured as follows:
Name [String]: JMS_header_JMSCorrelationId
Value [String]: correlationID
The SetJMSOrderMetadata service task sets the JMS_property_<customName> custom metadata and is configured as follows:
Name [String]: JMS_property_order
Value [String]: 1234
Custom metadata will appear as Headers and Properties in the relevant sections of the JMS provider.
