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.
Creating and running performance tests
This topic describes how to create, configure, and run performance tests.
Creating performance tests
A performance test is created within a Rational® Integration Tester project.
Adding distributed tests
You can add distributed tests to a performance test.
Test engines
Test engines are instances of Rational® Integration Tester that execute performance tests.
Creating test engines
You can configure additional test engines on a single agent to run multiple tests simultaneously.

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.
    - Before creating performance tests
      Agents (Rational® Integration Tester Agent) are required on the computers that will run IBM® Rational Integration Tester tests and the probes that monitor the systems.
    - Creating performance tests
      A performance test is created within a Rational® Integration Tester project.
      - Execution
        Select the root of the performance test in the configuration tree to display its configuration details, as shown below.
      - Configuring references
        You can configure a performance test to run scenarios, which are collections of stubs, that are available on the IBM® Rational® Test Control Panel domain associated with your Rational Integration Tester project.
      - Configuring probes
        The Probes tab (on the Config tab) is used to configure which probes to run during the test, and where to run them.
      - Adding distributed tests
        You can add distributed tests to a performance test.
        Configuring execution options
        On the Execution tab, you can modify the name of the selected test as well as the Rational® Integration Tester test that it should run.
        Load-generating tests
        If the load profile for the selected test is Constant Growth, the execution parameters will be defined in this topic and the number of test phases and their duration are fixed.
        Background tests
        A background test simply runs the selected test repeatedly while the performance test is active.
        Test engines
        Test engines are instances of Rational® Integration Tester that execute performance tests.
        Creating test engines
        You can configure additional test engines on a single agent to run multiple tests simultaneously.
        Linking test engines to tests
        This topic explains how to link engines to tests.
        Configuring input mappings
        On the Input Mappings tab, you can map values from a selected test data set to the tags in your test.
        Descriptions/notes
        On the Documentation tab, you can enter a description or notes about the selected test, and specify the test’s owner.
        Timed sections
        When tests are run within a distributed test in IBM® Rational® Performance Test Server, the overall execution times (that is, start to finish) are recorded.
      - Log Measurement action (optional)
        With the Log Measurement action, you can periodically record custom data, that is, data that is not provided by test engines and probes, as a performance test runs. The recorded data is stored in a database and is used to generate performance charts. Each item of data that is recorded is called a counter. Attributes are used to identify the counters. A UTC time stamp is stored with each set of counters.
    - Performance tests
      Performance tests are executed in Rational® Integration Tester in the same way and from the same perspectives as any other test resource.
    - Troubleshooting: Running a performance test with a MySQL database
      You can troubleshoot an issue that you encounter while you run a performance test with a MySQL database.
  - 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.
- 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.

Creating test engines

You can configure additional test engines on a single agent to run multiple tests simultaneously.

About this task

To create a test engine:

Procedure

Double-click an existing agent in Architecture School Physical View.
Click Add (to add another test engine).
Alternatively, click Rename to rename the selected engine or click Delete to delete the selected engine.

Note: The rename check is case-insensitive. If you only change the capitalization of the resource name, the OK button in the Rename dialog is not enabled.
Enter a name for the new test engine when prompted.
Note: When you create a new test engine, the default instance is disabled.
Click OK to close the dialog and save your changes.
Note: The Agent.config file (which is located in <Rational® Integration Tester Agent installation directory>\config) must be modified to include the engine names listed in the GUI.