IBM Support

Rational Test Workbench 8.0.1



IBM Rational Test Workbench 8.0.1 has been made generally available on the IBM Passport Advantage website.

Download Description

Table of Contents
Sections Description
This section provides an overview on what is new in this release with a description of any new functions or enhancements when applicable.
This section provides information related to the impact of this release to allow you to assess how your environment may be affected.
This section provides important information to review prior to the installation of this release.
This section provides the direct link to obtain the download package for installation in your environment.
This section provides the installation instructions necessary to apply this release into your environment.
This section contains a link to the known problems (open defects) identified at the time of this release.
Supporting Documentation
Document Description
Click to review the detailed system requirements information for a complete list of hardware requirements, supported operating systems, prerequisites and optional supported software, with component-level details and operating system restrictions.
Click to review a complete list of the defects (APARs) resolved in this release including a list of resolved defects for the entire version family.


No prerequisites required.

Installation Instructions

This installation guide provides the basic information for installing this offering:


Download Package

Download options
Access type Description
Passport Advantage Passport Advantage and Passport Advantage Express clients are required to sign in to download the software package.
IBM OEM software IBM Software Group OEM offerings are designed for partners who develop and sell business solutions with embedded or bundled IBM middleware software. Clients with Flexible Contract Type (FCT) license purchases and IBM Business Partners must sign in to download the software package.

How critical is this fix?

Impact Assessment
Impact Description
This release is a service release of Rational Test Workbench. It contains new features as well as fixes for client-reported and internally found defects.

Problems Solved

Click the Fix List link in the table of contents above to review a list of the problems solved in this release.

Known Side Effects

The following defects were not resolved in this release.

Defect title
Upgrade Installations and Rollbacks (When Products Have Been Installed as Windows Services) FailOn the Windows platform several components can be installed as Windows Services. These are the Rational Integration Test Agent, the Rational Test Control Panel and the Rational Integration Platform Pack Proxy.

If you attempt to upgrade or rollback an installation of these products when they are installed as a service then the process will most likely fail. The ‘uninstallation’ will appear to succeed but during the installation of the upgraded software (or the previous software in the case of a rollback) errors will occur stating that files are in use or could not be removed.

These problems can occur regardless of whether the service is running or not at the point of installation. Please note that this problem only occurs on the Windows platform and only for products which have been installed as services.

The problem is caused because Installation Manager is not able to completely remove the service during the un-installation phase. The service will remain in the Windows service list in a disabled state until reboot. Whilst it is in this state the upgraded service cannot be installed.

The workaround to this problem is for users to first uninstall the existing version of the software, then reboot the machine, then install the new version. i.e. Do not use the upgrade or rollback capability. It is advised that users stop the service before attempting the uninstall.

When uninstalling Rational Test Control Panel ensure you do not select the option to delete the workspace and make a note of the workspace directory. When you install the new version ensure you enter this directory as the workspace location and all settings and published stubs will be preserved.

If you do not know where the workspace directory is then you should open the following file:

<RTCP install location>\webapps\RTCP\WEB-INF\classes\

And look for the line containing the ‘workingDirectory’ key.


If this advice is not followed and the installation does fail then users are advised to first reboot their machine (to clear out the service). After reboot, confirm that the service has gone from the list of Windows services and then manually clear out the installation directory. It should then be possible to start a fresh install.

If you set the Rational Test Control Panel workspace to inside its installation directory (which is not a recommended approach) then be sure not to delete this directory or you will lose all RTCP configuration.

Note that this problem exists in all version 8.0.x and the same workaround advice apples to upgrades to the 8.0.0.x fixpacks.

Changes have been made as part of the 8.0.1 release to avoid this problem occurring in the future. i.e. Upgrades from 8.0.1 to fix packs and releases made at a later date should not encounter this problem.

