This topic explains how to configure monitoring for TIBCO EMS.

Sections include:


The tibjms.jar file must be added to your classpath (via Parasoft> Preferences> Parasoft> System Properties).


To configure the Event Monitor tool to monitor messages that pass through TIBCO EMS:

  1. Double-click the Event Monitor tool to open up the tool configuration panel.
  2. In the Event Source tab, select TIBCO Enterprise Message Service as the platform, then configure the following options:
    1. In the Connection area, specify your TIBCO EMS connection settings.
    2. 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 .
      • For instance, to track any JMS message that gets transmitted through TIBCO EMS, use

      • For details on specifying tracking topics for TIBCO EMS, see "Chapter 13: Monitoring Server Activity" and "Appendix B: Monitor Messages" in the TIBCO EMS User’s Guide.

    3. In the Destination Type field, specify whether the tracking destination is a topic or a queue.
    4. (Optional) In the Message Selector field,  enter a value to act as a message filter. See Using Message Selector Filters for tips.
    5. 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.

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

    6. 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.