This topic explains how to configure monitoring for any JMS system.

To configure the Event Monitor tool to monitor any JMS system:

  1. Double-click the Event Monitor tool to open up the tool configuration panel.
  2. In the Event Source tab, select Generic JMS system as the platform, then configure the following options:
    1. In the Connection area, specify your connection settings.
    2. In the Initial Context field, specify a fully-qualified class name string, passed to the JNDI javax.naming.InitialContext constructor as a string value for the property named javax.naming.Context.INITIAL_CONTEXT_FACTORY.
    3. In the Connection Factory field, specify the JNDI name for the factory. This is passed to the lookup() method in javax.naming.InitialContext to create a javax.jms.QueueConnectionFactory or a javax.jms.TopicConnectionFactory instance.
    4. In the Destination Name field, specify the topic or queue that you want to monitor.
      • You can specify a regular topic or queue (e.g., the entry or exit of a workflow process), or a special process tracking topic.
    5. In the Destination Type field, specify whether the tracking destination is a topic or a queue.
    6. (Optional) In the Message Selector field,  enter a value to act as a message filter. See Using Message Selector Filters for tips.
    7. If you want SOAtest to use the JMS QueueBrowser API in order to trace messages posted on a JMS queue— without removing them from the queue— enable the Leave messages on the queue option. This allows SOAtest to gain visibility into these messages without impacting the transaction.

      Caution: Leave messages on the queue

      For a discussion of potential complications with this option—and how to avoid them—see JMS Queue Options.

    8. If you want any additional JNDI properties applied to this deployment, specify them in the JNDI properties table.
  3. In the Options tab, modify settings as needed.