Tester does not support WebSphere Application Server’s native JMS implementation if security has been enabledRational Integration Tester cannot currently access WAS’s JNDI (required for JMS) if security has been turned on. IBM is currently investigation how to configure Rational Integration Tester such that this works and expects to issue a TechNote once the problem has been resolved.
Slow Fail Execution Is Not Supported When Running ‘Now’ on a Remote AgentVersion 5.4 of Tester introduced the concept of ‘slow fail’ to Test Suites. When a suite is run with this option turned on tests will not immediately stop when an individual test action fails. Instead they will continue so that users can see if future test steps succeed. Although this functionality is supported (in 8.0.1) when scheduling a test for future execution via RTCP it is not supported if you run a test suite ‘now’ on a remote agent using the Run… dialog.
Using the Shutdown.bat file (or shortcut) will not stop RTCP running as a serviceStartup and shutdown batch file scripts are provided with RTCP to start and stop it from the command line. On Windows shortcuts to these scripts are provided in the Start Menu. Note that, on Windows, if RTCP is running as a service then the shutdown batch script cannot be used to stop it. You must either using the control panel or issue a net stop IBMRTCP statement on the command line.
Oracle Java 7 layout bugThe behavior of a UI control widely used by Tester (JTextPane) changed significantly in Java 7, which has been used by Tester from release 8.0.0. Specifically, the way line breaks were automatically added changed. This adversely affects Tester when messages without spaces in are displayed. The Field Viewer in Recording Studio has been modified to work around this but other parts of the tool have not yet been changed. This was logged with Oracle as :
Varchar(256) in MySQLThe MySQL Results Database creation script provided with Rational Integration Tester defines a number of columns as VARCHAR(256). If this script is used on a MySQL instance that is using the InnoDB data engine in a database defined as using the UTF-8 character set then the following error will occur:
ERROR 1071 (42000) at line 1296: Specified key was too long; max key length is 767 bytes
This can be avoided by changing the following table definitions to use columns of 255 length:
Overwrite Expected Field for FiltersWithin the Message Difference Window, Overwrite Expected Field only works for filters (within stubs) when updating leaf nodes. Message structures cannot be copied when viewing filter actions. The whole message can be replaced while viewing the filter actions, using overwrite expected message, but overwriting part of a message currently only works for the validate field action.
Some Changes made in the Message Difference Window do not get flagged as dirty on closeChanges made to field values on the ‘expected side’ of a message displayed in the Message Difference Window do not cause a save notification when closing the window. You must manually save before close.
WaitForExit messages in Agent logChanges to the way that the Rational Integration Tester Agent logs information mean that users will now see the internal Java method name from which the log is being generated. This is part of the change to ensure that Agents log information to a file correctly when run as a Windows service. The console output will now show messages as coming from “WaitForExit”. The “WaitForExit” statement is not relevant to the actual information provided in the output.
AIX Performance Testing Does Not Support the sysstats ProbeThe sysstats probe is not provided for AIX. If a user attempts to configure an AIX-based performance test to use this probe then the following error will be shown in the console : [Error] Probe ERROR: http://localhost:4476 - Probes failed to start - Failed to start probe: System Statistics - java.lang.UnsatisfiedLinkError: ghsystemstats (Not found in java.library.path). You must remove this probe from the configuration of the test.
Stopping an Agent Results In Windows Event Log ErrorOn some Windows installations IBM has seen errors raised in the Windows Application Event Log when the Rational Integration Tester Agent service is stopped. This error occurs during the shut-down process of the service and does not affect the functionality of the Agent.
Component Tree Does Not Show Complete Project In Test FactorySome users have reported instances where the Test Factory Perspective does not show the complete list of project resources in the component tree. Rational Integration Tester has required re-starting to correctly display the tree. This problem has not yet been replicated within IBM’s labs and its cause is currently unknown.
User Interface FreezeSome users have encountered software freezes on Windows, particularly when moving the Rational Integration Tester user interface from a laptop screen onto an external monitor. This is believed to be caused by problems between the Java Virtual Machine and the DirectX video drivers in use on the machine. If this problem affects you then please try to resolve it by adding the following line to the GHTester.ini file in the installation directory:


