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 - 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.
Publishing and running stubs
You can publish stubs that are created in IBM® Rational® Integration Tester to IBM Rational Test Control Panel, Dockerfile and build context, Kubernetes, or Istio, if the stub is based on a supported transport.
Running stubs
Several methods are available to start and stop the stubs. You can also modify and control stubs while they are running.
Scenarios
In IBM® Rational® Test Control Panel, you can create scenarios, which are collections of configured stubs that can be started and stopped together.
Starting a scenario
After creating a scenario in IBM® Rational® Test Control Panel, you can start it.

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.
  - 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.
    - Rational® Test Virtualization Server overview
      Rational® Test Virtualization Server is software that is used for creating, maintaining, publishing, and running message-based stubs and database stubs.
    - Virtualizing HTTP
      You can simulate an HTTP connection with a virtual service, also known as a stub.
    - Virtualizing HTTPS
      You can simulate an HTTPS connection with a virtual service, also known as a stub.
    - Virtualizing TCP
      You can simulate a TCP connection with a virtual service, also known as a stub.
    - Virtualizing a REST API without recording or synchronization
      You can virtualize REST APIs by using the Recording Studio, or by synchronizing WADL, Swagger, or RAML documents. When none of these options is available, you can still manually virtualize REST APIs that use path parameters.
    - Creating message-based stubs
      In Rational® Integration Tester, there are several methods that you can use to create a message-based stub.
    - Modifying message-based stubs
      You can use either the Test Editor or the Stub Editor to create, modify, and enhance any legacy or new stubs created by Rational® Integration Tester.
    - Creating and modifying database stubs
      You can create and modify database stubs in Rational® Integration Tester.
    - Configuring stubs to connect to Rational® Test Control Panel and the HTTP proxy
      A stub running on its own may not be sufficient in some cases, because it might have dependencies on services such as Rational® Test Control Panel or the HTTP proxy. If the stub is running on the public cloud and the services are running in the enterprise, you must configure the stub to connect to these services.
    - Publishing and running stubs
      You can publish stubs that are created in IBM® Rational® Integration Tester to IBM Rational Test Control Panel, Dockerfile and build context, Kubernetes, or Istio, if the stub is based on a supported transport.
      - Publishing stubs
        You can publish a stub to IBM® Rational® Test Control Panel, Dockerfile and build context, Kubernetes, or Istio with Kubernetes by using the Rational Integration Tester Publish Stubs wizard.
      - Running stubs
        Several methods are available to start and stop the stubs. You can also modify and control stubs while they are running.
        Starting stubs
        IBM® Rational® Test Control Panel, Rational Integration Tester, Docker, or IBM Cloud Private can be used to start stubs.
        Scenarios
        In IBM® Rational® Test Control Panel, you can create scenarios, which are collections of configured stubs that can be started and stopped together.
        Creating a scenario
        You can create a scenario in IBM® Rational® Test Control Panel to control a collection of configured stubs.
        Starting a scenario
        After creating a scenario in IBM® Rational® Test Control Panel, you can start it.
        Modifying a scenario
        You can modify a scenario that is currently running from the Environments Dashboard in Rational® Test Control Panel. You can add stubs to a scenario, modify the stub configuration, delete a stub from a scenario, modify the stub behavior during start of the scenario, rename a scenario, or delete a scenario from the Environments Dashboard.
        Stopping a scenario
        You can stop scenarios that are starting or running in IBM® Rational® Test Control Panel.
        Stopping stubs
        You can use IBM® Rational® Test Control Panel, Rational Integration Tester, or Docker to stop the stubs.
      - Modifying running stubs
        If you are using Rational® Integration Tester to run a stub, you can modify the stub while it is running.
      - Controlling running stubs
        You can control stubs that are running in a number of ways.
      - Behaviors for stubs
        You can create a simple behavior called "echo" that will expose one function and one event for use by a IBM® Rational® Test Virtualization Server stub.
    - Viewing results in Rational® Test Control Panel
      You can use IBM® Rational® Test Control Panel to display the results of tests that you run in both Rational Integration Tester and Rational Test Control Panel.
    - Viewing usage statistics of virtual services in Rational® Test Control Panel
      You can use IBM® Rational® Test Control Panel to display the usage statistics of virtual services across Rational Test Virtualization Server and IBM Rational Integration Tester.
    - Viewing reports in Rational® Test Automation Server
      All the project stakeholders can view test reports for multiple testing products from the Results page on IBM® Rational® Test Automation Server. You can access the Results page from a web browser. Therefore, there is no need to install the desktop client.
    - Troubleshooting: Rational® Test Virtualization Server
      You can use workarounds to common problems that you might encounter when you use IBM® Rational® Test Virtualization Server.
- 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.

Starting a scenario

After creating a scenario in IBM® Rational® Test Control Panel, you can start it.

Before you begin

Optional: To prevent other users from interrupting your testing, lock the environment that you are using. If you lock the currently selected environment, the locked status message is displayed on the Environments Dashboard.

Procedure

Log in to Rational® Test Control Panel.
Click the Environments icon or navigation link.

The Environments Dashboard is displayed.
You can change the domain and environment you want to view by clicking the domain/environment link, and from the domain/environment selection dialog displayed, select the domain, and then select the Environment.

The Environments Dashboard is displayed for the selected environment and domain.
Note: If you are using 8.5.1.1 or later and domain-level security is enabled, you can use only the domains to which you were granted access.
Identify the scenario you want to start.

Note:
You can identify a scenario on the Environments Dashboard from the Start Scenario icon () that is present for a scenario, while the stub can be identified from the Start stub icon () it has.
For the scenario you want to start, click the Start icon () on the Environments Dashboard.

Note: All the stubs that were running when you created the scenario can be seen included under the new scenario.

Results

The scenario starts. The status of the scenario changes from STOPPED to STARTING or RUNNING.

In 8.5.1 or later:

If a scenario tries to start more instances of a stub than there are available agents (for example, four stub instances on three agents), Rational® Test Control Panel displays a message about insufficient agents and problems. If you choose to ignore these problems and continue, the number of stub instances started will equal the number of available agents, which will be less than the number of stub instances saved in the scenario.
If you have multiple subs in a scenario and each stub has multiple instances that are configured to run on multiple agents (for example, two stubs, each with three instances, and configured to run on three agents), Rational® Test Control Panel will start the scenario and not display any messages if the required number of agents is available. This is because separate stubs in a scenario are treated independently of each other and because scaling out applies to multiple stub instances and not to multiple stubs.