Message construction patterns describe the possible actions that can be performed on messages as they pass through a system. The only formally defined pattern supported by FUSE Mediation Router is the correlation identifier pattern.
The correlation identifier pattern, shown in Figure 4.1, describes how to match reply messages with request messages, given that an asynchronous messaging system is used to implement a request-reply protocol. The essence of this idea is that request messages should be generated with a unique token, the request ID, that identifies the request message and reply messages should include a token, the correlation ID, that contains the matching request ID.
FUSE Mediation Router supports the Correlation Identifier from the EIP patterns by getting or setting a header on a Message.
When working with the ActiveMQ or JMS components, the correlation identifier header is
called JMSCorrelationID
. You can add your own correlation identifier to
any message exchange to help correlate messages together in a single conversation (or
business process). A correlation identifier is usually stored in a FUSE Mediation Router message header.