This tells the JVM not to use DirectX. This has resolved the problems in all cases IBM is aware of so far although the UI does run more slowly. This issue has been raised with the IBM Java team.
GHDotNetUtils Must Be In the .NET Global Assembly CacheIf you are using Rational Integration Tester’s .NET integration then the GHDotNetUtils.dll file (in the root installation folder) must be added to the .NET Global Assembly Cache before .NET objects can be parsed.

Users wishing to use the .Net functionality will need to install the .Net SDK from Microsoft and register the dll manually e.g : gacutil /i GHDotNetUtils.dll
.NET 4.5 is not supportedTester’s integration with .NET has not been tested on .NET 4.5 and this is not a supported version of .NET.
Left-to-Right and Right-To-Left StringsIf a message element is a string that contains both left-to-right and right-to-left text in the same element then the string may not be displayed properly in the user interface. It will be published correctly.
Date Formatting StringsRational Integration Tester uses Java to format date strings for validation purposes. The IBM JRE acts differently from the Oracle/Sun JRE used by earlier versions of GHT Tester for one unusual format string.
Specifically, a date of "123" parsed using an input format of “yyy” with output format MMDDy will be formatted as “0101123” by the IBM JRE. Previous versions of GH Tester (using the Oracle JRE) would have formatted this as “010123”. This is unlikely to cause problems as it is unlikely customers will be using single-character year output format strings.
Library Manager ‘Browse For File’ dialogWhen you first open the browse/edit dialog from the Library Manager application (to select a file) the directory ‘up’ button will not work. If a different directory is selected the ‘up’ button will then work. This has been confirmed as bug in the IBM JRE.
Launching the ‘Tools Application’ (Source Control option on Menu) Displays License WarningIf you are running Rational Integration Tester using an evaluation license then when you launch the “Tools Application”, by choosing the Source Control option in the menu or by creating/editing a data model, a dialog will appear warning that you are using a trial license. This dialog will not appear once you have installed a full license.
Silent Install of Rational Test Control PanelDepending on how the silent installation response file has been generated the “Security Configuration” tool may still be launched at the end of the process. The imcl tool is known to work correctly and will suppress the dialog. As Rational Test Control Panel is a server-based product silent installations are not expected to be common but IBM will look to improve this in future releases.
To use imcl within the ${IM}/eclipse/tools directory run “./imcl-c”, specifying the response file when prompted.
The Agent Can Only be Started From its Installed Directory (Unix)On Unix, if an attempt is made to start the agent from a directory other than the one it is installed in then it will fail to start. For example:

/opt/GH/RIT-Agent/Agent -consolelog

Whereas if you are within the installed directory then:

./Agent -consolelog

works correctly.
It is not possible to rename a project resource by simply changing caseAlthough project resources can be renamed, it is not possible to simply change the case. i.e. A rename that changes “simpletest” to “SimpleTest” will not actually rename. This is because Tester uses the Eclipse framework to manage its files and Eclipse does not recognize this type of change.
Test Cycles and Coverage ReportsIf you are using Test Cycles and want coverage reports, the applicable tests must still be executed from within a test suite (i.e. coverage reports will not be produced for tests that are executed outside of a test suite).
Column Level Validation Cannot be Displayed in the Message Differences WindowValidation on table rows and cells performed within the SQL Query action works as expected and is displayed in the console accurately. If column-level validation is used, however, any differences are displayed correctly in the console, but they are unable to be displayed in the Message Differences window as it is currently only able to display row-by-row and cell-by-cell validation issues.
Duplicated Physical Resources when Using Source ControlRational Integration Tester now uses a different method of creating filenames for physical resources. For this reason, source control users may see duplicate items due to the way the project was updated/committed after the resource change. In this case, the newer/newly named resource should be kept.
webMethods Broker EventsWhen recording webMethods Broker events, some fields may be seen to contain null rather than their actual content. This occurs because elements wired to a byte-array by an IS to publish can only be un-wired by another IS, this is an internal mechanism of IS and cannot be overcome. This has been seen with the MQ adapter notifications for the “MsgBody” and “MsgBodyByteArray” fields, but may affect others. Further information can be found via Software AG support, incident number 5019024.
Logical ViewSometimes adding a service component to the logical view will not add it to the diagram.

