IBM Support

Rational Test Workbench Fix Pack 1 ( for 8.5



IBM Rational Test Workbench is available for download. It contains fixes to version 8.5 components including all predecessor fix packs.

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.
The information center provides you with user assistance for the product. You can view, browse, and search online information related to the product. You can also visit IBM Product information page to browse for additional information centers.
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.

Installation Instructions

<!-- EDIT TEXT IN BLUE --><a name="INSTALL"></a>]Install the Rational Test Workbench Fix Pack update using the Update wizard in IBM Installation Manager.

  1. Download the software from Fix Central.
  2. Open Installation Manager, click File, and select Preferences.
  3. Click Add Repository and browse to the location of the folder that contains the downloaded files.
  4. Start the IBM Installation Manager.
  5. Click Update and follow the instructions in the wizard.

[{"INLabel":"Rational Test Workbench 8.5 Installation Guide","INLang":"English","INSize":"4995","INURL":""}]

Download Package

The following sections provide detailed information related to this release.

How critical is this fix?

Impact Assessment
Impact Description
This release is a maintenance release of Rational Test Workbench 8.5. It contains 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

Known issues for Rational Performance Tester are described in the Rational Performance Tester download document.

Known issues for Rational Functional Tester are described in the Rational Functional Tester download document.

For Rational Integration Tester, you should be aware of the following.


38426On Microsoft Windows, if users attempt to uninstall, or rollback Rational Integration Tester Agent and Rational Test Control Panel components at the same time and both are installed as Windows services and both services are running and stubs have been run after the Agent service was started, uninstallation will fail, warning that prunsrv.exe could cannot deleted. If this occurs, user must delete the files from the installation directory manually before starting a new installation.

This problem may also occur when upgrading from 8.5.0 to or when rolling back an installation to 8.5.0.

To avoid this problem, users should either uninstall/rollback the components separately or stop both Windows services before starting the process.

CICS DPL virtualization JVM process

When using the CICS DPL virtualization solution, the CICS JVM process must be configured to have a maximum Java heap size of at least 512M. In IBM’s testing, values of less than this led to JVM failures during recording or virtualization of CICS programs.


Side-by-side installation of different versions of Rational Integration Tester is not supported.

If such installations are performed then users should note that the multiple versions will share the same start-up splash screen cause confusion in the version numbering.

Help/About must be used to determine the correct version number.


After uninstalling Rational Integration Tester Agent, Rational Test Control Panel or Rational Integration Tester proxies on a computer running Microsoft Windows XP, some users have reported seeing the error “Problem with executing "C:\Program Files\IBM\RIT-AgentNonDefault\prunsrv.exe" in the Installation Manager log.

This problem has no functional impact; the product will still have correctly uninstalled.


If a performance test is configured to start a stub on Rational Test Control Panel and that stub is already running, another instance will be (correctly) started for the performance test.

However, when the performance test stops, both instances of the stub will be stopped, not just the one that was started for the test.

Note: This does not apply to stubs that are already running but which are not configured to be used in the performance test - they will continue to run after the test ends.


When a Rational Test Control Panel scenario is loaded into Rational Integration Tester (by means of either the Test Suite scenario editor or the Performance Test configuration dialog), scenarios for all domains / environment are listed rather than just the domain/environment the user is currently working in.

If the test is then executed in an environment in which the stubs in the scenario have not been published too they will fail to start.


Due to the way in which table names are extracted from SQL when using the new integrated database problems can occur when working with case-sensitive, non-schema qualified table names. Specifically if a user is working with

- a case-sensitive database

- and with a mixed-case table name

- and with SQL that does not use schema-qualified table name

- and that SQL that does not quote the table name

Then TABLE NOT FOUND errors may be reported when using the integrated database. The workarounds are to either change the SQL to be schema qualified or to use the non-integrated schema approach where a second database schema is required.


Some users have reported that the Message Difference Window is slower to open on the 8.5 release (compared to the release) on very large messages (typically 1 megabyte messages).


