Home
Tester Guide
This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing.
Tester Guide - Performance Testing
Typically, a user with the Integration Tester role is also responsible for performance testing. This guide lists all such topics.
Deploying probes
A Rational® Integration Tester probe measures variables from a particular component in the system and reports back its findings for processing and storage.

Tester Guide
This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing.
- Tester Guide - Integration Testing
  This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing. This guide is intended for Integration testers.
- Tester Guide - Performance Testing
  Typically, a user with the Integration Tester role is also responsible for performance testing. This guide lists all such topics.
  - Creating and running performance tests
    This topic describes how to create, configure, and run performance tests.
  - View test results
    This topic describes how to work with IBM® Rational® Performance Test Server charts in the Results Gallery perspective.
  - Deploying probes
    A Rational® Integration Tester probe measures variables from a particular component in the system and reports back its findings for processing and storage.
    - System statistics probe
      The System Statistics (Systat) probe runs on Windows™ or Linux™ and captures key system statistics for the target host.
    - Windows™ performance monitor probe
      The Windows™ Performance Monitor probe captures the same statistics for the target host as those available through the Performance Monitor (perfmon.msc) on Windows systems.
    - TIBCO BusinessWorks probe
      The TIBCO BusinessWorks (BW) probe accesses the TIBCO Hawk microagents within BusinessWorks to collects execution statistics from running BusinessWorks processes.
    - TIBCO Rendezvous probe
      The TIBCO Rendezvous (RV) probe captures Rendezvous daemon (RVD) status messages that contain messaging and error rates.
    - TIBCO Rendezvous distributed queues probe
      The TIBCO Rendezvous Distributed Queues (RVDQ) probe uses Rendezvous daemon (RVD) transports to collect RV Distributed Queue statistics.
    - TIBCO Rendezvous trace probe
      The TIBCO Rendezvous Trace (RVTRACE) probe uses the TIBCO program rvtrace to monitor networks and capture Rendezvous daemon (RVD) subject statistics.
    - TIBCO EMS probe
    - webMethods Broker probe
      The webMethods Broker probe collects statistics for webMethods brokers, event types, clients, and client groups.
    - webMethods Integration Server probe
      The webMethods Integration Server probe collects statistics for the server and for specific webMethods services.
    - Handling probe errors
- Tester Guide - Service Virtualization
  This guide describes the tasks that you can perform for using virtual services or stubs to simulate parts of an environment if the real services are not yet available or because they are difficult or expensive to use. This guide is intended for Integration Testers.

Deploying probes

A Rational® Integration Tester probe measures variables from a particular component in the system and reports back its findings for processing and storage.

Probes are started by the agent on the local computer. Therefore, the agent software must be installed on that computer. More than one probe may be run from the same agent, but only one performance test controller at a time can use the probes of an individual agent.

The probe process will terminate if it cannot contact the performance test controller that started it by means of the agent. For Windows™ users, the probe process name is Probe.exe. For Unix-like system users, the probe process is a Java™ process that may be identified by using long ps output.

The probe process configuration file is Probe.config, which is located in Agent_installation_directory\config. This file can be edited to configure the level and location of the logging.