If there are a small number of objects on the logical view then the zoom level may automatically set itself to a very high level.

10905: User Names Containing “#” CharacterThe Eclipse framework (and therefore Rational Integration Tester) does not support user names that contain the “#” symbol. This issue may result in the deletion of project files as Rational Integration Tester cannot interpret the full path to the user’s “Documents and Settings” directory for application preferences.

The workaround for this issue is to create a folder to use as a Rational Integration Tester workspace (for example,C:RIT) and edit TestEngine.ini (found in C:\Program Files\IBM\RationalIntegrationTester, by default) to point to it. The line below “-data” should be changed from “@user.home/.rit8/perf-workspace” to “C:/RIT/..rit8/perf-workspace”.

UNC Paths as Current Directory in Run Command ActionCmd.exe, used by the Rational Integration Tester Run Command test action, may return an error when trying to process a UNC path. More information regarding the resolution is available at
10158: Issue with SSL tab referencing one of a number of identity storesIn a project with multiple identity stores the GUI does not always correctly reflect the one selected.

If you select any identity store from the Identity Store drop down menu and click OK to close the transport window, Rational Integration Tester will select the correct identity store when processing the data. This can be seen when opening up the physical files in the Physical folder of the GH Project on your C drive. The HTTP file references the id of the selected Identity Store correctly.

Error scenario

If you select any identity store from the Identity Store drop down menu, but then reselect the Identity Store drop down menu it will not retain the selected id store and will default back to the first id store in the drop down menu. Clicking OK on the window will then rewrite the physical files on your drive to reference the first id store in the list. So this should be avoided until fixed.

Simultaneous ModificationsIf a message is opened in a message editor (for example, a Subscribe action) and the message differences window at the same time, changes made in one window will be overwritten or reverted when closing the other window. More specifically, the content of the window that is closed last will overwrite the content of the window that was closed first.

This also applies if the message differences window is used to correct messages used in a stub if the stub editor window is open. Note that this problem can be avoided by selecting the user preference, “Run from Disk” as opposed to “Run from Memory”.

User Permissions on non-Windows PlatformsIt is possible to perform actions in Rational Integration Tester that require the opening of IP ports less than number 1024. For example, if you create and run a stub configured to listen on port 80. On non-Windows platforms this operation requires the user to be an administrator. Before you can run Rational Integration Tester as an administrator, however, you must run the Library Manager as an administrator (this is due to the way the .rit8 directory is created under the user’s home directory). Similarly, if you want to run Rational Integration Tester as a non-admin user, you must first run Library Manager as that non-admin user.
WS SecurityCurrently only outbound actions are supported within the WS-Security node processor.
Results RenderingThe third party rendering engine has performance issues when dealing with larger reports, this may be alleviated by increasing the amount of memory allocated to the application.
Invalid Schema MessagesSome message fields may be displayed as invalid (red “x”), even though they are valid fields/messages.
SCMIf a newer version of Rational Integration Tester is installed after adding team providers to SCM, the providers will have to be reinstalled unless their installation is outside of the Rational Integration install folder (detailed in Rational Integration Tester Installation Guide).
TIBCO BusinessWorks Private ProcessesThe BW private process transport uses HTTP as its primary communication method, but Rational Integration Tester’s “Publish” test action does not support HTTP. Therefore, the Send Request/Receive Reply action pair should be used for testing private processes.

