The Enterprise Gateway can add HTTP headers to a message as it passes through a
policy. It can also set a (Base64-encoded) value for the header.
For example, you can use the Add HTTP Header filter to add
a message ID to an HTTP header. This message ID can then be forwarded to
the destination Web Service, where messages can be indexed and tracked by
their IDs. In this way, you can create a complete audit trail
of the message from the time it is received by the Enterprise Gateway, until it is
processed by the back-end system.
Each message being processed by the Enterprise Gateway is assigned a unique transaction
ID, which is stored in the id message attribute. You can use the
${id} property to represent the value of the unique message ID.
At runtime, this property is expanded to the value of the id message
attribute.
|