If a user has run a stub from a project on an Agent via Rational Test Control Panel, stopped that stub (but left the project deployed to the agent, that is, has not run other stubs on that Agent yet) and then publishes a new version of the stub from the same project number to Rational Test Control Panel and then immediately attempts to start that stub then a failure will occur.

This is because Rational Test Control Panel believes that the project already deployed to the Agent contains the new stub and instructs the Agent to start it without deploying the new version of the project file.

A workaround to this is to use the Stop All Stubs option on the Rational Test Control Panel dashboard which forces all projects to be cleared out from Agents.


Users should note that JDBC database virtualization is not supported against IBM DB2 version 8.x.

The oldest supported version of DB2 for JDBC virtualization is 9.5 (on distributed) and 9.1 (on System z).


If, when importing a .NET object into Rational Integration Tester’s Schema Library, a user chooses a file that is not a .NET assembly (for example, an XML file) then errors can occur.

These errors occur in Microsoft Windows native libraries and cannot be handled by Rational Integration Tester. In the 8.5 release, Rational Integration Tester does some additional checks before attempting to ask the native libraries to load the assembly to reduce the number of error conditions.

However, errors may still occur if a user attempts to load a file that is not a .NET object into Rational Integration Tester.


Rational Test Control Panel now has the ability to clone running stubs. This means that a second (or subsequent) copy of a stub can be started up on a new agent using exactly the same configuration as the existing stub.

This is useful when using stubs for Performance Tests as, for some transports, this allows round-robin allocation of messages to occur which will result in higher throughput than from a single stub.

If such a configuration (multiple copies of the same stub running on different agents) is saved as a scenario in Rational Test Control Panel then it will not load back correctly, not will it load into Rational Integration Tester (from the test suite editor, for example) correctly.


If a Rational Integration Test suite scenario has a reference to a (local) stub as ‘blank’ in the References grid (that is, not ‘Live System’ and not a specifically selected stub) and a stub is already running for the referenced operation then, when the test suite starts, the running stub will be stopped by Rational Integration Tester (thus reverting message to the live system).

This may cause user confusion as they had not explicitly configured the scenario for ‘live system’.

Note: This can be worked around by explicitly stating which stub should be used in the scenario editor.


Use of –clean argument when Rational Integration Tester or Library Manager will not start

Problems can sometimes occur when Rational Integration Tester does not properly resolve multiple versions of the same JAR file correctly.

Multiple versions may be present within an installation because third party JAR files may each include a different version.

If incorrect dependency information is stored within the Eclipse workspace cache then it will not correct itself. One common symptom of this problem is that when a user runs Rational Integration Tester, the splash screen appears, then disappears but Tester never starts.

The same issue can occur when running Library Manager, although in this case, as there is no splash screen, it will appear to the user as if Library Manager has just failed to start.

Although one workaround is to uninstall and re-install Rational Integration Tester it is possible for a user to force cached dependency information to be removed and re-evaluated and, in the majority of cases, the problem will then correct itself.

To force the Eclipse environment to delete dependency information GHTester.exe must be started from the command line with the -clean argument specified, that is, from within the installed directory:
GHTester.exe –clean on Windows and ./GHTester –clean on Linux.

Rational Integration Tester will take longer than usual to start when -clean is specified.

For Library Manager use:
LibConfig.exe –clean on Windows and ./LibConfig –clean on Linux.

The same problem can occur in RTVS and RPTS installations with the Rational Integration Tester Agent.

In this case diagnosis and remediation is more difficult as there are multiple executable files and the correct one must be used. In these cases IBM Support should be contacted.


Rational Integration Tester does not support native JMS implementation of IBM WebSphere Application Server if security has been enabled

Rational Integration Tester cannot currently access the JNDI of WebSphere Application Server (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 after the problem has been resolved.


Slow Fail Execution Is Not Supported When Running ‘Now’ on a Remote Agent

GH Tester 5.4 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 Rational Integration Tester 8.0.1) when scheduling a test for future execution via Rational Test Control Panel 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 Rational Test Control Panel running as a service