Error schemas are not supported (for example, if a process outputs an error schema rather than an end schema, the error schema/output is not supported in Rational Integration Tester).

Rational Integration Tester does not support the following content in private process schemas:

  • A “Choice” content option at the root of the schema
  • Pointing to an AE message from anywhere (i.e. inner or at the root) causes a known deserialization issue
  • The “Java Object Reference” type is not supported at any level
  • The inline WSDL message content option is not supported
If you get a connection error when calling a private process, please check the network settings. If you open the Designer Engine Custom Properties in the Physical View of the Architecture School perspective, you will find the host and port number. The host/port in the Physical View menu must match the host/port in the GHEnable.proj design time library in the BW project. The BW host/port can be set when the project is deployed.
Data Transfer Objects (DTOs)DTO support is currently limited to the following:
  • Classes with a default constructor and publicly visible member variables
  • Member variables must be primitives, wrapper objects, Strings or other objects within the JAR file
  • JMS providers who use the Context Class Loader to obtain message definitions

Change History

These new features apply to Rational Test Workbench, Rational Test Virtualization Server, and Rational Performance Test Server. Some of the features require Rational Test Virtualization Server and Rational Performance Test Server licenses.

Mainframe (z) Support:

  • Release 8.0.1 expands the support for the z mainframe. A new document, the z/OS Reference Guide, covering the new functionality has been added to the installation set
  • CICS Transaction Gateway Test and Record. A new CICS Transaction Gateway (CTG) transport has been added to the Architecture School perspective (logical and physical views). This allows for functional and performance testing of CICS transactions via the CTG. It is also possible to record transaction invocations made through the CTG in Tester’s Recording Studio perspective. These events can be used to create tests and datasets.
  • IMS Connect Test and Record. A new IMS Connect transport has been added to the Architecture School perspective (logical and physical view). This allows for functional and performance testing of IMS transactions via IMS Connect. It is also possible to record transaction invocations made through IMS Connect in Tester’s Recording Studio perspective. These events can be then used to create tests and datasets.
  • The technology that allows Rational Integration Tester to record messages put onto IBM WebSphere MQ queues without requiring any client configuration changes is now supported for Queue Managers running on z/OS. As with the existing distributed support for IBM WebSphere MQ, recording of individual queues or all queues can be performed.
  • The installation and configuration details in the z/OS should be studied carefully before this is installed and use. The following should be specifically noted:
    • Every message that is intercepted has an MQPUT1 to the Rational Integration Tester queue. This doubles the CPU cost of a MQPUT or MQPUT1. To reduce the overhead, select only the messages that you are interested in. Avoid intercepting all messages.
    • To avoid problems with the Rational Integration Tester queue filling up, you should have a low message rate of intercepted messages, for example 10's of messages a second.
    • Messages are not intercepted when:

      • The queue name is SYSTEM.* and AMQ.MQEXPLORER.*
      • Messages put to a QALIAS of a topic
      • Puts are the result of an integrated publish/subscribe action.

      Messages put to a QALIAS queue are recorded against the base queue.
  • Tester now supports virtualization of z/OS DB2 databases. The virtual database can run on a separate DB2 instance on z/OS or on the distributed platform. This allows users to create virtual databases that do not require z/OS to run.
  • IBM has used Rational Integration Tester to invoke web services hosted on CICS. IBM has also tested that a CICS transaction can successfully call a Rational-Integration-Tester-virtualized SOAP web service. Details on the CICS configuration used during this testing can be found it the z/OS Reference Guide.

