Use the Recording Studio to monitor and capture events,
and use captured events for tests and other artifacts for use within
your IBM® Rational® Integration Tester project.
Capturing events
You can use the Recording Studio to capture events. The
Events View can be used with the Event Monitors view to select events
and record them. You can define the destination for recorded events
by using tags in the message header properties of selected operation.
Recording HTTP and HTTPS traffic
Use the HTTP proxy in the IBM Rational Test Control Panel to
record all HTTP and HTTPS traffic that is routed through the proxy.
Recording TCP traffic
The IBM Rational Integration Tester HTTP/TCP
proxy enables Rational Integration Tester to
record general TCP traffic that is routed through the proxy or to
route TCP traffic to stubs automatically when they start instead of
routing traffic through the live system.
Recording MQ telemetry traffic
The HTTP/TCP proxy enables IBM Rational Integration Tester to
record MQ telemetry transport traffic that is routed through the proxy.
Recording WebSphere MQ and TIBCO EMS Server events
Recording for WebSphere® MQ transports
is carried out in a different way than other transports. The WebSphere MQ transport
does not provide a native method for watching a queue in a non-destructive
manner. In other words, events cannot be captured without taking them
off the queue.
Recording and virtualizing RFCs
You can record and virtualize SAP application resources.
If you are testing a Java™ application
that uses the SAP Java Connector
(JCo) to make remote function calls (RFCs) to an SAP application server,
use IBM Rational Integration Tester to
record and virtualize those calls.
Configuring the Recording Studio settings of logical SAP application servers
You can record SAP application resources by configuring
a logical SAP application server to record IDocs. Use the Recording
Studio perspective of IBM Rational Integration Tester to
record incoming and outgoing intermediate documents (IDocs).
Configuring subscribe operations to record IDoc types
You can record and virtualize SAP application resources
by creating a subscribe operation for a logical SAP application server
and configuring it to record a specific IDoc type.
Creating event monitors for SAP recordable resources
After configuring the Recording Studio settings of a logical
SAP application server to record intermediate documents (IDocs) or
configuring a subscribe operation for a logical SAP application server
to record IDoc types, you must create an event monitor in Recording
Studio before you can start a recording session.
Recording SQL events
When the Rational Integration Tester JDBC
proxy is installed, you can use Rational Integration Tester and IBM Rational Test Virtualization Server to
record SQL events that are executed against databases from applications
that use JDBC. There are two methods of selecting a database for recording:
Architecture School method and Recording Studio method. Both methods
achieve the same result but the Architecture School method is a more
direct method.
Recording FIX traffic
Use IBM Rational Integration Tester and
an HTTP/TCP proxy to record FIX traffic.
Recording Java method calls
To record Java method
calls, you use the Java application
that you want to record, an instance of the Java virtualization agent or the Java virtualization proxy as applicable installed
into the application, and a Java method
transport in IBM Rational Integration Tester.
Playing back recorded events
You can select recorded events and replay them in the Recording Studio
perspective. You can specify the "pacing" speed with which the messages are published
(as-fast-as-possible, defined interval, or as-original). Rules and functions in the Rules
Cache can be used to make basic modifications to message contents as they are published.
Playback works on events that have been exported and re-imported.