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 and modifying database stubs
You can create and modify database stubs in Rational® Integration Tester.
Persistence
Database stubs created in Rational® Integration Tester can be non-persistent or persistent.

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.
  - 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.
  - 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.

Persistence

Database stubs created in Rational® Integration Tester can be non-persistent or persistent.

A non-persistent database stub starts from the same known state each time it is run. That is, any changes made to the contents of a database stub during its use is lost when the stub is stopped. This process enables tests to run against a known starting state.

In contrast, a persistent database stub will remember its state when it is stopped, overwriting the previously saved state. When it is restarted, the stub will have the same data that it had when it was last stopped.

It is possible to change a stub from being persistent to being non-persistent. Make a stub persistent while you design, build, edit, and refine it for a test case. Make a stub non-persistent if you want a known start state each time the stub is used.

Note: In Rational® Integration Tester, you have the option to record SQL but not create or use database stubs.