Download
Abstract
IBM Rational Test Virtualization Server 8.0.1.1 has been made generally available and contains fixes to version 8.0.1 including all predecessor fix packs.
Download Description
| 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. |
| Impact | Description |
|---|---|
| This release is a maintenance release of Rational Test Virtualization Server 8.0.1. 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
The following defects were not resolved in this release.
Defect title | Description |
| Linux root/non-root Installation Notes | Linux root/non-root Installation Notes: The 8.0.1.1 components can be now 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: 31329 - All 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) 30778 - If RTCP 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 RTCP was installed as a non-root user. If RTCP 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 RTCP installation directory issue the commands: chmod a+w logs RTCP should now run as a non-root user. An alternative solution that may be preferred by some administrators, is to change the directory that RTCP writes information into. IBM will be providing a TechNote explaining how to modify an installed RTCP instance to do this. 31538 - Installation of RTCP as non-root requires a change to a suggested directory When RTCP is installed as non-root user then the majority of the directory names that will be created (and shown to the user during the installation) are pre-fixed with /home/<username>/. However, the installer defaults the Workspace Path directory specified on the Standard Configuration panel to /var/rtcp. As the user will not be able to create the directory the installation will fail. The workaround is to enter a different Workspace Path directory during the installation (e.g. /home/<username>/var/rtcp). |
| 32139 Use of –clean argument when Tester 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 Eclipce workspace cache then it will not correct itself. One common symptom of this problem is that when a user runs Tester, the splashscreen appears, then disappears but Tester never starts.
Although one workaround is to uninstall and re-install 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. i.e., from within the installed directory: GHTester.exe -clean Rational Integration Tester will take longer than usual to start when -clean is specified. The same problem can occur in RTVS and RPTS installations with the RIT Agent. In this case diagnosis and remediation is more difficult as there a multiple executable files and the correct one must be used. In these cases IBM’s Support team should be contacted. |
| 30017 - Upgrade Installations and Rollbacks (When Products Have Been Installed as Windows Services) Fail | On 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. For all version 8.x releases prior to 8.0.1.1, it was not possible to upgrade or rollback an installation of these products if they were installed as a service. The uninstallation process appeared to succeed but during the installation of the upgraded software (or the previous software in the case of a rollback) errors occurred, stating that files are in use or could not be removed.
This problem has been resolved in release 8.0.1.1 of the affected products. However, it has only been possible to fix this problem when upgrades are done from 8.0.1 (or later) to a subsequent release. Customers who are upgrading to 8.0.1.1 (or above) from a version earlier than 8.0.1 must continue to follow the workaround below. However, they will be able to automatically upgrade to subsequent versions. Note: This problem only occurs on the Windows platform and only for products which have been installed as services. Workaround for upgrades to 8.0.1.1 from versions earlier than 8.0.1 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. While it is in this state the upgraded service cannot be installed. The workaround to this problem is to first uninstall the existing version of the software and reboot the machine, and then install the new version. Do not use the upgrade or rollback capability. Note: 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 that you enter this directory as the workspace location, and that all settings and published stubs will be preserved. If you do not know where the workspace directory is, open the following file: <RTCP install location>\webapps\RTCP\WEB-INF\classes\container.server.properties And look for the line containing the workingDirectory key: workingDirectory=C\:\\RTW\\RTCP-Workspace If this advice is not followed and the installation does fail, first reboot the machine (to clear out the service). After the reboot, confirm that the service has been deleted 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 be inside its installation directory (which is not a recommended approach), be sure not to delete this directory or you will lose all Rational Test Control Panel configuration settings. |
| 28408 - Tester does not support WebSphere Application Server’s native JMS implementation if security has been enabled | Rational 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 so that this works, and expects to issue a Technote once the problem has been resolved. |
| 29950 - Slow Fail Execution Is Not Supported When Running ‘Now’ on a Remote Agent | Version 5.4 of Rational Integration 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 Rational Test Control Panel it is not supported if you run a test suite ‘now’ on a remote agent using the Run… dialog. |
| 27840 - 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 Windows shortcuts to these scripts are provided in the Start Menu.
Note; On Windows, if Rational Test Control Panel is running as a service, the shutdown batch script cannot be used to stop it. You must either use the control panel or issue a net stop IBMRTCP statement on the command line. |
| 29672 - Overwrite Expected Field for Filters | In the Message Difference Window, the 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. |
| 29494 - WaitForExit messages in Agent log | Changes 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 Probe | The sysstats probe is not provided for AIX. If a user attempts to configure an AIX-based performance test to use this probe, the following error displays 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 Error | On 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 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 requires 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 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, try to resolve it by adding the following line to the GHTester.ini file in the installation directory: -Dsun.java2d.d3d=false This tells the JVM not to use DirectX. This has resolved the problems in all the cases that 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 Cache | If you are using Rational Integration Tester’s .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 |
| .NET 4.5 is not supported | Rational Integration Tester’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 Strings | If a message element is a string that contains both left-to-right and right-to-left text in the same element then the string might not be displayed properly in the user interface. It will be published correctly. |
| 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 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’ dialog | When 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 Warning | If you are running Rational Integration Tester using an evaluation license, when you launch the “Tools Application”, by choosing the Source Control option in the menu or by creating/editing a data model, a dialog displays, 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 might 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, it will fail to start. For example: /opt/GH/RIT-Agent/Agent –consolelog If you are in 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. For example, a rename that changes “simpletest” to “SimpleTest” will not actually rename the test. This is because Rational Integration Tester uses the Eclipse framework to manage its files and Eclipse does not recognize this type of change. |
| 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. |
| 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 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, might return an error when trying to process a UNC path. For information about the resolution, see http://support.microsoft.com/kb/156276/EN-US. |
| 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 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 does not retain the selected id store and defaults back to the first id store in the drop down menu. Clicking OK on the window rewrites 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 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 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, you could 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 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 might 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. 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:
If you get a connection error when calling a private process, check the network settings. Open the Designer Engine Custom Properties in the Physical View of the Architecture School perspective to find the host and port number. The host and port numbers in the Physical View menu must match the host and port numbers in the GHEnable.proj design time library in the BW project. The BW host and port numbers can be set when the project is deployed. |
| Data Transfer Objects (DTOs) | DTO support is currently limited to the following:
|
Change History
- Functionality has been added to enable client-side virtualization of calls to the CICS Transaction Gateway. This enables a Rational Integration Tester virtual service to be executed instead of the actual program on CICS. Sift and Pass Through capabilities can be used to enable the stub to pass the message on to the real transaction if it decides not to process it. This feature is supported only for certain specific scenarios and has a number of limitations. Further guidance will be made available in a technote. Customers should be aware that:
- This functionality is supported only for off-mainframe Java clients of the CICS Transaction Gateway. The client must be using only the CICS Transaction Gateway Java libraries from the CICS Transaction Gateway SupportPac CA5F. No other configurations are supported.
- The feature supports only synchronous calls from the client to the CICS Transaction Gateway that must be using commareas. Only ECI calls are supported.
- Extended Logical Units of Work are not supported by the virtual services.
- If users require client-side recording of messages in Recording Studio (which is required if recording of messages to a stub is desired) then the ctgserver.jar file must also be in the client’s classpath and the application configuration updated. The ctgserver.jar file must be obtained from a version of the CICS TG that the CA5F SupportPac is compatible with.
- It is now possible to record Software AG webMethods IS messages without requiring a wmBroker instance. Although useful in environments where no wmBroker instance is present there is a greater impact on the message throughout of the wmIS server compared to the technique that does use wmBroker. For this reason the default recording options have not been changed and will continue to assume wmBroker is present. To enable recording without wmBroker, edit the GreenHat.properties file in the GreenHat package on the IS Server and change the useBroker setting to False.
- The HTTP transport has been changed to use per-remote-host connection pools rather than attempting to create unlimited number of connections. This significantly reduces the number of ephemeral ports created by Rational Integration Tester and also resolves some problems where these ports were not being correctly closed down. This change has also led to an agent being able to generate a higher tps load from a load generation test during a performance test (assuming all other factors are equal). The per-remote-host pool size is specified on the physical HTTP transport. This setting applies per unique host. For example, if two transports are defined, each with a pool of 100, then a maximum of 200 connections will be made.
- Rational Integration Tester has been updated with the SWIFT MT 2013 message formats. Because Rational Integration Tester supports only a single version of SWIFT, earlier versions of the standard are no longer explicitly supported. However, as Rational Integration Tester allows general SWIFT message construction, this means that 2012 (and earlier) messages can still be constructed, edited, published and received but all red-cross validation will be done according to the 2013 standards. Additionally, when using the right-click menu option within a message editor, the child-element choices shown to users will be based on the 2013 standard.
- License borrowing has been enabled for Rational Integration Tester on the Microsoft Windows platform. The feature enables customers who are using IBM Rational’s floating license server technology to check out a license onto their device (such as laptop) so that they can continue to work when disconnected from the network. The license can be given back to the floating license server at a later date. License borrowing is not supported on other platforms. For further details on how to use license borrowing please contact the IBM Rational licensing support team.
- To enable users to diagnose the cause of load failures quickly and effectively, Rational Integration Tester now reports the actual filename of any project files that it cannot load (for example, files might be corrupted). In most cases, a dialog box will be shown to users, although in a small number of cases user must still open the JVM console (by clicking Help > About on the menu bar of Rational Integration Tester) to see the filename.
- An option has been added to Recording Studio to enable messages to be displayed in ‘received’ time order rather than using the timestamp within the messages themselves. This is useful in situations where multiple servers are being recorded and those servers are not time-synchronized. Prior to this change, if servers were not synchronized then Recording Studio could show the reply message before the request which then caused problems when creating tests and stubs from the recording. To enable this feature, click the new Use Received Timestamp in Table button on the Recording Studio toolbar. The table is not immediately re-sorted, so if a user wishes to re-order already-recorded events, they must click the appropriate column heading. Messages will now be displayed in received order. To revert to using the message timestamps, click on the button again. The Recording Studio Save Wizard and the Playback options will both honor the selected mode.
- Rational Test Control Panel now supports use of the Apple Safari browser.
- A number of usability enhancements and fixes have been made to the Rational Test Control Panel user interface.
- MQEnvironment properties can now be set on a physical IBM Websphere MQ transport in Rational Integration Tester. For example, to set the Coded Character Set Identifier (CCSID) property use the value CCSID.
- The certificate that is used to sign the LibConfig.exe file (the Library Manager executable) on the Windows platform has been changed to an IBM certificate. When running under User Account Control (UAC), Windows will display the certificate details as part of the request for elevated (administrator) permissions. This now shows the software author as IBM rather than Green Hat.
- It is now possible to show the JVM console output window by pressing the Ctrl+Shift+J key combination within Rational Integration Tester. When opened using this method the window can be left open while Rational Integration Tester is used.
- It is now possible to use tags in the directory path specified for a file-based Results Publisher within the Project Settings dialog of Rational Integration Tester.
- Rational Test Control Panel now includes a number of example services that can be used for training, demonstration and educational purposes. These are as follows:
- Calculator - A simple calculator web service offering add, subtract, multiply, divide and modulus
- Echo - A simple echo web service that sends the supplied string back again
- Login - A simple login web service that returns a unique token from all login attempts, does not verify the user name or password supplied
- Phone Book - A simple REST based phone book service
- The Rational Test Control Panel REST API for controlling stubs now provides additional textual information in error cases.
- The Rational Test Control Panel Agents page now makes it clear whether a proxy has been configured for HTTP or HTTPS traffic (or both).
- Rational Integration Tester Agent, Rational Test Control Panel, and Rational Integration Tester Platform Pack can now be installed as 64-bit installations on the IBM AIX platform. Prior to this release only the 32-bit version could be installed on AIX 64-bit. Rational Integration Tester itself only exists as a 32-bit installation on AIX.
- TIBCO EMS 7.0 entries have been added to Library Manager. Additionally, three extra JAR file dependencies have been added to EMS 6 and 7 in Library Manager: tibcrypt.jar, slf4j-api-1.4.2.jar and slf4j-simple-1.4.2.jar. These files will exist in the specified directory in a normal EMS installation. In most cases, Rational Integration Tester will have found these JAR files by means of one of the other TIBCO product references because it is unusual for a user to only specify EMS. Previously, if only EMS was specified, problems would occur because of the missing references.
- It is now possible to install the HP QC integration such that only specific users have it within their QC environment, rather than requiring it to be rolled out to all HP QC users. This approach means that, although administrative access is still required for the initial client-side installation, users do not need to be Windows administrators to use the plug-in. A file must still be installed on the QC server but no downloads are made from the server to client machines. The new installation package can be found in \tools\HP\ QualityCenterServerDist11-client-only.zip under the Rational Integration Tester installation directory. Contact the IBM Support team for information about using this approach to install the plug-in.
- For consistency with standard industry practices, and to make it easier to set-up security, the Namelist automatically created by Rational Integration Tester on an IBM z/OS WebSphere MQ Queue Manager (to enable recording) now has an upper-case name.
- It is now possible to install the four Rational Integration Tester components (Rational Integration Tester, Rational Test Control Panel, Rational Integration Tester Agent and Rational Integration Tester Platform Pack) without requiring root access on Linux systems or administrator access on Windows systems:
- Installing some of the components as non-root (or installing as root and then running as non-root) might require ownership and permissions to be modified on Linux before the components will operate correctly. For more information, please refer to the Known Issues section of this document.
- If you attempt to install the components as a non-administrative user on Windows, various installation options (such as the ability to install components as Windows services and the installation of pcap) will not be enabled.
- Rational Integration Tester now supports versions 3.0.x of the SAP JCo library (used to connect to the SAP server) up to and including 3.0.9.
- The Agents view in Rational Test Control Panel will now show additional information about the capabilities of the specific agent or proxy when the magnifying glass icon is clicked. This is particularly useful for CICS Transaction Gateway proxies as it is possible to tell whether the proxy is capable of recording messages, routing messages or both.
- When recording or routing rules are created (by starting a stub or starting a recording, for example) additional information is now output to the Rational Test Control Panel Activity log, the stub console, and in Recording Studio, specifying how many proxies the information was passed on to. If the rules were not sent to any proxies, a reason why is specified. This makes it easier for users to troubleshoot the environment.
- The console output from a stub has been modified to make it clearer to users that a guard expression has been used as a filter when processing a message.
- The Rational Test Control Panel user interface now shows the name of the logged in user.
Approximately 63 message types have been modified (within the categories MT1nn to MT9nn) for this specification release. All of these have a number of modifications to the usage rules and field specifications and thus the semantic content of the messages. The semantic content of the messages does not affect Rational Integration Tester, but users need to be aware of this (details are found in the SWIFT standards specifications). Of these modifications, 29 message types have a message format specification that could affect 2012 messages. The impact is limited to red-cross validation and the child-nodes that are displayed to a user as options when constructing a message. These message types are as follows:
MT300, 304, 305
MT370 (new, added)
MT508
MT524, 527, 535, 538, 540, 541, 542, 543
MT544, 545, 546, 547, 558, 564, 566
MT568, 578, 586
MT604, 606, 607
MT920, 941, 942
A technote will be published providing further information on these changes.
Was this topic helpful?
Document Information
Modified date:
29 September 2018
UID
swg24034131