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
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.
Working in non-GUI mode
You can use the tools and executable files that are provided along with the product software. You can use these tools to perform different test actions in a non-GUI mode.
Managing stubs
You can manage stubs by using the command-line, Ant, and REST APIs.
Selecting a stub to start or stop
You can use various options to select a stub to start or stop.

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 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. This guide is intended for Integration testers.
    - Integration Testing
      You can use find information about the tasks that you can perform for testing various domains, technologies, or applications.
    - Extending Rational® Integration Tester functionality by using custom functions
      You can add more calculations and operations to tests by using the Rational® Integration Tester custom function class. Rational Integration Tester custom function is a Java™ class that extends the com.ghc.ghTester.expressions function.
    - Working in non-GUI mode
      You can use the tools and executable files that are provided along with the product software. You can use these tools to perform different test actions in a non-GUI mode.
      - Command-line interfaces
        Rational® Integration Tester command-line client is available in Rational Integration Tester 8.0.1 or later.
      - Ant tasks
        You can use the supported Ant tasks that is supplied with Rational® Test Control Panel to create, update, or manage the environment, scenarios, and stubs.
      - REST services
        Representational state transfer (REST) is a simple stateless architecture that generally runs over HTTP. When used in conjunction with IBM® Rational® Test Control Panel, HTTP methods (such as GET and POST) are mapped to actions on domains, environments, scenarios, stubs and other resource types.
      - Running tests
        Use Rational® Integration Tester to run tests with command-line and Ant APIs.
      - Managing test results
        Use IBM® Rational® Test Control Panel to manage test results with command-line APIs.
      - Managing domains
        You can create, list, update, and delete domains with the Rational® Test Control Panel REST API.
      - Managing environments
        Locking a Rational® Test Control Panel environment prevents other users from changing the state of that environment, for example, starting or stopping stubs.
      - Managing scenarios
        Use IBM® Rational® Test Control Panel to manage scenarios with command-line, Ant, and REST APIs.
      - Managing stubs
        You can manage stubs by using the command-line, Ant, and REST APIs.
        Selecting stubs to be published
        You can use various options to select stubs to be published.
        Selecting a stub to start or stop
        You can use various options to select a stub to start or stop.
        Publish stubs by using the command line
        You can publish a stub to IBM® Rational® Test Control Panel, Dockerfile and build context, or Kubernetes by using the Rational Integration Tester command line.
        Start a stub by using the command line
        You can start a stub by using the Rational® Integration Tester command line.
        Stop a stub by using the command line
        You can stop all instances of a stub by using the Rational® Integration Tester command line. This option is useful in situations where Ant is not available.
        Publish stubs by using an Ant task
        You can publish stubs by using the IBM® Rational® Test Control Panel Ant task, the Dockerfile and build context Ant task or the Kubernetes Ant task.
        Updating a managed stub by using the command line
        You can update the values of the attributes of a managed stub by using the Rational® Integration Tester command line.
        Start a stub by using an Ant task
        You can start a stub by using the IBM® Rational® Test Control Panel Ant tasks.
        Stop a stub by using an Ant task
        You can stop a stub by using the IBM® Rational® Test Control Panel Ant tasks.
        Updating a managed stub by using an Ant task
        You can update the values of the attributes of a managed stub by using the IBM® Rational® Test Control Panel Ant tasks.
        REST services
        Representational state transfer (REST) is a simple stateless architecture that generally runs over HTTP. When used in conjunction with IBM® Rational® Test Control Panel, HTTP methods (such as GET and POST) are mapped to actions on domains, environments, scenarios, stubs and other resource types.
  - Technical Tester Guide
    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.
- 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.

Selecting a stub to start or stop

You can use various options to select a stub to start or stop.

When selecting a stub, the domain, environment, component, operation, name and version options must uniquely identify the particular stub and a particular version of that stub to start.

If, for a given name, there is only one stub with that name in an environment, only domain, environment, and name are required.
If there are multiple versions:
- You can specify domain, environment and stub name to start the latest version of the stub.
  Note: If you are using Rational® Integration Tester 8.5.0 or earlier, and the Rational® Test Control Panel command line or Apache Ant tasks are used to start a stub, and if no stub version information is provided, it is the earliest version of a stub that is run.
- Alternatively, you can specify domain, environment, stub name and version to start a particular version of the stub.
If there are multiple stubs of the same name in an environment, you use the component and operation options to specify which one is to be started. These are the component and operation names under which the stub is available in the Rational® Test Control Panel Environments dashboard. They are the same as lowest level service component, or similar, and the operation, if any, that the stub is under in the project.
If the command is being used in an automated script, always use the component, operation (if any), and version even if, at the time of writing the script, one of the alternatives above would be sufficient. This is because using all of these options bring resilience against future changes in the environment's list of available stubs and versions.

If you locked the environment that you use and Rational® Test Control Panel security is enabled and Administration of Rational Test Control Panel, you must include your user name with any commands that you enter. However, if the security functionality of Rational® Test Control Panel is disabled, you must not specify the user name option even if the environment is locked.