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.
Controlling running stubs
You can control stubs that are running in a number of ways.
Locking and unlocking environments
Locking a IBM® Rational® Test Control Panel environment prevents other users from starting or stopping stubs in that environment.

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.
      - 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.
        Locking and unlocking environments
        Locking a IBM® Rational® Test Control Panel environment prevents other users from starting or stopping stubs in that environment.
        Locking an environment in IBM® Rational® Test Control Panel
        When you lock an environment, you can continue to use the environment but other users cannot make any changes to it.
        Unlocking an environment
        You can unlock an environment in IBM® Rational® Test Control Panel.
        Viewing broken stub messages
        On IBM® Rational® Test Control Panel Environments Dashboard page, if a stub fails to start (irrespective of from where the stub is started) and displays a Broken state, placing your mouse pointer over the stub displays a message about the possible cause for the Broken state. See the Agent logs for more details of the cause.
        Viewing stub logs
        IBM® Rational® Test Control Panel enables IBM Rational Test Virtualization Server users to view the console output of stubs that ran in the selected domain and environment.
        Query Docker container logs
        You can use the docker logs commands to query Docker container logs.
        Debugging message-based stubs
        Use the Message Differences window or options available within the stub console display to debug message-based stubs.
      - 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.

Locking and unlocking environments

Locking a IBM® Rational® Test Control Panel environment prevents other users from starting or stopping stubs in that environment.

After an environment is locked:

The user who locked the environment can make any changes to the environment as normal.
Only the user who locked the environment or a Rational® Test Control Panel administrator can unlock it.
Any other user can request that the environment be unlocked.

When locking an environment, there is the option to specify an expected duration for the lock, which will be displayed to any users who try to access the environment while it is locked. However, the lock will not expire if the specified duration is exceeded.

The following topics describe how to lock and unlock an environment.