Schemas, Formatters and Transports
  • Support for EDI X12 dictionaries has been added. Rational Integration Tester can create new messages from the X12 dictionaries and parse, edit and publish standards-compliant X12 messages. Validations will be applied as per the supported dictionaries. As with other messaging standards, Tester will attempt to parse incomplete or invalid messages and will also allow a user to construct and publish messages that do not comply to the standard dictionary in order to perform negative testing.
  • A new field expander (schema) has been added to allow for the parsing of hexadecimal strings into Byte Arrays. This allows, for example, a hex string contained in an XML element to be converted into a Byte Array so that a further field expander such as Copybook can be applied. [released as part of the fix-pack]
  • Support for Data Format Description Language (DFDL) grammars has been added. This allows Tester to import a DFDL-defined message structure and use that information to parse, edit and publish messages compliant to that grammar.
  • The http transport now supports message bodies that have been compressed using gzip.
  • It is now possible to configure WS-Security on a Publish action such that WS-x elements (such as WS-Addressing, WS-Security and the body) are individually signed rather than having to sign the whole message. It is also now possible to sign using the certificate chain. [released as part of the fix-pack]
  • It is now possible to add in header values for FIX messages in the Value and Store stabs of a publisher and Filter, Assert and Store tabs of a subscriber. This allows sending and validation of the FIX header structure when using the FIX schema. For a publisher any values specified here will override values that are set according to the FIX transport configuration such as SenderCompID and TargetCompID. Note that the header fields displayed are the superset from the latest version of the FIX 4.x standard. If a user is creating messages for earlier versions of the standard they must know which headers are appropriate for that version.

    If header values require validation in a subscriber then the root message validation must be enabled and configured to:
  • Accept fields in any order
  • Ignore additional fields in received messages [released as part of the fix-pack]

Stubs and Virtualization
  • Stubs built on the MQ (distributed), http and webMethods IS transports now support additional capabilities to control how they handle received messages. They can be configured to automatically pass-through a message to the real service if it does not match a defined case. A new action has also been added to allow a user to specifically cause the message to be passed on to the live system as part of the normal stub processing if required. An optional delay can be specified before the message is passed to the live system. It is also possible to configure the stub to automatically respond with a transport-specific error if the received message does not match a defined case.
  • Database virtualization has been extended to support Stored Procedures on Oracle, MySQL, DB2 and MS SQL Server. When a virtual database is learnt all stored procedure invocations and their responses will be added to the virtual database. The saved responses can be edited and filter criteria defined to control how the virtual database will respond given a set of input parameters to the stored procedure.
  • Rational Test Control Panel now allows a user to define a scenario, which is a saved set of pre-configured stubs that can be started as a single unit. This saves time and prevents errors when starting up a set of virtual services as each stub no longer needs to be configured and started individually.
  • It is now possible for a user to lock an environment in RTCP. This prevents other users from making changes to the virtual services that are running. This capability is available from within RTCP itself, via a REST API onto RTCP (also from ANT scripts) and from within Rational Integration Tester. This allows Testers to use RTVS in long-lived test cases without risk of another user changing the stub configuration and affecting the test outcome.
  • The support for REST-based virtual services has been significantly extended. The Recording Studio wizards will now automatically create REST-based stubs from recorded traffic and Tester will automatically detect message data in URLs and make this available to the stub without the need for script to process it.
  • The Message Difference Window (MDW) has been extended to support stubs. Users may open the MDW from the console output to understand how a message interacted with a stub’s filters. This allows testers to easily identify why their stub is responding as it is and allow ‘repairs’ to be made to quickly change this behavior.
  • Microsoft SQL Server virtualization now supports the JTDS driver as well as the MS SQL driver.
  • The default installation of Rational Integration Tester and the Rational Integration Tester Agent now includes two JVM arguments to force Java-6 behavior when IP ports are allocated. This means that if an http stub attempts to start on a port that is already in use it will automatically detect this and allocate a different port. This makes it easier to run the real and virtual service on a single machine. In previous 8.0.x releases user has to manually add –D arguments to the GHTester.ini files to get this behavior.
  • It is now possible to start a stub on an RTVS server as part of a test suite scenario. Previously all stubs used in test suites had to run locally within the copy of Rational Integration Tester. This allows test suites to run stubs without tps restrictions. When you run such a suite the Tester task monitor will show the stubs as individual items even though they are not actually running within Rational Integration Tester. As part of this the way in which stubs show progress has been modified:
  • If a stub is a cancelled or fails during start-up (before it is ready to accept messages) it will show 0% complete.
  • When the stub is stopped progress will jump to 99% before the shut-down process begins
  • At the end of the shut-down process the progress will change to 100%, regardless of whether errors occurred in shut down or not.

  • Rational Integration Tester now supports multiple versions of the sap JCO3 library (sapjco3.jar) and does not require a single specific version to operate correctly.

