Home
Rational® Integration Tester
Getting Started
This guide provides an overview and describes the tasks to get you started with Rational® Integration Tester.
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.
Discovering, Recording, and Intercepting an HTTP proxy
You can create stubs (virtual services) when you do not have a service or an API definition file such as WSDL or Swagger. You can enable the stub to use an HTTP proxy as the transport for messaging, then use the topology discovery capabilities to discover the endpoints and intercept the endpoints. You can record an operation and verify if the service is virtualized by disabling the server application.

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.
  - Rational® Integration Tester overview
    You can use Rational® Integration Tester to create, modify, 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.
    - Creating and running a test
      You can create and run a test in Rational® Integration Tester by importing a Swagger definition of an API. You can also find pointers for creating and running tests when the system under test does not have a Swagger definition.
    - Creating and running a stub
      Integration testing in a real environment can be difficult because not all components are always available, even though the requirement is to test all the components of an application. With Rational® Integration Tester, you can create reusable and maintainable stubs (virtual services), which you can use in testing until the actual components become available. You can create and run a stub with a WSDL file.
    - Discovering, Recording, and Intercepting an HTTP proxy
      You can create stubs (virtual services) when you do not have a service or an API definition file such as WSDL or Swagger. You can enable the stub to use an HTTP proxy as the transport for messaging, then use the topology discovery capabilities to discover the endpoints and intercept the endpoints. You can record an operation and verify if the service is virtualized by disabling the server application.
      - Creating a project
        Creating a project is the first step to start working with Rational® Integration Tester. A project contains the basic settings used by tests. You can also find different interactive guides on the Home page that provide you with information on the common tasks that you can accomplish in Rational Integration Tester.
    - Running a stub in a Docker container
      You can package a stub into a Docker image and then run the stub in a Docker container. You can run the stub anywhere that you have a Docker environment, whether on a private cloud or public cloud.
  - 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.
  - 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.
- 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.
- 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.

Discovering, Recording, and Intercepting an HTTP proxy

You can create stubs (virtual services) when you do not have a service or an API definition file such as WSDL or Swagger. You can enable the stub to use an HTTP proxy as the transport for messaging, then use the topology discovery capabilities to discover the endpoints and intercept the endpoints. You can record an operation and verify if the service is virtualized by disabling the server application.

You must perform the following sub tasks in sequence: