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.
Integration 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.
Stopping stubs
You can use IBM® Rational® Test Control Panel, Rational Integration Tester, or Docker to stop the stubs.
Stopping stubs by using the Integration tester method
You can stop stubs using the Rational® Integration Tester method.

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.
  - Integration Tester Reference
    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.
  - Technical Tester Guide
    Typically, a user with the Integration Tester role is also responsible for performance testing. This guide lists all such topics.
  - Integration 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.
    - Task flow: Working with the IBM® Rational® Test Control Panel Environments dashboard
      You can use the Rational® Test Control Panel Environments dashboard to perform various tasks such as starting, stopping stubs and scenarios, and modifying stub configurations after you have published stubs to Rational Test Control Panel. You can also lock the environment that contain the published 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.
        Stopping stubs
        You can use IBM® Rational® Test Control Panel, Rational Integration Tester, or Docker to stop the stubs.
        Stopping stubs by using the Server method
        When you want to stop stubs that are running on IBM® Rational® Test Control Panel, you can stop individual stubs or stop multiple stubs from the Environments Dashboard or Infrastructure Dashboard.
        Stopping stubs by using the Integration tester method
        You can stop stubs using the Rational® Integration Tester method.
        Stopping stubs that are running in a Docker container
        Use the docker stop command to stop stubs that you published to a Docker container.
        Stopping stubs that are running in Istio or Kubernetes
        When you no longer require the stub that is running in an Istio or a Kubernetes deployment, you can delete the virtual service of the stub or delete the complete deployment of the stub.
      - 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 Rational® Integration Tester
  While working with Rational® Integration Tester, you might encounter some problems that you can easily troubleshoot.
- Rational® Integration Tester reference
  Rational® Integration Tester is a scripting-free environment for developing tests for service-oriented architecture (SOA) messaging and business process integration projects. Tests can be built by recording existing system behaviors or from requirements, by entering the data to send and the data that is expected in return.
- 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.

Stopping stubs by using the Rational® Integration Tester method

You can stop stubs using the Rational® Integration Tester method.

To stop a stub, do the following steps:

In Rational® Integration Tester Test Lab perspective, find the stub to stop.
Select the stub and click Stop on the Task Monitor windows toolbar.
Alternatively, select the stub and click Stop on the Task Monitor toolbar.

Stopping a message-based stub causes the following to happen:

If traffic was being routed automatically routed to the stub by means of a Rational® Integration Tester Proxy, the proxy will be configured to resume sending messages to the live system.

Stopping a database stub causes the following to happen:

Rational® Integration Tester instructs each proxy to return to the state it was in before the stub was started.
The simulation schema is cleared.

Note: Stopping a persistent stub updates the stub with a fresh snapshot of data. A non-persistent stub is not updated and, if started again, it will revert to its original state. If there is no connection to the database, exceptions are recorded in a log. In IBM® Rational® Test Virtualization Server, stubs cannot be persistent.