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 - 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 with SAP applications
You can use Rational® Integration Tester to test SAP application server resources.
Working with SAP application server resources
After importing SAP application server resources into your Rational® Integration Tester project, you can use the project to test those resources.
IDocs
The intermediate documents (IDocs) that you can use in your Rational® Integration Tester project depend on the IDocs you selected before synchronizing any logical SAP applications servers in your project.

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 requirements
        Review the software and system requirements for using the SAP capabilities with Rational® Integration Tester.
      - Installing a custom SAP ABAP plug-in
        To enable Rational® Integration Tester to be able to record IDocs and enable the watch mode subscriptions, you must install and configure the plug-in that is provided with Rational Test Control Panel.
      - Configuring SAP Process Integration to use the HTTP/TCP proxy
        You can configure SAP Process Integration to use the HTTP/TCP proxy in the SAP Integration Builder.
      - Synchronizing with an SAP application server
        Rational® Integration Tester can synchronize with and test business objects within an SAP system by using Business Application Programming Interface (BAPIs), remote function calls (RFCs), and intermediate documents (IDocs).
      - Working with SAP application server resources
        After importing SAP application server resources into your Rational® Integration Tester project, you can use the project to test those resources.
        BAPIs and RFCs
        A business application programming interface (BAPI) invocation is a synchronous operation, so it is modeled in Rational® Integration Tester as two schema items: one item defines the parameters that are passed into the system while the other item defines the resulting return information, usually a structure and sometimes a table. Data dictionary structures are used within SAP to describe these inputs and outputs.
        IDocs
        The intermediate documents (IDocs) that you can use in your Rational® Integration Tester project depend on the IDocs you selected before synchronizing any logical SAP applications servers in your project.
        Publishing IDocs
        In Rational® Integration Tester, the Publish messaging action is used to publish IDocs to an SAP system.
        Subscribing to IDocs
        In Rational® Integration Tester, the Subscribe messaging action is used to retrieve IDocs from an SAP system.
        Processing non-native (XML) IDOCs
        Using Rational® Integration Tester, you can send an XML encoded version of an IDoc to any appropriate receiver.
        Configuring an SAP system to send and receive IDocs
        To send or receive IDoc from SAP ECC, you must set up Rational® Integration Tester or IBM® Rational Test Virtualization Server as a registered TCP/IP program.
        Verifying the IDoc subscriber configuration
        Verify the IDoc subscriber configuration by sending an IDoc from an SAP system to Rational® Integration Tester.
      - Example: Virtualizing SAP RFC calls
        Follow an example of how configure a Java Application logical transport to record the necessary metadata in order to use stubs without connecting to an SAP system.
    - 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.
    - 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 as a GitHub Actions Workflow
    - 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.

IDocs

The intermediate documents (IDocs) that you can use in your Rational® Integration Tester project depend on the IDocs you selected before synchronizing any logical SAP applications servers in your project.

Every IDoc instance includes a reference to a metadata schema so that data structures can change over time. Typically, only the latest metadata version is used. However, Rational® Integration Tester assigns older metadata versions automatically when required; for example, when recording historic IDoc traffic.