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.
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.
Integration Testing
You can use find information about the tasks that you can perform for testing various domains, technologies, or applications.
Testing applications on z/OS®
You can test applications on IBM® z/OS® systems by using the capabilities that are supported for mainframes by Rational® Integration Tester. Rational Integration Tester is installed as part of the IBM Rational Test Workbench product offering.
Testing with CICS®
Rational® Integration Tester supports the recording and virtualization of CICS® programs that are run on z/OS® and are called by CICS Distributed Program Link (DPL). The CICS transport supports interacting with such calls in CICS Transaction Server (EXEC CICS LINK calls and ECIRequest calls using IPIC) and CICS Transaction Gateway (ECIRequest calls). CICS programs can be called in a test via a CICS Transaction Gateway.
Using CICS® Transaction Gateway for recording and virtualization
You can use CICS® Transaction Gateway for recording and stubbing (virtualization) ECI request calls of a CICS program. You can configure a Java™ application of the CICS Transaction Gateway client for recording and stubbing. Recording can also take place in the CICS Transaction Gateway daemon. When you use the CICS Transaction Gateway method, you can virtualize CICS even when there is no CICS server connected. In such a case, the messages are routed to a stub and the CICS Transaction Gateway need not connect to a running CICS server.
Enabling virtualization in a CICS® Transaction Gateway client application
You can enable virtualization for CICS® Transaction Gateway in a Java™ client that uses the CICS Transaction Gateway client API.

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.
  - 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.
    - Integration Testing
      You can use find information about the tasks that you can perform for testing various domains, technologies, or applications.
      - Testing Java™ applications
        You can use Rational® Integration Tester to test Java™ applications.
      - Testing Java™ Message Service (JMS) systems
        Use the generic JMS plug-in to connect Rational® Integration Tester to a wide range of EAI platforms, which includes any vendor that provides an implementation of this Java™ standard. JMS provides a way of separating the application from the transport layer of providing data. The same Java classes can be used to communicate with different JMS providers by using the JNDI information for a specific provider. The classes first use a connection factory to connect to the queue or topic, and then use populate and send or publish the messages. On the receiving side, the clients then receive or subscribe to the messages
      - Testing Java™ objects
        You can import Plain Old Java™ Objects (POJOs) from JAR files into Rational® Integration Tester in order to parse and construct messages containing the serialized forms of those objects. You can construct and parse the Java objects and perform validation, but you cannot test the objects directly.
      - Testing with Apache Camel components
        You can use Rational® Integration Tester to create tests and stubs by setting up an Apache Camel component in a Rational Integration Tester project. You can configure the technology endpoints supported by the Camel component as the physical resources in the Rational Integration Tester project and test for the services provided by the technology.
      - Testing with Apache Kafka
        Starting from IBM® Rational® Integration Tester 10.0.2 and later, you can create Kafka transports to test Kafka services.
      - Testing with Docker
        You can use Docker containers with Rational® Integration Tester to run stubs co-located with your test systems.
      - Testing with the email transport
        When you use applications in your test environment that use email services, you can use Rational® Integration Tester to create tests and stubs for testing the email services. You can set up an email transport in a Rational Integration Tester project and configure the email servers as the physical resources in the Rational Integration Tester project, and then test the email services.
      - Testing with Envoy Proxy (Experimental)
        You can use Rational® Integration Tester to record the HTTP traffic on the Envoy Proxy by using the Experimental HTTP Tap Filter feature of the Envoy Proxy.
      - Testing with the File transport
        As with any other transport, the File transport includes both logical and physical configurations. Tests and stubs are associated with the logical File resource, which represents an abstraction of the File resource and is the same for all environments. The physical File Access configuration includes connection details, and you can configure a different physical File Access for each environment.
      - Testing with the FIX transport
        You can use the Financial Information eXchange (FIX) transport and FIX dictionaries in Rational® Integration Tester to help you test trade-related messages and the systems that use them.
      - Testing with the HTTP transport
        To provide support for HTTP-based communications, you must configure and run Rational® Integration Tester by using the HTTP transport and SOAP message formatters.
      - Testing with IBM® API Developer Portals
        You can configure IBM® Rational® Integration Tester to synchronize IBM API Connect™ Developer Portal resources or IBM API Management Developer Portal resources.
      - Testing with IBM® App Connect Enterprise
        When you want to test the services on applications deployed by the integration node of IBM® App Connect Enterprise, you can use the synchronization feature in Rational® Integration Tester to import details of deployed applications into a Rational Integration Tester project. You can select the tests and stubs to be created in your project during the synchronization process in Rational Integration Tester.
      - Testing with IBM® Integration Bus
        When you want to test the services on applications deployed by the integration node of IBM® Integration Bus, you can use the synchronization feature in Rational® Integration Tester to import details of deployed applications into a Rational Integration Tester project. You can select the tests and stubs to be created in your project during the synchronization process in Rational Integration Tester.
      - Testing with IBM® WebSphere® Application Server
        You can configure IBM® Rational® Integration Tester to synchronize IBM WebSphere® Application Server resources.
      - Testing with IBM® WebSphere® MQ messages
        You can test WebSphere® MQ messages using the WebSphere MQ transport method or JMS interface. Rational® Integration Tester also supports testing WebSphere MQ on z/OS systems.
      - Testing with WebSphere® Portal
        You can configure IBM® Rational® Integration Tester to synchronize IBM WebSphere® Portal resources.
      - Testing with IBM® z/OS® Connect Enterprise Edition
        IBM® z/OS® Connect Enterprise Edition provides a framework for enabling z/OS®-based programs and data to fully participate in the new API economy for mobile and cloud applications. Use IBM® z/OS® Connect Enterprise Edition to access z/OS subsystems, such as CICS®, IMS™ and Batch, by using RESTful APIs with JSON formatted messages. You can access multiple z/OS subsystems concurrently through a common interface.
      - Testing with Istio
        When you have applications hosted in a Kubernetes cluster that have Istio as a service mesh, you can virtualize the services in the cluster by creating stubs and tests for testing with Istio in Rational® Integration Tester.
      - Testing with Kubernetes
        Rational® Integration Tester supports testing with Kubernetes after you set up a Kubernetes cluster. You can test the containerized applications that run as services in Kubernetes in Rational Integration Tester. You can also create and publish stubs from Rational Integration Tester to Kubernetes and then run the stubs in Kubernetes.
      - Testing with Microsoft™ .NET objects
        You can import serializable .NET objects from .NET assembly files (.exe or .dll) into IBM® Rational® Integration Tester and apply them to messages in the same way as you would apply a schema. A service-based test or stub can then send and receive a message containing a serialized form of a .NET object from the assembly file. You can construct and parse the .NET objects and perform validation, but you cannot test the objects directly.
      - Testing the migrated Postman collections
        You can migrate Postman collections and environments that you created in Postman to Rational® Integration Tester. Operations, transports, tests and stubs are automatically created during migration and you can run the tests and stubs in Rational Integration Tester.
      - Testing with MongoDB
        If you are using Rational® Integration Tester 9.5.0 or later, you can create MongoDB transports and run tests against them.
      - Testing with the MQ telemetry transport
        If you are using Rational® Integration Tester 8.6.0 or later, you can create MQ telemetry transports.
      - Testing with Oracle Fusion
        Configure and run Rational® Integration Tester with the Oracle Fusion plug-in, which provides support for synchronization with and testing of the web services and composites that are available on a configured SOA server (that is, an Oracle WebLogic server with Oracle SOA Suite 11g deployed on it).
      - Testing with RabbitMQ
        If you are using Rational® Integration Tester 9.2.1.1 or later, you can create RabbitMQ transports.
      - Testing with SAP applications
        You can use Rational® Integration Tester to test SAP application server resources.
      - Testing with Software AG CentraSite
        You can incorporate governance in your SOA by using the integration of Rational® Integration Tester with Software AG CentraSite.
      - Testing with Software AG Universal Messaging
        You can use Rational® Integration Tester API to test Software AG Universal Messaging Broker server resources. From Rational Integration Tester 10.0.2 or later, you can create Software AG Universal Messaging Broker transports, configure and run Rational Integration Tester with the Software AG Universal Messaging server.
      - Testing with Software AG webMethods
        You can configure and run Rational® Integration Tester with the Software AG webMethods Integration Server to connect to Software AG webMethods Broker and Integration Server resources.
      - Testing with SSL
        To provide secure connections between clients and servers during testing, you can use the Secure Sockets Layer (SSL) technology supported by Rational® Integration Tester.
      - TCP and UDP
        In Rational® Integration Tester, you can create transports that facilitate communication between clients and servers by using both TCP- and UDP-based sockets.
      - Testing with TIBCO applications
        To use IBM® Rational® Integration Tester to test TIBCO messaging, you must configure and run Rational Integration Tester with the TIBCO messaging plug-in. Doing so supports TIBCO Rendezvous messaging ("plain" TIBCO Rendezvous messaging and TIBCO ActiveEnterprise (AE) formats), TIBCO EMS messaging, and sending and receiving AE messages by using TIBCO EMS.
      - Testing applications on z/OS®
        You can test applications on IBM® z/OS® systems by using the capabilities that are supported for mainframes by Rational® Integration Tester. Rational Integration Tester is installed as part of the IBM Rational Test Workbench product offering.
        Testing with CICS®
        Rational® Integration Tester supports the recording and virtualization of CICS® programs that are run on z/OS® and are called by CICS Distributed Program Link (DPL). The CICS transport supports interacting with such calls in CICS Transaction Server (EXEC CICS LINK calls and ECIRequest calls using IPIC) and CICS Transaction Gateway (ECIRequest calls). CICS programs can be called in a test via a CICS Transaction Gateway.
        Before creating CICS® transports
        To use a CICS® transport in your tests in Rational® Integration Tester, you must configure Rational Integration Tester to use CICS Transaction Gateway JAR files.
        Using CICS® Transaction Gateway for recording and virtualization
        You can use CICS® Transaction Gateway for recording and stubbing (virtualization) ECI request calls of a CICS program. You can configure a Java™ application of the CICS Transaction Gateway client for recording and stubbing. Recording can also take place in the CICS Transaction Gateway daemon. When you use the CICS Transaction Gateway method, you can virtualize CICS even when there is no CICS server connected. In such a case, the messages are routed to a stub and the CICS Transaction Gateway need not connect to a running CICS server.
        Requirements for CICS® Transaction Gateway
        You can find information about the requirements that must be satisfied before you can use the CICS® Transaction Gateway (CTG).
        Adding the CICS® Transaction Gateway agent to a client application
        To record or virtualize requests in a CICS® Transaction Gateway Java™ client, you must add the CICS Transaction Gateway agent that is provided with Rational® Test Control Panel to the client application.
        Enabling recording in a CICS® Transaction Gateway client application
        You can enable recording for CICS® Transaction Gateway in a Java™ client that uses the CICS Transaction Gateway client API.
        Enabling virtualization in a CICS® Transaction Gateway client application
        You can enable virtualization for CICS® Transaction Gateway in a Java™ client that uses the CICS Transaction Gateway client API.
        Enabling recording and stubbing in the CICS Transaction Gateway daemon
        As an alternative to a CICS® Transaction Gateway client application, you can use the CICS Transaction Gateway daemon for recording and stubbing.
        Enabling and disabling remote diagnostic logging for the CICS® Transaction Gateway proxy
        To facilitate troubleshooting, IBM® Rational® Test Control Panel administrators can view, download, and share detailed log events information for the CICS® Transaction Gateway proxy. The capability to display this information in Rational Test Control Panel requires enabling remote diagnostic logging for the proxy.
        Viewing the configuration and log files
        To troubleshoot issues while working with the CICS® Transaction Gateway, you can use the configuration (ctg.ini) and log files.
        Recording and virtualizing DPL calls in CICS® Transaction Server
        You can record and virtualize CICS® Distributed Program Link (DPL) calls with CICS Transaction Server versions 5.2, 5.3, 5.4, and 5.5. To do so, install and configure Rational® Integration Tester CICS TS Agent in the CICS regions that are making the DPL requests.
        Recording and virtualizing CICS® applications that use IPIC
        To record and virtualize IP interconnectivity (IPIC) to a CICS® region, you must first configure the Rational® Integration Tester HTTP/TCP Proxy, and then enable your CICS client application.
        Using CICS® web services for HTTP traffic
        You can use CICS® web services to record, redirect, or create stubs for HTTP traffic. CICS programs can make available or use HTTP-based web services.
        Defining CICS® resources in Rational® Integration Tester
        You must define logical and physical CICS® resources to record and virtualize CICS programs running on zOS.
        Configuring CICS® Transaction Gateway messages in tests
        After you define CICS® physical and logical resources and bind them to an environment, you must create a test for an operation that is bound to a logical CICS server. Then you can configure CICS Transaction Gateway messages.
        Testing with WebSphere® MQ on z/OS® systems
        You can test WebSphere® MQ on z/OS® by using the Rational® Integration Tester MQ agent module. You can record at the transport level or operation level when running the agent with a single queue manager. If you have a queue sharing group and if you choose to run an instance of the agent for each queue manager within the queue sharing group, you can record shared queues using mirror queue recording. You can also virtualize requests to shared queues using fixed queue stubbing.
        Testing with IBM® IMS™ Connect
        For testing with IBM® Information Management System (IBM IMS Connect), you can set up Rational® Integration Tester. With this set up you can record the IBM IMS Connect traffic.
        Testing with IBM® Db2® on z/OS® systems
        With the Agent for z/OS® that works together with IBM® Debug for z/OS, you can record SQL statements to Db2® for z/OS databases from COBOL and PL/I programs that run on z/OS.
        Troubleshooting: Testing on IBM® z/OS®
        You can use workarounds to common problems that you might encounter when you use IBM® z/OS® with Rational® Integration Tester.
      - Managing credentials
        If you have external resources that must be accessed by project or test resources in Rational® Integration Tester and you do not want to expose the credentials used to access the external resources, then you can implement a user-defined access in a credential management system.
      - Configuration of virtual IP addresses as virtual clients
        You can find information about how to configure virtual IP addresses in the operating system, and then use the virtual IP addresses to configure them as virtual clients in tests or as virtual servers in stubs.
      - Configuration of test runs in a GitHub Actions Workflow
        You can configure test runs of test resources that you create in Rational® Integration Tester in a GitHub Actions Workflow. You can choose to run test resources in the GitHub Workflow when you do not want to run the test resources without opening Rational Integration Tester.
      - Security vulnerabilities testing by using HCL® AppScan
        You can use HCL® AppScan to scan all HTTP traffic that is generated as part of integration testing in Rational® Integration Tester for security vulnerabilities.
    - Extending Rational® Integration Tester functionality by using custom functions
      You can add more calculations and operations to tests by using the Rational® Integration Tester custom function class. Rational Integration Tester custom function is a Java™ class that extends the com.ghc.ghTester.expressions function.
    - Working in non-GUI mode
      You can use the tools and executable files that are provided along with the product software. You can use these tools to perform different test actions in a non-GUI mode.
  - Tester Guide - Performance Testing
    Typically, a user with the Integration Tester role is also responsible for performance testing. This guide lists all such topics.
  - 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.
- 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
  While working with Rational® Integration Tester, you might encounter some problems that you can easily troubleshoot.
- Reference Guide
  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.
- 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.

Enabling virtualization in a CICS® Transaction Gateway client application

You can enable virtualization for CICS® Transaction Gateway in a Java™ client that uses the CICS® Transaction Gateway client API.

Before you begin

You must have added the CICS® Transaction Gateway Agent to your client application. See Adding the CICS Transaction Gateway agent to a client application.

Procedure

Specify the following Java™ system property before you run the client application, to enable virtualization.
```
-Dgateway.intercept.plugin=com.ibm.rational.rit.CTGRequestIntercept
```
Optional: If you do not want the client to connect to the gateway, you must specify the following system property.
```
-Dcom.ibm.greenhat.noGateway=true
```
In the case where a gateway is not used, you must configure the stubs to handle all requests made by the client.