Startup and shutdown batch file scripts are provided with Rational Test Control Panel to start and stop it from the command line. On Microsoft Windows, shortcuts to these scripts are provided in the Start Menu.

Note: On Microsoft Windows, if Rational Test Control Panel 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.


Overwrite Expected Field for Filters

Within 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.

AIX Performance Testing Does Not Support the sysstat Probe
The sysstat probe is not provided for IBM 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://<server>: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 Error
On some Microsoft 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 Factory
Some 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 Freeze

Some users have encountered software freezes on Microsoft 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.

Note: Users who experienced this problem while using computers with NVIDIA graphics cards found that upgrading to the most recent driver for their graphics card resolved the problem.

GHDotNetUtils Must Be In the .NET Global Assembly Cache
If you are using Rational Integration Tester/.NET integration, 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, for example: gacutil /i GHDotNetUtils.dll

Date Formatting Strings
Rational 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 GH 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.

Launching the ‘Tools Application’ (Source Control option on Menu) Displays License Warning
If 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 Panel
Depending 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 case
Although project resources can be renamed, it is not possible to simply change the case, that is, 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.

38005If a Rational Integration Tester project results database is created on MySQL on Linux, the MySQL system variable lower_case_table_names in the my.cnf file must be set to 1. On Linux systems, this is not the default setting.

37010When Rational Integration Tester is installed on Apple Mac systems running OS X 10.8.4, some users are still experiencing software hangs when running Rational Integration Tester or Library Manager.

The reason why the software hangs on some Mac systems and not on others is still being investigated.

36796In Recording Studio, the information window that displays details about warnings or errors that have occurred while recording truncates some information.

For example, recording rules used by the HTTP proxies will typically be truncated. This is by design. The full text can be see in the Rational Test Control Panel activity log.

37069When Rational Test Control Panel is started, a large number of JAX-RS warnings will be output to the stdout (console) output.

These will be of the form "WARNING: The class was already added to the JAX-RS runtime. The runtime is ignoring this value.

Check that this class was not returned in the subclass getSingletons() and getClasses() methods." These can be ignored because they do not indicate a problem.

Linux root/non-root installation notes

The 8.5 components can be installed on Linux as a non-root user. Alternatively, components can be installed as root and then run as non-root.

The Network Capture (pcap) component of Rational Integration Tester requires root access and cannot be installed as a non-root user.

Most Linux administrators will be aware of file/directory ownership issues when performing these types of installation. The following known issues should be considered.

31329All users must be in the same group to be able to run/view reports

When a report is generated in Results Gallery Tester will create a directory called /tmp/ghtester5reports.

This directory will be owned by the user that creates it (which may be root). When another user attempts to run a report then, if they’re not in the same group, they will be unable to write to the same directory and the report generation will fail.
The workaround is to ensure that all users can write to this directory (for example, by making them all members of the same group)

30778If Rational Test Control Panel is installed as root but run as non-root then it will fail

This is caused because directories used at runtime for logging information have been created by root and therefore cannot be written into by a non-root user.

This problem does not occur if Rational Test Control Panel was installed as a non-root user. If Rational Test Control Panel was installed as root and a user wishes to run it as non-root then directory permissions must be changed.