Usability and Efficiency
  • The default view in the stub editor has been simplified to make it easier for new users. Users may switch to an ‘advanced’ view to gain access to all of the features. The advanced view will automatically be used if a stub is opened that makes use of the advanced features.
  • A preference has been added to limit the number of optional fields created from a schema to prevent memory issues with extremely large schemas. Typically this problem would occur when using the Create Test from MEP feature on XSDs with broad and deep structures of optional elements. [released as part of the fix-pack]
  • Architecture School’s Schema Library now shows ordered lists of schemas for message protocols such as X12 that contain multiple ‘groups’ (e.g dictionaries).
  • When RTVS Agents register with RTCP it is now possible for them to register with user-defined attributes. These attributes can be used when determining which agent a stub should be run on. This is particularly useful when defining a scenario within RTCP as it removes the need to specify agents by name or IP address, thus making the scenario more resilient to environment change. For example, agent attributes can be used to express geographic location, operating system, performance and capability of the machine an agent is installed on. An agent matching given attributes will then be found when a scenario starts. These attributes can also be used when scheduling a test for later execution.
  • The Rational Test Control Panel user-interface has had a number of small improvements and changes made to it to increase usability and consistency.
  • The Tag Data Store dialog within Tester now remembers the selection status of environment and system tags meaning that if a user turns them off they will stay hidden.
  • When navigating through test results using Rational Test Control Panel’s Results Gallery feature Next and Previous now automatically expand the tree of results.
  • The Project->Refresh menu option now displays a progress dialog if it takes more than a very short period of time.
  • The Bindings table in the Environment Editor can be sorted by clicking on the headings.
  • When an element is marked as repeating [in the message editor] an icon appears immediately as visual feedback of the repeat.
  • The Rational Test Control Panel Agent view now shows the type of agents that are registered. Possible values are RTVS (can run stubs, performance tests and probes), RPTS (can run performance tests and probes) and Probe (can only run probes). This makes it easier for a user to understand the capability of the deployed agents.

WebSphere Application Server
  • It is now possible to use the JDBC Virtualization configuration from within Tester for an instance of WebSphere Application Server that has security enabled.
  • Changes have been made to Library Manager to make it easier to configure Rational Integration Tester for use with WebSphere Application Server’s native JMS implementation. However, see the Known Issues list at the end of this document as a problem will occur if security is enabled in WAS.

WebSphere MQ
  • Subscribe actions for MQ-based operations now support the non-destructive watch-mode. This allows Tester to ‘watch’ for a message being published to an MQ queue without having to subscribe to (and consume) the message. This is particularly useful in integration tests where Tester is being used to validate that a message has been published. As part of this work the UI for the watch-mode configuration across MQ, HTTP and EMS transports has been made consistent.
  • The API-Exit to enable MQ recording and sift-and-pass-through now supports MQ 7.1.x as well as 7.0.1.x on supported distributed platforms [Windows (32, 64bit), Linux (32, 64 bit), AIX (64 bit), Solaris Sparc (64 bit), Solaris x86 (64 bit)]. MQ 7.5.x is not currently supported.
  • The default number of Queue Manager connections for a physical MQ transport is now 5 (increased from 1). This setting defines the maximum number of connections Tester will make to the Queue Manager for that transport. If a user records, stubs and tests using the same MQ transport then a single connection is insufficient and some processes will block. Note that another workaround is to define separate transports for recording, stubbing and testing that are all configured to the same Queue Manager.

  • Rational Test Control Panel now offers a REST-based API that can be used to start and stop stubs and scenarios and lock environments. The Platform Pack includes example ANT scripts showing how this can be used as part of a build/test environment to automatically start virtual services as part of a continuous-integration test environment.

