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.
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.
Starting stubs
IBM® Rational® Test Control Panel, Rational Integration Tester, Docker, or IBM Cloud Private can be used to start stubs.
Starting stubs by using the Integration Tester method
Rational® Integration Tester can be used to start stubs, but IBM® Rational Test Control Panel provides more control over the startup of a stub or a set of stubs.

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.
- 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.
        Starting stubs by using the Server method
        When you want to start stubs that are published to IBM® Rational® Test Control Panel, you can do so from the Environments Dashboard. Also, when you cannot use or access Rational Integration Tester to control stubs, you can use the Environments Dashboard of Rational Test Control Panel to start the stubs.
        Starting stubs by using the Integration Tester method
        Rational® Integration Tester can be used to start stubs, but IBM® Rational Test Control Panel provides more control over the startup of a stub or a set of stubs.
        Running stubs in a Docker container
        After you publish one or more stubs to a Dockerfile and build context and you built a Docker image from those files, you use the docker run command to run the image in a container.
        Running stubs in Istio or Kubernetes
        After you publish one or more stubs to Istio or Kubernetes, you must upload the project files to a file server and edit the YAML file to point to the URL of the file server before you can run the 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.
    - 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.

Starting stubs by using the Rational® Integration Tester method

Rational® Integration Tester can be used to start stubs, but IBM® Rational® Test Control Panel provides more control over the startup of a stub or a set of stubs.

Procedure

To start a stub:

In Rational® Integration Tester Test Lab perspective, find the stub that you want to start.
Right-click the stub and click Run on the shortcut menu.
Alternatively, select the stub and click Run on the Task Monitor windows toolbar.

Note: If you want to run all stubs for a particular operation, right-click the operations Stubs folder and then click Run All > Stub on the shortcut menu.

Results

Starting a message-based stub causes the following things to happen:

The Test Lab perspective Console window displays progress of the stubs startup and messages from the stub as it runs. If the stubs log level has been set to Debug, you will be able to view detailed information about what the stub is doing. (For information about setting a stubs log level, refer to Starting stubs by using the IBM Rational Test Control Panel method.)
The stub will start listening on queues and ports.
If proxies are being used, traffic will be routed to the stub automatically.

Note: For information about restrictions on stubs started by Rational® Integration Tester, refer to Starting stubs.

Starting a database stub causes the following to happen:

The data contained in the stub is loaded into the simulation database.
The Rational® Integration Tester JDBC proxy is switched to simulate mode, which affects the system under test but not Rational® Integration Tester, and all interactions between the system under test and the live database are directed to the stub. (For information about simulate mode, refer to Creating and modifying database stubs.)
The Test Lab perspective Console window displays progress of the stubs startup.

Note: If you are using Rational® Integration Tester 8.0.1 (or later), clicking default case console output or failed validation console output on the Console window opens the Message Differences window, which enables you to debug the stub. (For information about debugging a stub, refer to Debugging Message-Based Stubs. For general information about the Message Differences window, see Rational Integration Tester reference.)