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 HCL OneTest™ API.
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.

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 HCL OneTest™ API.
- Getting Started
  This guide provides an overview and describes the tasks to get you started with HCL OneTest™ API.
- Administrator Guide
  This guide describes how to install HCL OneTest™ API. 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.
    - HCL OneTest™ Virtualization overview
      HCL OneTest™ Virtualization is software that is used for creating, maintaining, publishing, and running message-based stubs and database stubs.
    - Task flow: Working with the HCL Quality Server Environments dashboard
      You can use the HCL Quality Server Environments dashboard to perform various tasks such as starting, stopping stubs and scenarios, and modifying stub configurations after you have published stubs to HCL Quality Server. 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 HCL OneTest™ API, 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 HCL OneTest™ API.
    - Creating and modifying database stubs
      You can create and modify database stubs in HCL OneTest™ API.
      - 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.
        Setting up the schema used for stubbing a physical database
        Before you can create database stubs, you must specify in HCL OneTest™ API which database schema is to be used for the simulation database.
        Setting up a logical and physical database
        Before you can create database stubs, you must set up a logical and physical database in HCL OneTest™ API.
      - 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 HCL OneTest™ API can be non-persistent or persistent.
      - JDBC proxy
        The HCL OneTest™ API JDBC proxy package is provided with HCL Quality Server. 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 HCL OneTest™ API 8.0.1 or later, you can record and virtualize most stored procedures.
      - Data type support
        HCL OneTest™ API 8.0.1 or later supports most built-in data types of supported database management systems. HCL OneTest API 8.5.1 or later supports certain user-defined types of some supported database management systems.
      - Synonyms
        A synonym is an alias or alternate name for a table, view, sequence, or other schema object. HCL OneTest™ API 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 HCL OneTest™ API to create a database stub while SQL events are being recorded from a database.
      - Modifying database stubs
        You can modify database stubs in HCL OneTest™ API.
    - Configuring stubs to connect to HCL Quality Server 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 HCL Quality Server 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 HCL OneTest™ API to HCL Quality Server, Dockerfile and build context, Kubernetes, or Istio, if the stub is based on a supported transport.
    - Viewing results in HCL Quality Server
      You can use HCL Quality Server to display the results of tests that you run in both HCL OneTest™ API and HCL Quality Server.
    - Viewing usage statistics of virtual services in HCL Quality Server
      You can use HCL Quality Server to display the usage statistics of virtual services across HCL OneTest™ Virtualization and HCL OneTest API.
    - Viewing reports in HCL OneTest™ Server
      All the project stakeholders can view test reports for multiple testing products from the Results page on HCL OneTest™ Server. You can access the Results page from a web browser. Therefore, there is no need to install the desktop client.
    - Troubleshooting: HCL OneTest™ Virtualization
      You can use workarounds to common problems that you might encounter when you use HCL OneTest™ Virtualization.
- 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 HCL OneTest™ API
  While working with HCL OneTest™ API, you might encounter some problems that you can easily troubleshoot.
- HCL OneTest™ API reference
  HCL OneTest™ API 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.

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.

The following topics describe how to complete these prerequisites.

Preparation and planning

For information about installing and configuring the required software, and determining which live databases are to be stubbed and whether there are any database schema or data source requirements, refer to Setting up the JDBC proxy.

Note: The version number of the HCL Quality Server software that you are using must be the same as the version number of the HCL OneTest™ API software that you are using. Therefore, if you have upgraded your HCL OneTest™ API installation and you want to record SQL or create database stubs, you must also upgrade your HCL Quality Server installation and upgrade the JDBC proxy wherever it is deployed.