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.
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.
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.
Stop a stub by using an Ant task
You can stop a stub by using the IBM® Rational® Test Control Panel Ant tasks.

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.
  - 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.
- 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.

Stop a stub by using an Ant task

You can stop a stub by using the IBM® Rational® Test Control Panel Ant tasks.

Here is an example syntax:

<taskdef name="stopStub" classname="com.ghc.ghTester.ant.StopStub" classpathref="tasklib" />

<stopStub domain="<Domain name>" environment="<Environment name>" component="<Component name>" 
operation="<Operation name>" name="<Stub name>" version="<Stub version number>" 
serverUrl="https://<Hostname or IP address>:5443/RTCP/"/>

The following table lists the attributes that you can use with the stopStub Ant task for stopping a stub.

Table 1. List of available attributes
Attribute	Description	Required
async	Run asynchronously (flag).	No, default option is synchronous.
component	Component the stub exists within.	No
domain	Domain name	Yes
environment	Environment name	Yes
failureProperty	The name of a property that is set in the event of a failure.	No
haltOnFailure	Set to true to fail the Ant script if the stub fails to stop (flag).	No, default is false.
name	The name of the target stub to stop.	Yes
operation	The operation the stub exists within on the server.	No
serverUrl	URL of the Rational® Test Control Panel	Yes
securityToken	Specify the security token generated for you to authenticate with Rational® Test Control Panel when the domain security is enabled. In the locked environment mode, the operation can be performed by the user who locked the environment.	No, default is to send no token.
version	Version of the target stub to stop.	No
username	Specify the user name to authenticate with the server if the environment is locked and the domain security is disabled.	No

Error codes

For details of any error codes, see Exit codes for Command-line client and Ant client.