Database Reference
In-Depth Information
Monitoring JMS destinations
More often than not, many of the integrations that run on top of Oracle SOA
Suite 11g may leverage JMS destinations to support asynchronous integrations.
These destinations can be JMS queues (for point-to-point integrations) or JMS
topics (for publish-subscribe integrations). Oracle WebLogic Server 11g
provides a way to easily create these JMS destinations that become accessible
via a JNDI in the code.
As an administrator, you must be aware of all queues and topics created, as
there are many reasons why you would want to monitor them:
•
Ensure that messages in the queues and topics are being produced and con-
sumed without error and/or delay.
•
Ensure that poison messages, ones that have exceeded the maximum num-
ber of delivery attempts, do not remain in the queue or topic.
To monitor your JMS destinations:
1.
Log in to the Oracle WebLogic Administrator Console.
2.
Click on
JMS Modules
.
3.
Click on the JMS module name that is hosting your queue/topic.
4.
Click on the queue or topic name.
5.
Click on the
Monitoring
tab. Here you will see a summary of statistics re-
garding your JMS destination such as current, pending, and total messages.
6.
If the JMS destination already has subscribers, click on the checkbox beside
your destination name, then click on the
Show Messages
button. From here,
you can export some or all of the messages to an XML file, if you choose
to (for either backup purposes or with the intention of importing them into a
different environment).
7.
Click on the JMS
Message ID
. The following screenshot displays the result
of this. Details of the message are displayed as part of the JMS header, in-
cluding ECID, composite instance ID, as well as the payload of the message:
