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 - 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.
Creating message-based stubs
In Rational® Integration Tester, there are several methods that you can use to create a message-based stub.
Stub creation by using the Recording Studio
Use the Recording Studio to create a message-based stub if you have access to a live system from which you can record events.
Reply-sequenced stubs
In the Recording Studio perspective, you can create a stub that can send different replies to a particular request, depending on the state of the tag data store for the stub.

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 - 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.
    - Message-based stubs overview
      A message-based stub is essentially an Rational® Integration Tester resource that listens for incoming messages on a particular transport. A stub can reply to specific messages or message-types, matched according to incoming filters, by using message case actions.
    - Creating an empty stub
      You can create an empty stub. You can add content later by using the stub editor.
    - Creating a stub by using MEP
      You can use the message exchange pattern (MEP) properties for an operation, which define binding and timeout details, to create a stub.
    - Creating a stub populated with data
      You can create a stub based on the structure of the schema that is defined for the operation and the have the response payload populated with data.
    - Stubs with multiple operations
      You can create a single stub to manage multiple operations as a unit. Such a stub is required if you need to share state across several operations.
    - Stub creation by using the Recording Studio
      Use the Recording Studio to create a message-based stub if you have access to a live system from which you can record events.
      - Creating basic stubs
        A basic stub, also called a hardcoded stub, is a stub that always returns the same response. You can create a basic stub from recorded events by using the Recorded Events wizard from the Recording Studio perspective.
      - Creating parameterized stubs
        A parameterized stub, also called a data-driven stub, is one that uses a data source such as a spreadsheet. You can create a data-driven stub from recorded events.
      - Creating data model-driven stubs
        Data models provide an alternative way to store data for a stub. This method creates stubs from recorded events, and such stubs can reuse the data across multiple operations.
      - Creating a stub that manages multiple operations using recorded messages
        Create a stub with multiple operations by using the Recording Studio perspective. Such a stub is required if you need to share state across several operations.
      - Reply-sequenced stubs
        In the Recording Studio perspective, you can create a stub that can send different replies to a particular request, depending on the state of the tag data store for the stub.
      - Managing recorded events data
        IBM® Rational® Test Control Panel can be used to manage and share recorded events data exported from Rational Integration Tester.
  - 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.
  - 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.

Reply-sequenced stubs

In the Recording Studio perspective, you can create a stub that can send different replies to a particular request, depending on the state of the tag data store for the stub.

Reply-sequenced stubs are generated in the Recording Studio by the same process you use to save any events to a stub. See Creating tests from recorded events. Reply-sequenced stubs are created whenever the recorded events contain replies that vary, for a particular request, during the recorded sequence of events.

When replies are sequenced, all events in the stub share a single tag data store, specifically the value of the SESSION/GROUPn/ReplyId tag. In the finished stub, reply sequencing events are displayed first, in the order that they were recorded, followed by events that uniquely map a request to a reply.

For hardcoded stubs, event handlers are created automatically for reply sequencing events, and a function is created to increment the SESSION/GROUPn/ReplyId tag. Duplicate messages are discarded.
For parameterized stubs, the Test Data Lookup action is used as a guard, matching the SESSION/GROUPn/ReplyId tag to the value in the nextReplyId column in the test data.

You can disable reply sequencing by selecting Tags > None on the Session page of the stub editor and clicking Yes in the Remove references dialog. All references to the SESSION/GROUPn/ReplyId tag are removed, and the guards for the events are changed. Any functions that were created for the events are also removed.