You can use Rational® Integration Tester
to record JMS Traffic.
You can record JMS traffic in two ways:
- Subscribe/Browse recording.
- In Rational Integration Tester 8.7.0
and later, using the Client Agent.
The following sections compare and contrast the two approaches.
Recording JMS by using the Client Agent
You can record JMS flows at the transport level or at the operation level.
- By default, all JMS queues or topics that are associated with
the JMS application are recorded. You can filter queues or topics
by specifying a queue or topic prefix on the Recording
Studio tab of the JMS Domain in
the Logical View of the Architecture School perspective.
- Recording is achieved using the Client Agent:
The Java™ virtualization agent.
- Both JMS 1.1 and JMS 2.0 applications are supported.
- The JMS application must be using Java version
6 or above.
- The Client Agent does not take part in XA transactions.
In some circumstances, the Client Agent might still send messages
if the outer transaction is rolled back.
- Messages that the client code receives will be recorded, regardless of manual acknowledgment or
auto acknowledgment. With manual acknowledge, if a message is redelivered, it is shown twice in
Recording Studio.
Recording JMS by using Subscribe/Browse
In
releases of
Rational Integration Tester that
are earlier than 8.7, you can record JMS with restrictions:
- Recording occurs at the operational level. Specifically recording
occurs against the queue or topic that is specified under JMS
Headers in Message Exchange Pattern on
the operation as defined in the Logical View of the Architecture School
perspective.
- Recording is achieved when Rational Integration Tester Recording
Studio directly browses a queue or subscribes to a topic.
- Both JMS 1.1 and JMS 2.0 applications are supported.
- These JMS Providers are supported:
- Fiorano MQ
- IBM® WebSphere® MQ
- Oracle OC4J (Application Server)
- Oracle OC4J (BPEL)
- Solace
- TIBCO
EMS
- WebLogic JMS Thick
- WebLogic JMS Thin
- webMethods JMS, Versions 6.5, 7.1, 8.0, 8.2.
For detailed information about how to record JMS traffic,
see these topics :