This topic explains how you can use SOAtest to monitor transactions that pass through a TIBCO EMS system, then generate functional test cases that check the monitored messages.
Sections include:

Overview

SOAtest can monitor transactions that pass through TIBCO EMS, then generate functional test cases that check the monitored messages. In addition to providing visibility into the system’s messages, this allows you replay transactions directly from SOAtest and verify that the monitored functionality continues to work as expected.

To achieve this, you tell SOAtest how to connect to your TIBCO EMS and what destination (topic or queue) messages you want it to monitor, then you prompt it to start monitoring.  SOAtest will generate a test suite of Messaging Client tests for each JMS message captured at the specified destination or for all messages within the process flow (if a process tracking topic was used). These tests are preconfigured with the connection parameters, requests, and destination information so that SOAtest can replay the same messages.

SOAtest can generate test clients for the following types of JMS messages:

• javax.jms.TextMessage
• javax.jms.MapMessage
• javax.jms.ObjectMessage
• javax.jms.BytesMessage
• javax.jms.StreamMessage

Prerequisites

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

Generating Tests from TIBCO EMS Transactions

To generate tests:

1. Choose the Other> TIBCO Enterprise Messaging Service option in one of the available test creation wizards. For details on accessing the wizards, see:
   • Adding a New .tst File to an Existing Project
   • Adding a New Test Suite
2. Complete the first page of the TIBCO EMS wizard as follows:
   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
        $sys.monitor.Q.r.>
      • 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 mes-sages 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.

   6. In the JNDI properties table, specify any additional JNDI properties you want applied to this deployment

       

3. Click Next. SOAtest will start monitoring the messages that match the settings specified in the previous wizard page. If you run another application that sends messages to the bus, those messages will be noted in this panel.
4. When you are ready to stop monitoring, click Finish. SOAtest will then create test cases based on the verified messages.