IBM Rational Test Virtualization Server 126.96.36.199 has been made generally available and contains fixes to version 8.0 including all predecessor fix packs.
|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.|
|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.|
- Download the software from Fix Central.
- Open Installation Manager, click File, and select Preferences.
- Click Add Repository and browse to the location of the folder that contains the downloaded files.
- Start the IBM Installation Manager.
- Click Update and follow the instructions in the wizard.
The following sections provide detailed information related to this release.
How critical is this fix?
|This release is a maintenance release of Rational Test Virtualization Server 8.0. It contains fixes for client-reported and internally found defects.|
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
|Test Cycles and Coverage Reports||If you are using Test Cycles and want coverage reports, the applicable tests must be executed from within a test suite. 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. However, if column-level validation is used, any differences are displayed correctly in the console, but they are not displayed in the Message Differences window, where only row-by-row and cell-by-cell validation issues are displayed.|
|Duplicated Physical Resources when Using Source Control||Rational Integration Tester now uses a different method of creating filenames for physical resources. For this reason, source control users might see duplicate items, due to the way the project was updated or committed after the resource change. In this case, the newer or newly named resource should be kept.|
|webMethods Broker Events||When recording webMethods Broker events, some fields might appear 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 might affect other fields as well. For more information, see via Software AG support, incident number 5019024.|
|Logical View||Sometimes adding a service component to the logical view does not add it to the corresponding diagram.
If there are a small number of objects in the logical view, the zoom level might automatically set itself to a very high level.
|10905: User Names Containing “#” Character||The Eclipse framework (and therefore Rational Integration Tester) does not support user names that contain the “#” symbol. This issue could 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
|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. For information about the resolution, see http://support.microsoft.com/kb/156276/EN-US.|
|10766: Performance tests when running multiple test engines on one agent||Various issues with performance tests if running multiple test engines on one agent.|
|10158: 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 that is 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 selects 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.
|Simultaneous Modifications||If a message is opened in a message editor (for example, a Subscribe action), and in 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 overwrites the content of the window that is 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. To avoid this issue, select the user preference, “Run from Disk” as opposed to “Run from Memory”.
|User Permissions on Linux||The user of the Recording Studio perspective on the Linux platform requires administrative privileges. 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 Security||Only outbound actions are supported in the WS-Security node processor.|
|Results Rendering||The third party rendering engine has performance issues when processing large reports. To improve performance, increase 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 or messages.|
|SCM||If a newer version of Rational Integration Tester is installed after adding team providers to SCM, the providers must 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 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.
|Data Transfer Objects (DTOs)||DTO support is currently limited to the following:
188.8.131.52 is the second fix pack for the Rational Test Workbench, Rational Performance Tester Server, and Rational Test Virtualization Server offerings. The same fix pack updates components from the three offerings. You can update existing 8.0 or 184.108.40.206 installations to 220.127.116.11 by using the update feature in IBM Installation Manager. You can also install 18.104.22.168 directly by checking for updates before starting an 8.0 installation with Installation Manager. A small number of enhancements have been added to 22.214.171.124.
- The Stored Procedure action allows 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.
- You can sign SOAP message parts, optionally using the complete certificate chain.
- You can configure WS-Security on a Publish action so that WS-x elements (such as WS-Addressing, WS-Security and the body) can be individually signed (rather than having to sign the whole message). You can also sign using the certificate chain.
- You can add header values for FIX messages in the Value and Store tabs of a publisher, and in the Filter, Assert, and Store tabs of a subscriber. This enables sending and validation of the FIX header structure when using the FIX schema. For a publisher, any values specified here override values that are set by the FIX transport configuration (such as SenderCompID and TargetCompID). Note that the header fields that are displayed are the superset from the latest version of the FIX 4.x standard. If users create messages for earlier versions of the standard, the users 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
- A new field expander (schema) has been added to enable parsing of hexadecimal strings into Byte Arrays. For example, a hex string contained in an XML element can be converted into a Byte Array so that a further field expander, such as Copybook, can be applied.
|Download||RELEASE DATE||LANGUAGE||SIZE(Bytes)||Download Options
What is Fix Central (FC)?
|Rational Test Virtualization Server 126.96.36.199||4 Sep 2012||English||11||FC|
IBM Rational Software Support Communities
Helpful Hints For Obtaining Technical Assistance:
Before you contact IBM Rational Software Support, gather the background information that you need to describe the 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:
If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support.