Home
Rational® Integration Tester
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.
Creating and modifying database stubs
You can create and modify database stubs in Rational® Integration Tester.
Modifying database stubs
You can modify database stubs in Rational® Integration Tester.
Editing database stub wizard
You can use the Edit Database Stub wizard to edit the contents of the currently selected database stub.
The database stub edit spreadsheet
You can edit the contents of a database stub by using the Edit Database Stub wizard. A spreadsheet editor is opened in which you can modify the stub. The editor contains information about how the spreadsheet is started and the spreadsheet format.

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.
- 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.
  - 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.
  - Technical Tester Guide
    Typically, a user with the Integration Tester role is also responsible for performance testing. This guide lists all such topics.
  - 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.
    - Creating and modifying database stubs
      You can create and modify database stubs in Rational® Integration Tester.
      - Prerequisites for creating database stubs
        Before creating any database stubs, you must complete any required software installation tasks and set up the schema that is used for stubbing a physical database.
      - Database stubs overview
        If you want to create a test or suite of tests for an application that uses a database, you run the test (suite) in a repeatable fashion against a known set of database contents. Therefore, you must stub the database to obtain repeatable conditions. Database stubs enable you to execute tests against some parts of a system under test without affecting a live database.
      - Persistence
        Database stubs created in Rational® Integration Tester can be non-persistent or persistent.
      - JDBC proxy
        The Rational® Integration Tester JDBC proxy package is provided with IBM® Rational Test Control Panel. You must deploy the package on any stand-alone applications, or application servers that host applications that use JDBC to access any live databases that you want to record or virtualize.
      - Stored procedures
        If you are using Rational® Integration Tester 8.0.1 or later, you can record and virtualize most stored procedures.
      - Data type support
        You can find information about the data types supported for database management systems in Rational® Integration Tester.
      - Synonyms
        A synonym is an alias or alternate name for a table, view, sequence, or other schema object. Rational® Integration Tester 8.5.1 or later supports certain synonyms for some supported database management systems.
      - Creating database stubs by using the Recording Studio
        You use the Recording Studio perspective of the Rational® Integration Tester to create a database stub while SQL events are being recorded from a database.
      - Modifying database stubs
        You can modify database stubs in Rational® Integration Tester.
        Example: Using pass-through in database stubs
        The editing options toolbar
        With the editing options toolbar, you can work with the database stubs.
        Editing database stub wizard
        You can use the Edit Database Stub wizard to edit the contents of the currently selected database stub.
        Editing using SQL queries
        You can edit using SQL Queries in the Edit Database Stub wizard.
        Editing tables
        You can edit tables using the Edit Database Stub wizard.
        The database stub edit spreadsheet
        You can edit the contents of a database stub by using the Edit Database Stub wizard. A spreadsheet editor is opened in which you can modify the stub. The editor contains information about how the spreadsheet is started and the spreadsheet format.
        Refresh wizard
        With the Refresh wizard, you can import additional data from a live database into the currently selected stub.
        Add wizard
        You can use the Add wizard to add more queries, tables, stored procedures, or sequences to the currently selected database stub.
        External edit wizard
        You can use the External Edit wizard to use any database management systems tools (to which you have access) to edit the contents of the currently selected database stub.
    - 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.
- 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 Rational® Integration Tester
  While working with Rational® Integration Tester, you might encounter some problems that you can easily troubleshoot.
- Rational® Integration Tester reference
  Rational® Integration Tester is a scripting-free environment for developing tests for service-oriented architecture (SOA) messaging and business process integration projects. Tests can be built by recording existing system behaviors or from requirements, by entering the data to send and the data that is expected in return.
- 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.

The database stub edit spreadsheet

You can edit the contents of a database stub by using the Edit Database Stub wizard. A spreadsheet editor is opened in which you can modify the stub. The editor contains information about how the spreadsheet is started and the spreadsheet format.

Spreadsheet editor

A temporary .xls file is created and the system default spreadsheet editor is started.

Note: This default can be overridden by explicitly associating a .xls editor under Applications Preferences (See Changing preferences and, specifically, Applications preferences).

Spreadsheet format

The spreadsheet can take two forms, which are based on the type of database information it represents:

Database table spreadsheet format

Each page represents a single table. The title of the page is the table name. The first row contains the column names and subsequent rows contain the respective values:

Any value that you select in the spreadsheet can be edited.
A new column can be added to the table by entering a new column name in the header cell and the database-type to be used for the column, and then by entering values for each row.
Note: The type name must be in parentheses. For example, NEW_COL (VARCHAR(20)).
An existing column's name or type cannot be modified.

Note: If you select to edit the contents of multiple tables for simultaneous editing, each table is on a separate page.

Database stored procedure spreadsheet format

The spreadsheet can contain the following pages:

Inbound parameters: The page contains the names of the inbound parameters on the first row. You can specify your own values on the second row.
Outbound parameters: The page contains the names of the outbound parameters and the result code on the first row. You can specify your own values on the second row (result code is 0 by default)
Result Set 1, Result Set 2, and so on: The pages are present if the stored procedure returns result sets. The first row contains the column names and subsequent rows contain the respective values.

A new result set can be added by adding a spreadsheet page, whose title is of the form Result Set <n>, where <n> is the new result set number.