What trace-route messaging is used for
The information recorded using trace-route messaging can be used in the
following ways:
- To determine the last known location of a message
- If a message does not reach its intended destination, trace-route messaging
can be used to help determine the last known location of the message. A trace-route
message is sent into a queue manager network with the same target destination
as the original message, in the hope that it will follow the same route. Activity
information can be accumulated in the message data of the trace-route message,
or recorded using activity reports. To increase the chance that the trace-route
message will follow the same route as the original message, the trace-route
message can be modified to mimic the original message, see Mimicking a message.
The activity information recorded for a trace-route message can be used to
determine the last known location of the original message.
- To determine configuration issues with a queue manager network
- Trace-route messages are sent into a queue manager network and activity
information is recorded. By studying the activity information recorded for
a trace-route message, it can become apparent that the trace-route message
did not follow the expected route. There are many reasons why this can occur,
for example, a channel could be inactive forcing the message to take an alternative
route. In these situations, a system administrator can determine whether there
are any problems in the queue manager network, and if there are, correct them.
Notes:
- Trace-route messages can be configured, generated, and put in to a queue
manager network using the WebSphere MQ display route application, see WebSphere MQ display route application.
- If you put a trace-route message to a distribution list, the
results are undefined.