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.
Integration 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.
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.
Performance profiles
You can use a performance profile to store response time characteristics for a stub over a period of time.
Creating performance profiles
You can use performance profiles to define response time details for a stub over time.
Applying a performance profile to a stub
After you create a performance profile, you must apply recorded response data to the stub execution to gather performance data.

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 Reference
  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.
- Integration 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.
  - Task flow: Working with the IBM® Rational® Test Control Panel Environments dashboard
    You can use the Rational® Test Control Panel Environments dashboard to perform various tasks such as starting, stopping stubs and scenarios, and modifying stub configurations after you have published stubs to Rational Test Control Panel. You can also lock the environment that contain the published 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.
  - 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.
    - The Events tab
      With the Events tab, you can define how the stub will handle internally and/or externally received events.
    - The Behavior tab
      With the Behavior tab, you can add reusable behavioral entities, that is, pre-programmed intelligence, to your stub.
    - The Properties tab
      With the Properties tab, you can set up states for your stub and input parameters that can determine how the stub behaves when it runs.
    - The Performance tab
      With the Performance tab, you can change the performance characteristics of the stub either by adding delays when a stub runs or by disabling performance optimization.
    - The Session tab
      With the Session tab, you can configure the sharing of the tag data store between workers (instances of the stub), so that messages can be processed based on information that was captured from previously processed messages.
    - The Logging tab
      With the Logging tab, you can define how much information is recorded while your stub is being executed.
    - The Documentation tab
    - Adding a timer behavior to a stub
      You can use a timer behavior to set a timer event in a stub. After a set time period, the timer event is triggered, the stub receives the event, which it can then respond to. For example, you might have a stub to manage user sessions and you want to add a timer behavior that automatically logs out a user after 30 seconds of inactivity.
    - Example: Adding a repeating timer behavior to a stub
      In this example, you add a repeating timer event to a stub that starts after zero seconds and then repeats every 10 seconds.
    - Sift-and-pass-through capability
      You can filter the messages that a stub receives, separating traffic from client and server applications that need to use the live system as opposed to a virtual system.
    - Performance profiles
      You can use a performance profile to store response time characteristics for a stub over a period of time.
      - Creating performance profiles
        You can use performance profiles to define response time details for a stub over time.
        Creating a stub that includes a performance profile
        You can save performance data at the same time that you save recorded events for a stub in Recording Studio.
        Importing performance data from Recording Studio
        When you save events in Recording Studio, you can import performance data into a performance profile. You can then use the performance profile to simulate the timing of the responses from a stub.
        Populating performance profiles manually
        You can populate performance profiles for stubs manually.
        Importing performance data from a spreadsheet
        In Rational® Integration Tester version 8.5.1 or later, you can populate stub performance profiles by importing data from spreadsheets.
        Importing performance data from Tivoli Composite Application Manager for Transactions
        Depending on the version of Rational® Integration Tester that you are using, you can use the Rational Integration Tester command-line client or user interface to import data from IBM® Tivoli® Monitoring and IBM Tivoli Composite Application Manager for Transactions, and then populate stub performance profiles with this data.
        Applying a performance profile to a stub
        After you create a performance profile, you must apply recorded response data to the stub execution to gather performance data.
  - 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.

Applying a performance profile to a stub

After you create a performance profile, you must apply recorded response data to the stub execution to gather performance data.

Procedure

In Test Factory, open a stub.
Specify a response-time type for each operation. On the Properties tab, double-click the cell under Type.
In the Edit window, select Performance Profile. The performance profile options are displayed.
Select a performance profile.
Select a start time. The start time represents the simulated time at which the first phase begins. The start time setting is used in conjunction with the start time that is configured in the response time properties of a stub, to determine at what point in the profile to begin when a stub is started. Use the start times to simulate the response times for a specific period in time, regardless of the actual time the stub executes. The selected time should fall within the period recorded in the performance profile, as defined by the profile's start time and the total duration of all of its phases.
Here is an example of how to use the start time:
Assume that the performance profile covers 124 hours starting from November 11, 08:00, and time from November 11, 08:00 to November 16, 12:00. Assume that the first few phases are as follows (duration (minutes), fixed delay (ms)):
1. 60, 1000
2. 60, 2000
3. 60, 3000
4. 30, 4000
5. 30, 5000
6. 720, 6000
7. 480, 500
8. 60, 1000
A start time of Nov 11, 08:30 would start half-way through phase 1 (because the run has a fixed delay of 1000ms for 30 minutes before moving on to 2000ms for 60 minutes). A start time of November 12, 06:00 would run with a 500ms delay (phase 7) for 2 hours before hitting phase 8 and running for an hour with a 1000ms delay.
When the stub runs, as each phase starts, the changes to the response time are displayed on the console or written to the agent log.