Home
Getting Started
This guide provides an overview and describes the tasks to get you started with Rational® Integration Tester.
Rational® Test Control Panel overview
Rational® Test Virtualization Server stubs designed in Rational Integration Tester are published to Rational Test Control Panel, which holds them in a repository.
Running stubs
When several versions of a stub are deployed, it is possible to run all versions of them in the same environment.

Getting Started
This guide provides an overview and describes the tasks to get you started with Rational® Integration Tester.
- Rational® Integration Tester overview
  You can use Rational® Integration Tester to create, modify, and run service tests, and performance tests.
- Testing methodology
  By following four basic guidelines, you can incorporate Rational® Integration Tester into your testing methodology. These guidelines drive efficient and expedient integration testing, and they can be applied to your testing process and infrastructure requirements.
- Service-oriented architecture (SOA) testing
  A SOA consists of business processes that are implemented by linking individual services. The linking can be done programmatically or with tools based on Business Process Execution Language (BPEL). SOA testing can be challenging because there is no GUI; the focus is on testing interfaces and services.
- Getting started with testing
  You can start using Rational® Integration Tester by completing the preliminary tasks such as creating and running a test, creating and running a stub, recording an HTTP proxy, and running a stub in a Docker container.
- Rational® Test Control Panel overview
  Rational® Test Virtualization Server stubs designed in Rational Integration Tester are published to Rational Test Control Panel, which holds them in a repository.
  - Domains and environments
    You can use domains to group and manage test assets. Within a domain, you can have one or more environments, which can use to group test variables and test tags.
  - Deploying stubs
    For the stub to access the correct data source, you must publish each stub to the correct domain and environment that is the one that contains that stubs data source.
  - Publishing several versions of the same stub
    During testing, you might discover that you require several versions of a stub and you might not want to override the previous version.
  - Running stubs
    When several versions of a stub are deployed, it is possible to run all versions of them in the same environment.
  - Sharing and managing stubs
    If the purpose of a particular Rational® Integration Tester project is to develop and test a component that requires virtualization (stubbing), that project must own that stub but it can be shared across other projects that need to use it.
- Rational® Integration Tester accessibility features
  Users who have a physical disability, such as limited vision, can review the available accessibility features to use Rational® Integration Tester.

Running stubs

When several versions of a stub are deployed, it is possible to run all versions of them in the same environment.

Note: Stubs can affect each other if they are listening on the same queue. For example, if you are running multiple versions of the same stub, reconfigure endpoints so that each version of the stub does not clash with each other when started.

Before running tests, you might require several stubs to start in your environment. Selecting individual stubs to start each time takes time and might also mean that you start the incorrect ones or that you forget to start some.

By saving a scenario, you can quickly start a set of stubs. When you start a scenario, it will start all the stubs that are currently running in the dashboard. Save new scenario

Save new scenario

Configuration at run time

When you are starting a stub in IBM® Rational® Test Control Panel, a stub startup configuration window is displayed. You can use this window to select the stub and the version you want to run, configure tags, and select the agents to which the stub will be deployed. You must also add descriptive labels and ensure that stub version numbering is implemented correctly.