Home
Rational® Integration Tester
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.
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.
Logging measurements to the results database
You might want to periodically record custom data in to a database as a performance test runs.
Modifying counter-limits
Each item of data that is recorded is called a counter. By default, the number of counters is limited to eight REAL and four STRING. You might want to increase the number of counters and can do so by modifying a table definition in the database creation script.

Rational® Integration Tester
- Release Notes
  This document contains information about What's new, installation, known issues, and contact information of IBM Support.
- System Requirements
  This document includes information about hardware and software requirements for IBM® Rational® Integration Tester.
- Getting Started
  This guide provides an overview and describes the tasks to get you started with Rational® Integration Tester.
- Administrator Guide
  This guide describes how to install Rational® Integration Tester. After you install the software, you can perform administration tasks such as configuration and integration of the product. This guide is intended for administrators.
- 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.
        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.
        Logging measurements to the results database
        You might want to periodically record custom data in to a database as a performance test runs.
        Modifying counter-limits
        Each item of data that is recorded is called a counter. By default, the number of counters is limited to eight REAL and four STRING. You might want to increase the number of counters and can do so by modifying a table definition in the database creation script.
        Modifying attribute-limits
        Attributes identify the data that is stored by the counters. By default, the number of attributes is limited to five. You might want to increase the number of attributes and can do so by modifying a table definition in the database creation script.
        Example: Logging measurements to the results database
        In this example, you use a background test and the log measurement action to act as a custom probe for the system under test.
      - 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.
- Test Manager Guide
  This guide describes the tasks that you can perform for tracking the quality of the application. This guide is intended for Test Managers.
- Troubleshooting
  While working with Rational® Integration Tester, you might encounter some problems that you can easily troubleshoot.
- Reference Guide
  This guide provides the topics to help the Integration tester use the product by using the user interface, commands or scripts. This guide is intended for Integration testers.
- Security Considerations
  You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
- Notices
  This document provides information about copyright, trademarks, terms and conditions for product documentation.

Modifying counter-limits

Each item of data that is recorded is called a counter. By default, the number of counters is limited to eight REAL and four STRING. You might want to increase the number of counters and can do so by modifying a table definition in the database creation script.

About this task

To modify counter-limits:

Procedure

If your results database connection is valid, Rational® Integration Tester silently queries the counter-limits. If the limits are exceeded, invalid rows are shown in red and no rows can be edited until the extra ones are removed.

You can increase the number of counters by modifying a table definition in the database creation script.

The example that is shown is from the Oracle create script. (Some lines of SQL are omitted for brevity.)

The CTR_ID_9 and STRCTR_ID_5 entries show the lines that must be added to increase the number of REAL and STRING counters by one.


CREATE TABLE "LOGMEASUREMENT_TS"(
    "IDX"                    NUMBER(19, 0)    NOT NULL,
    "LOGMEASUREMENT_MRV_ID"  NUMBER(19, 0)    NOT NULL,
    "EXECUTION_ID"           NUMBER(19, 0),
    "TIME"                   NUMBER(20, 0)    NOT NULL,
    ...
    "CTR_ID_8"               NUMBER(19, 0),
    "CTR_VAL_8"              NUMBER(20, 3),
    "CTR_ID_9"               NUMBER(19, 0),
    "CTR_VAL_9"              NUMBER(20, 3),
    ...
    "STRCTR_ID_4"            NUMBER(19, 0),
    "STRCTR_VAL_4"           VARCHAR2(255),
    "STRCTR_ID_5"            NUMBER(19, 0),
    "STRCTR_VAL_5"           VARCHAR2(255),
    FOREIGN KEY ("EXECUTION_ID")
    REFERENCES "EXECUTION"("ID") ON DELETE CASCADE,
    FOREIGN KEY ("LOGMEASUREMENT_MRV_ID")
    REFERENCES "LOGMEASUREMENT_MRV"("ID") ON DELETE CASCADE,
    FOREIGN KEY ("CTR_ID_1")
    REFERENCES "COUNTER_DETAILS"("ID") ON DELETE CASCADE,
    ...
    FOREIGN KEY ("STRCTR_ID_4")
    REFERENCES "COUNTER_DETAILS"("ID") ON DELETE CASCADE,
    FOREIGN KEY ("CTR_ID_9")
    REFERENCES "COUNTER_DETAILS"("ID") ON DELETE CASCADE,
    FOREIGN KEY ("STRCTR_ID_5")
    REFERENCES "COUNTER_DETAILS"("ID") ON DELETE CASCADE,
)
;

Important: You can increase the table sizes even if the results database contains data. If you need help, consult your local database administrator (DBA).