Release notes for IBM® Rational® Integration Tester

This document contains information about What's new, installation, known issues, and contact information of IBM Support.

Contents

Product description

Rational® Integration Tester is an integration testing and virtualization tool that includes capabilities to automate and run tests earlier and more often to find problems sooner in the development cycle. See Rational Integration Tester overview.

What's new

You can find information about the features introduced in this release of Rational® Integration Tester.

The following sections list the new features, enhancements, or other changes made in this release.
  • Rational® Test Automation Server

    For information about Rational® Test Automation Server, see Release notes.

  • Rational® Test Control Panel
    • Tools page

      The list of agents changed for a release was updated. Review the Tools page of Rational® Test Control Panel to see each tool and the version that it was last changed.

  • Technologies

    • Testing of internal Kubernetes services

      Rational® Integration Tester now supports testing of the internal services in a Kubernetes cluster when those services are not exposed externally through an ingress gateway.

      You can configure the physical connection to the Kubernetes cluster and then synchronize the application resources that run the internal services to create tests and stubs in Rational® Integration Tester.

      See Testing internal services in Kubernetes.

    • Enhanced the connection resilience for an IBM® WebSphere® MQ transport

      The connection resilience is enhanced so that you can now configure the connection resilience in an WebSphere® MQ transport to treat MQRC_NOT_AUTHORIZED errors in the same way as errors that indicate a problem with the MQ connection.

      See MQ Transport: Advanced settings.

    • Enhanced JSONPath and XPATH field actions

      The JSONPath and XPATH field actions are enhanced to allow more fine-grained control when you work with repeating elements. You can now extract the entire set of repeating data or extract any specific individual element.

    • Enhanced stub editor

      The stub editor is enhanced such that when you edit the content of a database stub, the internal datatypes of the columns are now shown in the headers. You can understand the limitations that apply to the content.

    • Sample program to list the state of stubs in Rational® Test Control Panel

      A sample program is now provided that demonstrates the usage of server REST APIs to enumerate domains, environments, and stubs to list out their current status. You can use the example program as the base when you want to implement non UI-based services such as alerts when stubs move into a broken state.

    • Option to stop stubs that are running in Rational® Test Control Panel

      When you want to delete a project from the Rational® Test Control Panel administration page, you can now specify if you want to stop all stubs that are running within the project.

Deprecated capabilities

You can find information about the capabilities that are deprecated in this release and are planned for a removal in a future release.
Note: You can contact the IBM Support team if you have any concerns.
  • No capabilities are deprecated in this release.

Removed capabilities

No capabilities are removed in this release.

Installing and upgrading

You can find information about the installation and upgrade instructions for IBM® Rational® Integration Tester.

Installing Rational® Integration Tester

For information about installation, see Installing Rational Integration Tester.

Installing Rational® Test Control Panel

For information about installation, see Installing Rational Test Control Panel.

Upgrading Rational® Integration Tester

If you use Installation Manager, you can find the upgrade requirements in Rational Integration Tester upgrade information and requirements.

If you use the stand-alone installer to install the software packages, you cannot upgrade the product software. You must uninstall the previous version of the product software and install the latest version by using the stand-alone installer.

Upgrading Rational® Test Control Panel

If you use Installation Manager, you can find the upgrade requirements in Rational Test Control Panel upgrade information and requirements.

If you use the stand-alone installer to install the software packages, you cannot upgrade the product software. You must uninstall the previous version of the product software and install the latest version by using the stand-alone installer.

Known issues

You can find information about the known issues identified in this release of Rational® Integration Tester.

Table 1. Release documents - Fix list and known issues
Product Download document Knowledge base
Rational® Integration Tester Release document Knowledge articles

Known problems are documented in the download document for each product and in the form of individual technotes in the Support Knowledge Base:

Note: Starting from 9.5.0 a single fix list document and a single download document is used for all products.

The knowledge base is continually updated as problems are discovered and resolved. By searching the knowledge base, you can quickly find workarounds or solutions to problems.

Contacting IBM Rational Software Support

  • For contact information and guidelines or reference materials that you might need when you require support, read the IBM Support Guide.

  • For personalized support that includes notifications of significant upgrades, subscribe to Product notification.

  • Before you contact IBM Rational Software Support, you must gather the background information that you might need to describe your problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
    • What software versions were you running when the problem occurred?
    • Do you have logs, traces, or messages that are related to the problem?
    • Can you reproduce the problem? If so, what steps do you take to reproduce it?
    • Is there a workaround for the problem? If so, be prepared to describe the workaround.