For example, from within the Rational Test Control Panel installation directory issue the commands:
  • chmod a+w logs
  • chmod a+w logs/*
  • chmod a+w /var/rtcp
  • chmod a+w /var/rtcp/*

Rational Test Control Panel should now run as a non-root user. An alternative solution that may be preferred by some administrators, is to change the directory that Rational Test Control Panel writes information into. A Technote has been published here describing how to do this:

Globalization issues


Rational Integration Tester is a Swing based Java application. Java/Swing uses visual cursor movement when working with bi-directional text in user-editable fields.

This means that the cursor arrow keys and the delete/backspace function will always operate visually (that is, left moves left) which may not be the expected logical movement.


Not all Unicode characters (especially the glyph-style characters) can be rendered using all fonts. For example, very few fonts contain a glyph for the U+0904 (DEVANAGARI LETTER SHORT A) character.

Rational Integration Tester’s default behavior means that it will not attempt to find a font that does contain that character. This means that messages containing this character will not render correctly.

The workaround is for the user to use the Rational Integration Tester font preferences to select a font that is capable of rendering these characters.


Dates in ISO format in message nodes will not be rendered according to the preferred operating system date format (when not running in English) in the Message Difference Window.

Changing this behavior would require making changes that could invalidate ‘expected messages’ in existing projects causing tests to fail. For this reason it has been decided not to change the rendering of these nodes.


Attempting to publish a message to an IBM WebSphere MQ Queue Manager using a character set that WebSphere MQ will not support will result in a failure.

This is as-expected and is not a Rational Integration Tester fault. For example, it is possible to publish a message containing the string 叱る亜うぃんをいはるいうはにぽげきんぼ if the character set on the publish action is set to 33722 but not if it’s set to 29626 because WebSphere MQ does not support that.


When attempting to install multiple products at the same time (for example, Rational Integration Tester and Rational Integration Tester Platform Pack) warning messages may be displayed in Installation Manager indicating that not all the products in the selected set provide the same set of languages.

Both Rational Integration Tester and Rational Test Control Panel have been translated into the same set of 14 languages and this warning can be ignored.


Attempting to connect to a DB2 database using non-ASCII user names may result in the error “cannot convert Unicode string to Ebcdic string” being displayed.

For example, attempting to connect using the default Russian administrator user name of "администратор" will show the error, but connecting using “administrator” will not. The workaround is to use the ASCII forms.


Arabic numbers pasted into a numeric control with up and down increment arrows (for example, the Minimum length field when setting up length validation in the message editor) will revert to Western numerals when the up/down increment arrows are clicked.


When running Library Manager on a non-English operating system the network card information displayed may contain corrupted characters.

This is due to a problem processing Unicode characters in third party software used by Library Manager to access the network card details.

GH Tester known issues that are still relevant to Rational Integration Tester

Test Cycles and Coverage Reports
If you are using Test Cycles and want coverage reports, the applicable tests must still be executed from within a test suite (that is, 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 Window
Validation 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 Control
Rational Integration Tester now uses a different method of creating file names 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 Events
When 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 IBM WebSphere 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 View
Sometimes adding a service component to the logical view will not add it to the diagram.

10905: User Names Containing “#” Character
The 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 Action
Cmd.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


Issue with SSL tab referencing one of a number of identity stores

In 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 Modifications
If 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: This problem can be avoided by selecting the user preference, “Run from Disk” as opposed to “Run from Memory”.

User Permissions on non-Windows Platforms
It 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-Microsoft 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.

Results Rendering
The 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 Messages
Some message fields may be displayed as invalid (red “x”), even though they are valid fields/messages.

If 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 Processes
The BusinessWorks private process transport uses HTTP as its primary communication method, but the “Publish” test action of Rational Integration Tester 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 (that is, 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

The following new features and functions have been added in this releases.

Queue prefixesThe prefixes used by Rational Integration Tester when creating IBM WebSphere MQ model queues for the sift-and-pass-through capability for message-based stubs have been changed to be more consistent.
"rit.stub." "AMQ.RIT.STUB."Distributed WebSphere MQ
"rit.diverted." "AMQ.RIT.DIVERTED."Distributed WebSphere MQ
This may impact clients' security requirements around these queues.
Stub startupA change has been made to the behavior of stub starting when the Rational Test Control Panel REST API or Apache Ant tasks are used.

Previously, if no stub version information was provided, the earliest version of the stub would be run. This has been changed so that it is the latest version of the stub that is run.
Subscriber action timeoutsPreviously, subscriber actions created by means of message exchange patterns had a timeout set to 5000ms. This has now been changed so that the timeout value is taken from the preferences setting used elsewhere.
HTTP-based stubs - Filtering by sub-pathsRational Integration Tester has been enhanced to allow HTTP-based stubs to filter based on sub-paths within the resource path. Previously, if the resource path was set to filter, for example, for ""/customer"", a request for ""/customer/orders"" would not be matched and a 503 error would be displayed. It is now possible to instruct a stub to match any request where the first part of the stub matches the filter regardless of sub-path.

This functionality is enabled by selecting the new ""Allow sub-paths"" check box located to the right of the ""Resource Name"" field on the Stub tab of the Operation window in the Logical View of Architecture School. The check box enables matching of sub-paths, so if a stub is listening for messages with a resource name ""/addNumbers"", selecting the ""Allow sub-paths"" check box will enable the stub to also receive messages destined for a resource named ""/addNumbers*"" where ""* "" is any sub-path (/mypath, /123/abc).

If the ""Resource Name"" path is populated on operation creation, the ""Allow sub-paths"" check box should be selected because allowing sub-paths is the new default behavior.

Note: For operations created by earlier versions of Rational Integration Tester, the ""Allow sub-paths"" check box is not selected by default because this would cause existing stubs to start matching more messages. Therefore, the ""Allow sub-paths"" check box is primarily intended for new operations created in this release of Rational Integration Tester or later.
HTTP proxy loggingAdditional logging has been added to the Rational Integration Tester HTTP proxy to make problem resolution easier. In particular, more output is provided if the log level is set to "FINEST".

This is controlled by the file in the Rational Integration Tester installation directory. The default log file location is %h/ghproxy-%g.log, where %h is the ""home"" folder of the user who is running the process. When running as a service, this is usually C:\Windows\System32\config\systemprofile.

The logging level is controlled by the file (and requires a restart to pick up changes). The HTTP proxy code is in packages under com.greenhat.

The default log level at installation time is expected to be "INFO" (shown by com.greenhat.level=INFO at the end of the file).
Default report templateWhen selecting a default report template (in Results Gallery), Rational Integration Tester now explicitly looks for DetailedReport.xsl instead of assuming that it will be the first one in the list.
Rational Test Control Panel /OSLC client integration improvement - iconsWhen used by means an OSLC interface (for example, from IBM Rational Quality Manager), Rational Test Control Panel now provides stub and scenario icons to the delegated user interface displayed in the OSLC client. These icons are consistent with the stub and scenario icons used in Rational Test Control Panel
Rational Test Control Panel /OSLC client integration improvement - deployment plansWhen creating or modifying a deployment plan in IBM Rational Quality Manager by means of the OSLC integration to Rational Test Control Panel, if users elect to use an existing deployment, the state of the existing virtual services (running, deployed, and so on) will be displayed to help users to make the correct selection.
Recording Studio - Regular expression-based searchesRecording Studio has been enhanced to support regular expression (RegEx)-based searches. If users wish to use a RegEx to search for events, they should select the new check box on the finder panel (Edit > Find on the menu bar) in Recording Studio. When the check box is selected, messages are searched for RegEx matches. When the check box is cleared, messages are searched only for string matches.

Note: RegEx searching is case sensitive but normal searching is case insensitive, so searching for literal ""h"" as a RegEx may return fewer matches than searching for the same literal without RegEx matching.

Recording Studio has been enhanced to offer a new "Jump To" option on the right-click pop-up menu for a recorded event. This option will select and scroll to the corresponding message in a "pair" automatically. For example, if a request is highlighted, "Jump To" will jump to the corresponding reply (for that request). This is useful when trying to find a message pair in a long list of events from which to create stubs or operations. The option can be chosen only when one event at a time is selected.
Recording Studio - Search filtersRecording Studio has been enhanced so that users can convert search results into a search filter. This enables users to progressively search within search results by applying layers of filters. Each of these filters can be removed to show the longer list of events again.
Recording Studio - Search feedbackRecording Studio has been enhanced to offer feedback to the user when a search is being performed. This is so that the user can see progress when searching through a large number of events. Previously, users could think that Rational Integration Tester had hung. Progress through events is shown in the text at the top of event table. After the first result has been received, this information is available in the tooltip for this text.
Recording Studio - Column filtering in Events tableRecording Studio has been enhanced so that a user can determine whether a column is being filtered upon. This is shown by the addition of an asterisk ("*") at the end of the column name in the events table. For example, if a user has added a filter to the "Description" column, "Description*" is displayed.
Recording Studio - Filter window improvementA change has been made to the window that is displayed when users select a column to filter in Recording Studio. Previously, the drop-down lists in the Filter window contained an entry for each unique description found in all the recorded events. When the number of events is large, this list takes a very long time to populate (which can give make it seem that Rational Integration Tester is hanging) and is of limited use to user because it is not practical for them to scroll through the hundreds of descriptions to find the one that they want.

The functionality of these drop-down lists has been modified to be a most recently used (MRU) list of filters. When users define and use a filter, it will be added to the MRU list for that filter. The MRU is persisted across sessions. This enables a user to switch quickly between filters that they have previously defined.
JDBC driver - Java version supportIn all earlier releases of Rational Integration Tester Platform Pack, the JDBC driver supplied by IBM that provides JDBC virtualization capabilities was built against the Java JDBC version 3 specification included within Java 1.5. This could lead to problems if it was used with a client application that was specifically using features added into the Java JDBC version 4 specification introduced in Java 1.6 because the Rational Integration Tester JDBC driver would not support them and the client application would fail.

In or later, IBM ships two versions of the JDBC driver. Users must decide which one to install based on their knowledge of the client application and the container (for example, application server) in which the client application is running. In general, if the container is Java 1.6 compatible, use the 1.6 version of the driver. If the container supports only Java 1.5, the 1.5 driver must be used.

The file names of the JAR files match the Java version as follows:
  • JDBC 3 / Java 1.5 use greenhat.jdbcdriver.jar and jsqlparser15.jar
  • JDBC 4 / Java 1.6 use and jsqlparser15.jar

If the container is IBM WebSphere Application Server, installation of the driver is performed by means of a set of scripts provided in Rational Integration Tester Platform Pack. These scripts have been updated to always install the JDBC4 version of the driver because all supported versions of WebSphere Application Server use Java 1.6.
Schema data and Java objectsA change has been made to the way that schema data is generated for (plain old) Java Objects (POJOs). Previously when selecting a class to apply within a message editor, the full class name, including package name, of each Java class was displayed in the right-click menu for schema selection. These names could be extremely long and the most important part (the actual class name) was at the far right, meaning that, in some cases, it was not displayed, making selection difficult. Rational Integration Tester now attempts to use the short class name instead of the full path. The full class name is still available by hovering over the menu item.

This behaviour can be turned off (that is reverted to pre- behavior) if desired by setting the following -D JVM argument in Library Manager:
Schema mapper and Java objectsWhen generating a Java object schema, properties of type "Object" are now treated as Rational Integration Tester schema "Any" types. This means that the schema mapper of Rational Integration Tester can be prevented from incorrectly converting a known type back to Object, which can result in a failure to create a valid serialized object for publication.

This change has side-effects, so users must opt in to it. To enable this functionality, the following -D argument must be specified in Library Manager for both Rational Integration Tester and Rational Integration Tester (if they are used in tests or stubs running on the agent): -Dgreenhat.schema.mapper.testAny=true"

If this option is not specified, there will be no change in behavior from earlier releases of Rational Integration Tester.

Note: Any previously generated schemas will have to be recreated before this change can take effect.

[{"DNLabel":"Rational Test Workbench","DNDate":"13 Aug 2013","DNLang":"English","DNSize":"2500000000","DNPlat":{"label":"Windows","code":"PF033"},"DNURL":"","DNURL_FTP":" ","DDURL":null}]
[{"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":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Problems (APARS) fixed

Document Information

Modified date:
20 July 2018