When you are investigating a problem, you might need to
find where the message points for a destination are located.
About this task
You may need to perform this task as part of problem determination,
to find out on which messaging engine a message point is located.
Note: If
you have an alias destination, the alias is resolved to the physical
destination immediately after a message is produced. You can use this
task to find the physical destination.
Procedure
Click Service integration -> Buses -> bus_name -> [Additional
Properties] Destinations to display the destinations on the
relevant bus. Review the Type of the destination:
- If the destination is a queue, the queue point name has the form destination@messaging_engine_name.
- If the queue is localized to a
cluster, there is one queue point for every messaging engine in the
cluster.
- If the queue is localized to a
cluster, there is one queue point for every messaging engine in the
cluster.
A mediated queue has at least one mediation point. If the queue is localized to a cluster,
there is one mediation point for every messaging engine in the cluster.
- If the destination is a topic space, it will have a publication
point localized to every messaging engine in the bus. When a topic
space is not mediated, service integration delivers messages directly
to the publication point situated on the same messaging engine that
the producing application is connected to. When the topic space is
mediated, in the same way as a queue, service integration directs
messages to the mediation point or points and then to the publication
point that is co-located with that mediation point.
What to do next
If the destination is a queue with multiple queue points,
or it is mediated using multiple mediation points, perform the problem
determination for each message point that the message could have been
sent to or consumed from.