Test Results
  • A File Publisher has been added to the list of Result Publisher types. This enables a suite report to be published to a specified location on disk. The File Publisher will also write out results in JUnit XML format. [released as part of the fix-pack]
  • Support for Test Cycles has been added to the Rational Test Control Panel Result Gallery view.
  • The Rational Test Control Panel Results Gallery date/time search now returns all executions which started between the entered start/finish times, rather than requiring the execution to have finished before the finish time.

  • Rational Integration Tester now offers integration to IBM’s InfoSphere Optim product. This integration allows users of Rational Integration Tester to automatically perform Optim actions as part of test or stub start-up. For example, a user can initiate a test data refresh within Optim that causes a test data set used by a Rational Integration Tester stub to be reset to a known state without the Rational Integration Tester user having to understand how to issue Optim commands.

  • If a requirement linked to tests is deleted then the user is now warned that the deletion will impact tests. A search is run to find all of the tests linked to that requirement. The user is given the option of ‘in-lining’ the requirement into each test.

Recording Studio
  • The Recording Studio perspective has a new “Playback” button which will replay recorded events. The user can specify the “pacing” speed with which messages are published (as-fast-as-possible, defined interval or as-original). Rules and functions in the Rules Cache may be used to allow basic modifications to message contents as they are published. Playback will work on events that have been exported and re-imported (into the same project). [released as part of the fix-pack]

  • DB2 is now supported as a Results Database. The Rational Integration Tester installation includes a DB2 database script which is intended for use by DB2 DBAs. Rational Integration Tester, Rational Integration Tester Agent and RTCP installations all include a DB2 driver (which will automatically appear in Library Manager) to avoid the need to download it separately. Note that use of DB2 on Z does require a DB2 Connect license which is not provided with Rational Integration Tester.
  • The Library Manager configuration for using WebSphere Application Server’s JNDI to access MQ/JMS resources has been made simpler and clearer to set-up.
  • The Rational Integration Tester Platform Pack Proxy can now be configured to use a down-stream proxy. This is useful in cases where the system it is sending messages to can only be access via another TCP/HTTP proxy.
  • A default installation of the Rational Integration Tester Agent will now output information to a log file and the console window. Previously a great deal of useful information was only sent to the console output which meant it was lost of the Agent was running as a Windows service. If the service is configured to run as the Local System Account then, on Windows, the default directory for this log file will be C:\Windows\System32\config\systemprofile.
  • Support has been added for extended feature codes to enable additional capabilities. [released as part of the fix-pack]
  • It is now possible to install a Rational Integration Tester Agent in a mode that only allows the execution of probes. This type of installation does not require the Agent to be PVU-licensed and is intended for use in Performance Testing scenarios. [released as part of the fix-pack]

Test and Stub Actions
  • A new concept of Environment Tasks has been added to Rational Integration Tester. These allow ‘actions’ to be run prior to starting stubs to configure the environment to a known state.
  • The Stored Procedure action has been enhanced to allow for the assertion of result sets returned by the procedure. This includes both explicit ‘out’ parameter result sets and implicit result sets, such as the one returned by the ‘last’ select statement in a Microsoft SQL Server stored procedure. [released as part of the fix-pack]

[{"Product":{"code":"SSBLQQ","label":"Rational Test Workbench"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Installation","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
29 September 2018