text:
Product documentation
This document contains a complete listing of releases, refreshes, fix packs and interim fixes sorted by version for IBM Rational Performance Test Server.
Tab navigation
- Release 8.6- selected tab,
- 8.5
- 8.0
- Support Resources
- Visit the IBM Support Portal to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.
- Visit developerWorks to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community.
- Visit the Jazz Community if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track development progress.
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:
- What software versions were you running when the problem occurred?
- Do you have logs, traces, or messages that are related to the problem?
- Can you reproduce the problem? If so, what steps do you take to reproduce it?
- Is there a workaround for the problem? If so, be prepared to describe the workaround.
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.
Follow IBM Rational Client Support on Twitter | Facebook | YouTube | devWorks Blog
Table of Contents:
|Date Released
13 June 2014
|A problem existed where the values added to tag inputs in the Data Drive tab of a test suite scenario could be lost when the scenario was saved. This problem has been fixed.
|In Rational Test Control Panel, when displaying agent deployed projects and stubs, the scroll bar for the lower part of the display did not allow the full set of agents to be scrolled into view. This problem has been fixed.
|The Message Editor was not correctly saving properties in message headers if the schema was not mapped. This problem has been fixed.
|When attempting to configure a Retrieve Task for a Software AG webMethods BPMS resource, it was possible that the user would experience a stack overflow error in Rational Integration Tester. This occurred if there was a circular reference in the definitions. This problem has been fixed.
|A problem has been resolved that meant Rational Integration Tester could not parse the extra encoding in an ISO8583 bitmap when NON-TCP transport was used (for example, using MQ transport and using zoned binary in bitmap).
This fix adds a new ISO8583-specific tag ibmrit:bitmapConvert="1" to the schema. Rational Integration Tester checks this tag and does bitmap conversion when applying the ISO8583 schema in field expansion or collapse.
Users should add this tag when using NON-TCP transports when they wish to use extra encoding in the bitmap, as in the following example:
The tag ibmrit:bitmapConvert="1" must not be added when using extra bitmap encoding in the TCP transport.
This fix also resolves the following issues:
1) Allow the application of the ISO 8583 schema to text messages in addition to binary messages.
2) Change the root of the 2 example schemas to be consistent with the schema names (ISO8583_1987_ASCII and ISO8583_1987_BINARY).
3) Add the new schema ISO8583_1987_ASCII_NONTCP for reference when the transport is not TCP.
4) Add support for the new 8583-specific tag ibmrit:bitmapLowercase="1" to the TCP transport.
|A problem existed where re-applying an XML schema or requirement to a message action would overwrite the previous settings for "Field is optional" and "Ignore rule cache". This problem has been fixed, with the following note: When a field is required by the schema and you mark the field as "Field is optional", the setting is overwritten, as it should be, when the schema is re-applied.
|A problem existed where adding a Process Tag action type to a Send Request message could result in a java.util.ConcurrentModificationException. This problem has been fixed.
|Elements in a message were falsely showing WSDL/schema validation failure (red crosses) when they contained a local element that referenced an abstract type that is already being processed. This problem has been fixed.
|Previously Rational Integration Tester might incorrectly format and match field values when handling a field with an XSD schema type of xsd:decimal. Values might contain exponents when output and values received that contained exponents might be incorrectly treated as valid. This issue has been resolved. Fields that are associated with a type of xsd:decimal will now output in the correct format. It should also be noted that when validating xsd:decimal type fields, values with exponents such as 1.0000001E7 will no longer be seen as valid. Previously they would have been, because the way Rational Integration Tester handled xsd:decimal was based around double types.
|A problem existed where running multiple JMS tests in parallel within a test suite could cause unused connections to be opened. The problem has been fixed.
|Previously, when running tests that contained Function actions that used Apache Ant or RunTests, the following message was displayed on the command line:
SEVERE: failed to locate properties file
This error message was only relevant if the rarely used Coherence functions were called, so the error message was removed to avoid misleading the majority of users. Customers that do use Coherence functions should be aware that they will not see an error message for a missing configuration file.
|Previously, if a user attempted to view test results in the Rational Test Control Panel Results Gallery view and the database from which results were being retrieved was MySQL then a ""connection abort: socket write error" message could be displayed and no results would be shown. This would occur if Rational Test Control Panel had not been used for a long period of time [hours] and was caused by problems within the database connection pooling. This problem has now been resolved.
|In previous versions of Rational Integration Tester, fields that were used to create HTTP proxy routing rules were not tag aware.
For example, an operation might be defined as: /RTCP/examples/calculator/calculatorService/%%URL%%
Then, when the stub was started, it correctly substituted the tag for the end of the URL and ran,but messages were not routed to it by the proxy. This was because the rule that was created included the %%URL%% string rather than the substituted tag value. This problem can be seen from the console output:
[Infrastructure] HTTP(S) Stubbing rule added. [((URL Prefix: /RTCP/examples/calculator/calculatorService/%%URL%% AND port=7821) AND.....
This problem was resolved and the tags are correctly evaluated in order to construct the routing rules.
|A problem has been resolved that caused the twisties (on Linux) or the "+"/"-" (on Windows) in the synchronization view of Architecture School to not work correctly.
|When importing a TIBCO BW project into Rational Integration Tester, errors were sometimes logged to the JVM Console (and the -consoleLog output) similar to the following message:
[13:12:28.092 2013/06/12] Jun 12, 2013 1:12:28 PM com.ghc.schema.SchemaStore getFile
When this happened, no context was provided to help the user locate the malformed URL.
These errors did not have any meaning and should not have been shown to users because they caused confusion. These messages are no longer displayed.
|In previous versions of Rational Integration Tester, if the "Preparing Test" dialog was displayed when running a test, then there were circumstances where the dialog window was not big enough to display all of the text. This problem has been resolved.
|Previously, it was not possible to select multiple test actions via multi-select when the action editor was set to display on the right or bottom. This problem would not be seen if the pop-up action editor was used.
To reproduce this problem:
The last action in the above task was not possible; setting the action editor to be a pop-up made it possible.
This problem has been resolved and multi-select of test actions is now possible when not using the pop-up action editor.
|If any of the following environment variables are set when Rational Integration Tester or Library Manager is run, then problems may occur:
When launching Rational Integration Tester, the splash screen appears but the project selector never displays. Library Manager simply does not appear. This causes a problem during installations where Library Manager must be run.
The Library Manager launch batch files used during installation have been changed to clear these environment variables before attempting to launch Library Manager. This prevents the installation from failing to complete. Additionally, a new script named GHTester.bat is now included in the installation, which clears these variables before launching Rational Integration Tester. LibConfigInstall.bat can be used to clear the variables before running Library Manager.
|All Rational Integration Tester Actions can be copied to the clipboard individually. However, in previous versions, when a group of actions was selected, if certain specific actions were included, then the Copy command was not available. For example, if any of the following actions were in the selection, Copy would be disabled:
-Default Case Action (of Message Case)
The problem has been resolved and groups of actions may now be copied correctly.
|The Validate Message from File action now behaves as originally intended. When using this action, the message you reference is used as the expected message when validating the received message. The enabled state of the validation actions is ignored and all fields are validated. The user can specify paths in the Exceptions text area that should not be validated.
These paths are the display paths as shown in the validation error messages that are displayed in the test console.
// can be used in a path to indicate any descendant. For example, /root//A matches /root/A, /root/X/A, /root/X/X/A and so on.
An asterisk can be used as the index to specify that any instance of a node should match. For example, /root/A[*] matches /root/A, /root/A[1], /root/A[2] and so on.
|Expanding and collapsing byte array data in a message received over IMS Connect using a non-default codepage could sometimes result in corruption because the codepage was not stored in the message. This problem has been fixed.
|Previously it was not possible for an IMS Connect client to connect to a server by using the Rational Integration Tester TCP proxy if the connection was secured with SSL. This was due to a mismatch in settings. This problem has been fixed and recording and virtualization of IMS Connect messages using SSL through the proxy is now possible.
|A defect that could cause a SD23 ABEND to occur when the "CANCEL" command was input against the MQ Exit RITRUN job on Z (Input "/C RITRUN" in SDSF) has been resolved.
|A defect in the Rational Integration Tester MQ exit for Z, which could cause a RITMQF S0C4 ABEND when using Sift and Pass Through, has been fixed.
|When importing a WSDL file into Rational Integration Tester on a platform that does not use the IBM Java Runtime (such as OS/X on the Mac), it was possible for the import to fail with the following error:
SEVERE error: Failed to install default SSLSocketFactory.
This error occurred because Rational Integration Tester assumed that the SSL_TLS context was available to make a secure connection. This context is only available in the IBM Java Runtime. This problem has been fixed and the code now falls back to a more generally available SSL context if the SSL_TLS context is not available.
|Due to an erroneous domain value, using the Run Later option in Rational Test Control Panel with a test suite that contained a stub could result in the stub failing to start. This problem has been fixed.
|The Rational Integration Tester JDBC driver has been enhanced so that it attempts to locate and load the vendor-specific driver directly when running in environments where java.sql.DriverManager is not able to find the correct driver. This enhancement allows the driver to be used with older versions of JBoss, among other environments.
|Rational Integration Tester now loads test data sets (CSV or Microsoft Excel format) completely into memory if the file size is <1% of available JVM memory at load time. This considerably improves the performance of Lookup Test Data actions.
|In Rational Integration Tester Recording Studio, test data can be saved to a CSV file whose name contains a number sign (#). Due to an error, the "#" symbol was being replaced with the string "[#]" in the UI, resulting in the Refresh process being unable to locate the file. The problem has been fixed and number signs are no longer being erroneously surrounded with brackets.
|If you used the Packet Capture mode to record an HTTP transport, and an application (such as the Firefox POSTER plugin) kept the sockets alive between calls, recording did not resume after a pause. The problem occurred because Rational Integration Tester did not register the connection as still open. This problem has been fixed.
|Previously, when importing a WADL file, Rational Integration Tester did not name the operations as a user might expect. Names such as ".opr" would be generated. This has been corrected and meaningful names from the WADL file are now used.
|The Recording Studio Wizard no longer creates rule cache rules by default; a user must request them to be created.
|Invocation of SAP Remote Function Calls (RFC) without table parameters is now supported. Previously such a call would fail.
|Rational Integration Tester was not correctly interpreting the IMS Connet protocol. Specifically, Rational Integration Tester views some fields as mandatory when it is legitimate for them not to be included. If Rational Integration Tester or the Rational Integration Tester TCP proxy received a message without these fields, then it would fail to parse them properly. Typically an end user would experience this by encountering dropped connections from the client application to a virtual service. This problem has been resolved.
|When Rational Integration Tester tried to import events from Rational Test Control Panel and an I/O error, such as a refused connection, occurred, the import wizard might hang and become unresponsive. This problem has been fixed.
|A problem existed in the Message Editor when completing a date field by selecting the "Use current date and time" check box. The value of the check box was not saved. This problem has been corrected.
|The Rational Integration Tester JDBC driver registration.xml file has been enhanced to include optional includes and excludes. By default, the JDBC driver will intercept all of the JDBC connections that the application makes. To explicitly enable or disable the driver for specific connections, you can use the new includes and excludes sections in the registration.xml file.
|Manually started stubs that performed multiple operations displayed differently in the Results Gallery than manually started stubs that performed only a single operation. The scenario and suite fields for single-operation stubs were correctly displayed as blank, while the same fields for multi-operation stubs contained meaningless values. A stub that is started manually should not have scenario and suite information attached. The problem has been fixed.
|Clicking the Details button for an error sometimes resulted in a truncated error message display. A horizontal scroll bar is now automatically created when the detailed message shows an exception stack.
|If a user added a new session state to a stub from the Stub Editor properties tab, then the description that they entered might not have been saved. This problem has been fixed.
|Previously the File Data Source dialog did not contain a vertical scroll bar, which meant that it was not always possible for a user to see all of the information. A scroll bar has now been added.
|Rational Test Control Panel Activity level messages now have a different icon than Trace level messages in the Diagnostic Log.
|Activity Log messages from SERVER source could appear in the Diagnostic Log as coming from an UNKNOWN source. The problem has been fixed.
|An example TCP port forwarding rule in the proxy registration.xml configuration file was accidentally uncommented in an earlier release, meaning that the proxy automatically created a rule forwarding messages from port 2000 to 3000 on the localhost. The line has been commented out again.
|If you deleted the first of two domains in Rational Test Control Panel, the second domain was displayed twice when the deletion completed. The problem has been fixed.
|Previously, if an HTTP/TCP proxy rule was set up that forwarded messages to a host with Unicode characters in its name, then the proxy failed to start. This problem has been resolved.
|The HTTP/TCP proxy was not processing Java KeyStore file locations properly. The proxy assumed that addresses were URLs rather than file paths and did not display helpful error messages if the file was not found. These problems have been fixed.
|Rational Integration Tester failed to record an MQ message that was added to a queue using the SET_ALL_CONTEXT option with a null putdatetime. Rational Integration Tester's Java log showed that a null pointer error had occurred in Recording Studio. Because this is a valid message, the problem has been fixed and such a message can now be recorded.
|In some circumstances, if a user deleted message properties on messages created from operations and message actions (for transports such as JMS/EMS) then the deleted properties reappeared when the actions were reopened. This problem has been fixed.
|In previous versions of Rational Integration Tester, attempts to create the results database on MySQL using the provided SQL script might have resulted in the following error:
ERROR 1071 (42000) at line 2003: Specified key was too long; max key length is 767 bytes
This problem has been resolved in the SQL script provided in version 8.6.0.
|Previoulsy, the WADL import wizard allowed only local files to be imported. You can now use a radio button to choose whether to import a local file or import from a URL.
|Previously, if a user configured a transport to use SSL by referencing an identity store that did not contain a valid key when first referenced, then the transport would not connect correctly until Rational Integration Tester was restarted, even if a valid key was added to the store. This was due to the transport continuing to use the version with the key. This problem has been resolved and users no longer need to restart Rational Integration Tester.
|It is possible to have both a Service Integration Bus (SIB) agent and a CICS Transaction Gateway (CTG) agent running in Websphere Application Server at the same time. Previously, both agents used the same registration.xml file, creating a potential conflict. It is now possible to point each agent to its own unique registration file.
Previously both agents looked for a Java property called com.ibm.rational.rit.registration to tell them the location of the registration.xml file. This meant it wasn't possible to have two files.
The SIB agent now looks for a property named com.ibm.rational.rit.registration.sib before looking for the previously named property.
The CTG agent now looks for a property named com.ibm.rational.rit.registration.cicstg before looking for the previously named property.
|The registration.xml file for the HTTP/TCP proxy did not list "http" as an option for port forwarding, even though it was a valid option. This problem has been fixed and the "http" port forwarding type is now listed.
|A problem has been resolved where the domain and environment names of JDBC proxies were not shown correctly in the Recording Studio tab of a Database Server Logical Resource in Rational Integration Tester.
|When a Rational Integration Tester stub failed to start due to an "Address already in use" error, the error was displayed in a green font in the Task Monitor, creating the false impression that no problem had occurred. This problem has been fixed.
|When a stub was created from a Publish operation using the Message Exchange Pattern, the Publish action in the activity actions for the stub was incorrectly created in the disabled state. This problem has been fixed.
|Rational Test Control Panel failed to restart if the current environment was locked. The environment lock check is no longer performed before the program is restarted.
|The Test Cycle Manager window was not displaying comments for newly added cycles until Rational Integration Tester was restarted or the user left or rejoined the cycle. This problem has been fixed.
|Previously the Schema Source field for a Schema Validation action stated that the source was a WSDL even when it was some other form of schema document. It now states "Document".
|When creating a Rational Integration Tester test suite, disabled rows in the Scenario Editor were still editable. This problem made it possible to click the Location & version field, which could cause an IndexOutOfBoundException. The problem has been resolved by making such rows non-editable.
|When running a test from the command line using the RunTests command, a spurious NumberFormatException error was sometimes displayed. This error was not displayed when running Rational Integration Tester through the user interface. The error did not affect the pass or fail status of the test. This was a spurious error, which has now been corrected and the command line no longer displays the NumberFormatException error.
|When using Rational Integration Tester to create an IMS Connect Operation from recorded events, the default schema root was incorrectly created as a ByteArray. The correct IMS Connect Data schema is now assigned to the IMS operation.
|In Rational Test Control Panel, two OSLC endpoints for ResourceShapes were not found. The correct representations are now returned. Although this was not evident to end users, it was an incomplete implementation.
|Previously, if uninstalling the JDBC provider from the different scopes in IBM WebSphere Application Server was unsuccessful, a Jython exception from uninstallJDBCProvider.py was thrown and the number of errors was not correctly shown. This problem has now been fixed and the number of errors is correctly shown.
|The "Paste" context menu option was disabled when attempting to paste XML content into a requirement message text node. This problem has been fixed.
|Previously in Rational Integration Tester, when a connection-based transport was disconnected while running a stub with a "one-to-one, looping" setting, the subscribe action reported it as an error. The subscribe action now reports this scenario as a cancelled instance.
|A new option has been added to the IBM MQ transport to allow fixed queue names when using the Sift and Pass Through stubbing mode. This is a new option that can be selected on the Stubbing tab on the Physical Resource and allows the queue suffix and open options to be configured. The fixed queues must have been previously created and configured in the MQ Queue Manager before they are used by the stubs,
This option must be used if multiple instances of the same stub are to be run on different agents to provide a greater throughput. If the default configuration of dynamic queues is used, then only one stub will ever receive the messages regardless of how many agents it is run on.
When you use multiple copies of a stub, all of the copies of the stub should be stopped together. If the copies are stopped one at a time while the producer is still putting messages onto the queue, the messages that are waiting to be processed are either deleted or passed through to the live system (depending on the transport setting) when the first copy of the stub is stopped. This can result in warnings in the other copies that are still trying to process the messages.
|If a project was set to "Run from memory" and a stub was open in the Test Factory perspective of Rational Integration Tester, then running the stub caused it to be incorrectly marked as changed (an asterisk next to the stub name in the tab). This problem no longer occurs.
|Rational Integration Tester message attributes were not namespace-aware, with the result that when a new, valid namespace prefix was used, the attributes failed to match the schema. The lack of a correct match with the schema can cause mismatched types, among other problems.
The message attributes now recognize alternate namespaces.
|In the Rational Integration Tester Project Settings window, Permissions Settings page, if you change the Authorization Realm to Rational Test Control Panel, you now see a message with Rational Test Control Panel security information.
|Previously, Rational Integration Tester was inconsistent in handling the Accounting Token field in MQ, treating it sometimes (correctly) as a byte array and sometimes as a string. As a result, tags could not be used in the field and values that were manually entered could be distorted. A second problem was found in the MQ exit that resulted in the field being accidentally cleared.
Both problems have been fixed.
|A new script, uninstallJDBCProvider.py, to remove the JDBC provider from the different scopes in IBM WebSphere Application Server, is now provided in the \jdbc\WebSphere directory of the Rational Integration Tester Platform Pack installation.
|In versions of Rational Integration Tester earlier than 8.6.0, when a UDP stub is started, the counter continuously increments for the entire time the stub is running. This eventually causes all of the threads to be exhausted. The problem is fixed in Rational Integration Tester 8.6.0 when using the new UDP transport. The old combined TCP/UDP transport still exhibits this behavior, and customers who are affected should migrate to using the new transport.
|The HTTPS proxy now supports the denotation of the SSL protocol to be used for the accepting socket and onward client socket. These are specified using the options serverProtocol and clientProtocol, both of which take a comma-separated list of protocols that may be supported by the JRE, with the first available one being used.
|The installers for Rational Integration Tester Agent and Proxies now check with Rational Test Control Panel to see if authentication is required. If it is, then a user name and password is requested.
|The new UDP transport in this release resolves an existing problem where Rational Integration Tester could sometimes not communicate with a UDP server on a remote host. The problem still exists with the old-style TCP/UDP connnection, which should not be used with a remote UDP server. The user should migrate existing TCP/UDP transports to the new UDP transport.
|In the Logical view of the Rational Integration Tester Architecture School perspective, you can paste a URL that points to a WSDL file in order to create a WSDL in the Schema Library. Pasting the URL launches a wizard. Previously a problem existed where canceling the wizard resulted in the WSDL still being created in the Schema Library. This problem has been fixed.
|When setting up a Results Publisher in the Rational Integration Tester Test Factory perspective, a Browse button is now provided to simplify entering the path in which the file should be created.
|When a multi-part MIME message was rebuilt for publication, any parameters beyond the first two (multipart/related and boundary) were lost. This problem has been fixed.
|The Rational Integration Tester Field Editor now displays labels for the main text box. This is so that training and user guides can easily refer to the correct part of the editor. The label that is displayed depends on the action type:
Equality action ("Value")
Table of Contents:
|Date Released
20 June 2014
|A defect has been resolved that meant that the ProcessTag action, Validate using Tag action, and Validate using Message from File action would only work correctly the first time in an iterator. This problem only occurred when there was no field expander or repeating field in the message.
|In previous versions of Rational Integration Tester, the SOAP envelope namespace prefix defaulted to "SOAP-ENV" for SOAP 1.1, and "env" for SOAP 1.2. Some customer systems require SOAP messages to use a particular envelope namespace prefix, commonly "soapenv". Rational Integration Tester now allows the prefix to be customized by operation and message. See the new "Envelope Namespace Prefix" field on the "SOAP" page of the SOAP properties dialog.
|Rational Integration Tester now honors the elementFormDefault="qualified" attribute in WSDL files correctly. This change means that Rational Integration Tester now correctly prefixes typed elements with the namespace prefix.
|Previously, when recording MQ messages from an operation, Rational Integration Tester waited until it saw a request message to set up recording on reply queues. The recording was set up on the reply queue seen in the request message, regardless of the reply queue specified in the operation. The advantage of this approach was that the correct reply queue would always be recorded, as it was taken from the request message. However, Rational Integration Tester requires a finite amount of time to set up recording on the reply queue, and if the system being recorded responded before setup was complete, then the first message could be lost, as it was placed in the reply queue before Rational Integration Tester started recording. This problem has been resolved, and Rational Integration Tester now automatically sets up recording on the reply queue defined in the operation as well as on the reply queue set in the request message (if different).
|A problem has been resolved that could cause a stack overflow exception to occur in Rational Integration Tester when working with myWebMethods task definitions. This problem was caused by processing of circular references in task definitions.
|Errors that occur when Rational Integration Tester generates a schema from a Protocol Buffers (.proto) file are now shown to the user. Previously they were hidden, which made problem solving difficult.
|Previously, JNDI property values that were specified in a JMS physical transport were converted to Strings before being passed to the provider. They are now passed through using the correct native type.
|A number of defect fixes have been made to Rational Integration Tester's Protocol Buffers import and schema generation process.
|Rational Integration Tester now logs exceptions that occur during webMethods Integration Server synchronization in order to make problem solving easier. Exceptions are logged on both the client and server side.
|A problem that could result in Rational Integration Tester showing a "ClassCastException" when a user attempted to modify a myWebMethods task action has been resolved.
|The Result Window, accessed by clicking a failed validation line in the test console window, could not be closed after the validation action type for an element in a response message had been changed. This problem has been resolved.
|A problem has been resolved where an "UnsupportedEncodingException" could occur when Rational Integration Tester attempted to decode a SOAP message.
|Previously, if the Rational Integration Tester HTTP proxy received a GET, HEAD, or CONNECT message with a BODY, then it would assume the BODY was empty. While it is not considered normal to send body contents with these messages, the standard does allow it. If the Content-Length or Transfer-Encoding headers were set, then the application downstream of the proxy could end up waiting for body content which never appeared. This could lead to long time outs.
This problem has been resolved and the proxy now correctly handles such messages.
|Date Released
27 February 2014
|Previously, when Rational Integration Tester automatically expanded bytes into strings during the processing of a received message, it would sometimes incorrectly select EBCDIC as the encoding/codepage for the message. This problem has been resolved.
|A problem has been resolved where, if HP Quality Center was used to run a test, and that test included any action that logged to the console in the Warning role, then an error would occur when the console output was transferred back to HP Quality Center.
|When running a test, if an assertion or filter fails due to a difference between the expected and actual messages, then Rational Integration Tester shows both the expected and actual values from the messages in the test console. For example, the console might show a message such as:
Assertion failed : Expected value "091231", found "013922"
If the two values from the messages are very large, such as MIME attachments, then Rational Integration Tester can freeze while it tries to render the complete value. Version 126.96.36.199 adds an option to limit the size of the expected and actual values that Rational Integration Tester attempts to render in the console.
To use this option, a user can add the following system property in Library Manager:
where maxLength is an integer that sets the maximum number of characters to be rendered in the console.
For example, using -Dcom.ibm.rational.rit.equality.message.trim=3 results in the previous example being rendered as:
Assertion failed : Expected value "091...", found "013..."
If the maxLength value supplied in the -D argument is a negative number or cannot be parsed as an integer, then it is ignored and complete values are rendered in the console output.
In addition, a problem has been resolved in Recording Studio that caused Rational Integration Tester to freeze when a user attempted to display a message containing large byte[] attachment. Although Recording Studio does limit the display of individual elements to 1024 characters, there was a window of opportunity before this rule was applied where Rational Integration Tester attempted to render the complete value, which could cause a problem in the case of very large values. The 1024 character rule is now applied immediately.
|A problem was introduced in Rational Integration Tester 188.8.131.52 that caused Rational Integration Tester to fail when performing a Test Data Lookup on either CSV and XLS files where the test data included cells whose value ended with the \ character. This was caused by a change to the escape-character handling in the library that Rational Integration Tester used for CSV parsing. This problem is resolved in Rational Integration Tester 184.108.40.206.
|A problem has been resolved with the MQ-Exit for the Z platform that meant that, if it was not correctly configured, then, after a period of time, the common storage area would become full which would cause ABENDs. This problem only occurs when using the sift-and-pass-through capability. It does not occur if the exit is used to only record messages.
|It is now possible to apply a DFDL schema to a text-based node in the Message Editor. Previously these schemas could only be applied to binary nodes.
|In previous versions of Rational Integration Tester, if a Copybook schema was applied to content that was longer than the Copybook schema, then the extraneous bytes would cause an error in processing. As Copybooks are often transmitted in fixed-length data areas, which need to be large enough for the largest possible variant of the message, this error could cause failures to occur due to spurious data being present in the byte array.
This functionality has been changed in version 220.127.116.11. When Rational Integration Tester expands content into a Copybook, if there is additional data present that does not map into the schema, then it will be presented to the user in an additional node at the end of the Copybook.
Differences in content of this additional node will not cause validation failures. However, in order to get the node into the expected message, a user must use the Overwrite Expected Message feature of Rational Integration Tester; it cannot be added manually.
|In previous versions of Rational Test Control Panel, if a user repeatedly attempted to log in using invalid credentials, then the audit log might record these "authentication failed" events as being logged by the "Remote Proxy" user. The events should be recorded as "no user," because no authentication took place. This problem has been resolved.
|The Windows build of the Library Manager executable (LibConfig) has been signed with a new certificate as the previous version was due to expire. This is required so that Windows will automatically prompt for escalated privileges via the User Access Control (UAC) mechanism.
|In previous versions of Rational Integration Tester, if a TIBCO-based project from an old version of GH Tester (5.2.11 or earlier) was loaded into Rational Integration Tester, then messages could appear to have no schema set on them and would be displayed with a red X. However, Rational Integration Tester would not allow the user to set a new schema due to the inconsistent state of the project. From version 126.96.36.199, should this situation occur, then a user can right-click the message and set a new root schema.
|In previous versions of Rational Integration Tester, the default schema root for an operation that was created from recorded IMS Connect events was set to the ByteArray type. This type was incorrect and led to further problem with incorrect data types being selected. This problem has been resolved and the correct schema root is now automatically selected.
|When returning a Proxy object from a Java Method transport stub, if the proxy was created without a state map being specified, a NullPointerException would be thrown. In this scenario Rational Integration Tester now creates an empty state map in the returned proxy object.
|When returning a Proxy object from a Java Method transport stub, if the proxy was created with an empty state map, the state would not be available for tagging in subsequent interactions, with the result that state could not be persisted. This problem has been fixed.
|When recording an operation that uses a Java Method transport the "Include invocation target 'this' in header" setting was ignored and the configuration from the Recording Studio tab of the logical transport was used. Rational Integration Tester now uses the operation setting to govern this behavior.
|A problem has been resolved that meant Unicode characters were not correctly displayed in emailed versions of Rational Integration Tester result reports where those emails were automatically generated by Rational Integration Tester Results Publishers.
|In previous versions of Rational Integration Tester, if changes were made to the field formatting options for the value of a date message field in a SOAP header, then those changes could cause the test and other tests using the same formatting to output the raw value rather than the formatted value. The problem stopped occurring if the project was closed and reopened.
This problem was caused by the SOAP Header being loaded into memory before the test was edited. The in-memory copy was used when the test was run and it did not have the changes incorporated in it. This problem has been resolved and the correct header, including the formatting, is now used at run time.
Note that use of the "Use Current Date and Time" option causes the actual value entered into the field to be ignored. This is because formatting takes precedence and if the formatting command generates a value, then it is used in preference to the entered value. However, the "type" validation is done on the entered vale before the formatting occurs. This might require a user to enter a "value" in order to pass type validation even though this value is not used at run time. For date/time-based validation, a simple workaround is to use the tag %%SYSTEM/CURRENT_DATE_TIME%%. This means that the type validation will pass and then the formatting will be applied.
|A problem has been resolved that could cause a java.lang.IndexOutOfBoundsException to occur in Rational Integration Tester when sending a reply in a stub that was using a data model.
|A fix has been made to the migration utility that is used to migrate GH Tester 4 project data to GH Tester 5 and Rational Integration Tester 8.0 or later. The fix resolves an issue that could cause a "com.ghc.ghTester.gui. SubscribeActionDefinition cannot be cast to com.ghc.ghTester.gui. ReceiveRequestActionDefinition" exception to occur during migration.
|A problem has been resolved where a stub using a Java Method transport could behave unpredictably when being used by multiple threads or JVMs.
|A problem has been resolved with the Java Method transport where attempts to construct java.util.Date instances failed and resulted in an error appearing in the console that included the text: "java.lang.ClassCastException: com.ghc.utils.GHDate incompatible with com.ibm.rational.rit.javabase.shared.model.MObject".
|Beginning with version 8.5.1 of Rational Integration Tester, a problem could occur if the path to the application that Rational Integration Tester was using to open CSV or XLS files contained spaces. In some of these cases, Rational Integration Tester failed to open the file and displayed an error similar to the following example:
com.ghc.applicationlauncher.ApplicationLauncherException: Cannot run program "C:\Program": CreateProcess error=2, The system cannot find the file specified.
This problem was caused by a change to the version of the Java Virtual Machine that ships with RIT 8.5.1. It has been resolved in version 184.108.40.206 of Rational Integration Tester and the files now open correctly.
|If the HTTP proxy received a request with its own URL as the endpoint, then it honored that request and entered into a loop that eventually caused the proxy to crash. Users typically saw this if they configured an HTTP transport such that the host/port on the physical transport on the settings tab was the host/port that the HTTP proxy was configured to listen on. Clicking Test Transport would cause the proxy to loop and fail.
With Rational Integration Tester 126.96.36.199, the proxy reports the problem and does not forward the message, preventing the loop from occurring.
|A problem has been resolved that could cause MQ-based stubs that were configured to use sift-and-pass through to slow down under high load. This was caused by a race condition in the management of the MQ connection pool between the sift and pass through logic and the stub itself that could result in a delay before a worker thread began processing the next message.
|A problem has been resolved that could cause an IMS Connect transport based stub to raise a "java.lang.NegativeArraySizeException" error during the Send Output processing.
|Rational Integration Tester 8.5.1 introduced a QuickLink tool as part of the HP Quality Center Integration. As part of the Rational Integration Tester installation, a link to this tool was placed in an "IBM" start menu folder. The link should have been placed in the "IBM Rational Integration Tester" start menu folder. This has been corrected.
|A problem has been resolved that meant references to TIBCO BusinessWorks design time libraries could be incorrectly duplicated when opening the resource editor.
|A comment has been added to the Agent.config file make it clearer how to configure it for Rational Quality Manager integration. Specifically it now suggests use of the /qm suffix on the URL.
<!-- RQM endpoint is usually '/qm' but check with your RQM Server Administrator -->
|In previous versions of Rational Integration Tester, some drop-down selection boxes rendered with the incorrect background on Linux. This could cause users to think the drop-down was disabled when in fact it was enabled. An example is the Schema root selection drop-down in the Schema Library. This problem has been fixed and the drop-down boxes now render with the correct background color.
|In previous versions of Rational Integration Tester, if a user saved the project without anything being selected in the Logical View pane, then, on reload of the project, Rational Integration Tester could appear to choose an arbitrary zoom/location for Logical View. This could result in the user seeing what appeared to be a blank page in Logical View because the objects were not on screen. The only workaround available was to ensure that an item was selected before saving the project, so that Rational Integration Tester would ensure that the selected object was displayed on reload.
From version 126.96.36.199 of Rational Integration Tester if, on project load, there is no selected object in logical view then the view is set-up such that the center of the leftmost object on the canvas is in the display area. This avoids the situation whereby a user sees a completely empty canvas on reload and wonders where their objects have gone. The alternative, of selecting an object before save, still works.
|In previous versions of Rational Integration Tester, if a test action that had a failure path was moved (for example, dragged onto the test action tree), then the failure path steps disappeared. Closing and reopening the test caused them to reappear in the correct place. This problem has been resolved and failure path steps are now correctly redrawn when a test action is moved.
|FIX messages are now correctly timestamped with the time they are received by Rational Integration Tester. Previously they were timestamped when Rational Integration Tester processed them, which could be a small amount of time subsequent to receipt.
|In previous versions of Rational Integration Tester, the "Slow Fail" option in the Run dialog for the Test Suite was incorrectly enabled when a remote agent was selected. This option is not supported when suites are run remotely. The problem has been resolved and the option now stays disabled.
|Date Released
19 December 2013
|A problem which meant that editing test data filters in performance tests didn't result in the editor being marked as dirty has been fixed.
|The default database schema for Log Measurement defines 8 counters and 5 attributes. It is possible to modify the tables to include additional columns in order to cater for more counters and attributes, but there was a problem which meant that any data recorded in these columns would not be displayed in charts. This has been fixed.
|If a project uses DFDL schemas and references those schemas using project-relative paths then, if a performance test is run that requires those schemas then the test will fail with an error similar to: INFO: TestEngine (2): [Error] Child: Publish:"Text" to file "%%PROJECT/ROOT_DIRECTORY%%/myFile.txt" using schema "Text" via "File" "/text" - Failed to collapse expanded field, com.ghc.a3.a3utils.nodeformatters.api.FormatterException: [CRRIT4238E] Failed to collapse: due to java.lang.Exception: null: C:\Users\IBM_ADMIN\AppData\Local\Temp\ghs_repo_4476_7354545369012800524\DFDL4RIT\Sample01.xsd (The system cannot find the path specified.) The error does not occur if the schema location is specified using an absolute path (and that path is available to the agent). This problem has been resolved in version 220.127.116.11 of Rational Integration Tester.
|In version 8.5.1 of Rational Integration Tester the "--username" command line option for GHTesterCmd commands: start-stub, stop-stub, lock-environment, unlock-environment, start-scenario and stop-scenario was incorrectly re-named to "--user". This has now be changed back to "--username" to remain consistent with the command options in 8.5.0
|The use of -t as a shortcode for the -stop-stub option to GHTesterCmd has been removed as it was already in use by another command.
|A problem has been resolved that meant poor performance could be seen from stubs that were making extensive use of CSV or XLS test data sets. This was caused by an incorrect caching algorithm leading to cache rebuilds occurring too often.
|The 'Stop Service' button on the supplied AddNumbers server (as part of the Rational Integration Tester install) now correctly stops the service.
|In previous versions of Rational Integration Tester, fields within DFDL schemas that used XML Schema derived simple types were treated as String fields. This has been improved to map the derived simple types to more suitable types (such as Bytes, or Long) when there is a more suitable match. Existing tests that validate these fields will fail and will need to be updated to expect the new data types (by, for example, using the Overwrite Expected Field or Message functionality), although the values of the fields should be unaffected.
|A problem has been resolved which caused failures when saving and loading Copybook messages containing PIC S9(2) computational fields.
|A problem that caused Rational Integration Tester to fail to send some DFDL-defined messages has been fixed. The failure occurred when the message to be sent included a length count that was used to define the size of another field later in the message. Note that this problem was introduced in version 8.5.1 and was fixed in 126.96.36.199.
|When a SOAP message cannot be compiled due to a change in the schema the error message displayed to the user is now more meaningful.
|A problem has been resolved that meant SOAP message headers generated by Rational Integration Tester were incorrect for WSDLs that contained xsd elements referenced by both message header and message body definitions.
|A problem has been resolved that meant if a WSDL file without any WS-Security information was synchronised into Rational Integration Tester version 8.5.1 and a test created from the WSDL via MEP then the Enable Security checkbox would be incorrectly ticked.
|When synchronising WSDL files from an SSL/TSL secured source Rational Integration Tester will now blind-trust the certificate presented by the server to secure the connection. This avoids synchronisation failures when RIT has not been configured with the details required to trust the connection.
|Previously, a problem existed that meant Rational Integration Tester would display red crosses on xml namespace declarations (i.e. xmlns attributes) for those declarations that were declaring namespaces used only at a deeper level of the xml document. This has been resolved and it is now possible for xml declarations for all known namespaces to exist anywhere in the xml document without RIT displaying red-cross validation issues.
|The GHRunAgent.exe executable used as part of the HP Quality Center integration is now recognised as a 32 bit application on Windows XP. This fix was delivered in version 8.5.1 of Rational Integration Tester but was not documented in the release note.
|A problem has been resolved that meant if a Rational Integration Tester Agent version 8.5.1 was configured to operate only in RQM mode (only connects to RQM and not to RTCP server) then it would report a NullPointerException on startup and will not connect to RQM.
|On opening a project Rational Integration Tester starts an an internal HTTP server that is used for various component communication reasons. Previously, if the server could not be started the project would not open. This was most often because RIT could not bind to the specified or default IP address and port. This behaviour has changed and the project now opens regardless and a warning is displayed in the Global Notifications explaining how to fix the problem. The most notable functionality that requires the HTTP server is Performance Tests and Probes. Additionally, if an Agent is configured with an invalid bind address or port it will not be able to execute tests on behalf of a performance test; if an attempt is made to do so an error is logged.
|Libraries referenced in Library Manager will now be resolved at test execution time even when their path contains a comma.
|The Activity and Diagnostic log views in Rational Test Control Panel now remember the "Auto Update" setting value between page clicks.
|The length-limit of the description that can be added to recorded events exported to Rational Test Control Panel is now consistent between Rational Integration Tester and RTCP.
|On non-Windows systems if Rational Test Control Panel is running when an upgrade is performed (and it was run from the command line) then the upgrade process will now stop RTCP automatically. Previously RTCP would not be stopped and the upgrade would fail.
|In 8.5.1 old versions of Firefox (prior to Version 4) were not be able to view the Rational Test Control Panel web pages. This is most likely to be observed when using an operating system where the more recent versions of Firefox are not available (e.g. Solaris). This problem has been resolved and older versions of Firefox are now supported.
|Searching for recordings in the Rational Test Control Panel library page now behaves more consistently when a search string is entered but no other search criteria are specified.
|The Logout and About menu options in Rational Integration Tester have been changed to be buttons rather than links for consistency.
|A change has been made so it is now possible for a user to right-click on the Edit Domains button on the VIE Domain selection page and open it in a new browser tab/window.
|The Domain column in the table shown in the Agents view within Rational Test Control Panel has been removed. This is because the user has already selected a domain so the table would only ever show a single domain in the table.
|The email plug-in will now pass username/password details to the email server if they are provided.
|The FIX transport now contains settings that allow the user to express the timeout period for a message to be sent. This prevents Tester from hanging forever when the server does not respond. The default timeout is 15 seconds.
|The technical description for REST-based publish actions now correctly shows that it is a parametrized URL. For example, a SendRequest to /RTCP/examples/phonebook/1 is now correctly described as /RTCP/examples/phonebook/1]{id}.
|Previously, when a stub based on the MQ transport that was configured to use sift-and-pass-through was stopped then an error similar to the following was occasionally reported in the Rational Integration Tester console: Message Switch:on queue "RIT_TARGET" via "QL01 - S&PT" Null Pointer Exception: null This problem has been resolved.
|IMS Connect content recognition had been disabled in version 8.5.1 of Rational Integration Tester due to a problem that caused most byte[] content to be incorrectly recognised as IMS Connect messages. This problem has been resolved and version 220.127.116.11 should correctly identify IMS Connect messages.
|Tests that use the IMS Connect transport with expanded bytes where no encoding has been configured will now use the codepage specified as part of the messaging action rather than the project wide default for the bytes content handler.
|A problem has been resolved which meant that if an IMS Connect-based operation had spaces at the end of its name (which could occur when creating an operation/stub from recorded IMS Connect messages) then it would not be recorded correctly.
|A problem has been resolved that meant, when recording IMS Connect traffic, if the client specified a Client ID then the reply might not be shown in Recording Studio.
|Performance tests that use an SSL-secured TCP transport will now work correctly. Previously, if such a performance test was run then error messages similar to the below would be reported by the agents: INFO: TestEngine (2): java.lang.IllegalArgumentException: [CRRIT0000E] id can not be null INFO: TestEngine (2): at com.ghc.ghTester.performance.SlaveProject.resolve(SlaveProject.java:119) INFO: TestEngine (2): at com.ghc.ghTester.applicationmodel.impl.ProjectAdaptor$7.run(ProjectAdaptor.java:1127)
|The packetiser settings used on TCP messages allows the use to specify the length of the message as characters or bytes. A problem has been resolved that meant if the length was expressed in bytes then Rational Integration Tester could incorrectly limit the quantity of data to be sent.
|Support for TIBCO Rendezvous has been improved to enable use of arrays and unsigned integer types.
|The Help/About box in the Tools app (used for SCM integration, Data Model editing and DFDL configuration) now contains product/version information. Previously it was empty.
|A problem has been resolved that meant if Rational Integration Tester was synchronized against a WSDL file containing elements marked as then a stack overflow error would occur.
|In previous versions of Rational Integration Tester if a user clicked the Clear button in the Operation Assignment page in the Save Recorded Events wizard then the Operation field would be cleared but an error message would be incorrectly displayed as well. This problem has been resolved and the error message no longer appears.
|When the Recording Studio wizard is used to create a test data set (or a data driven test/stub) a problem could occur that meant the generated data was not consistent in its use of NULL and blanks in the data. The intent is that a user should be able to create a stub from recorded data (containing both NULLs and blanks) and have the stub respond in the same manner as the recorded messages. This problem has been resolved in the case where Rational Integration Tester's "Send NULL values" preference is unchecked, which is the default. (Preferences -> XML panel). If this preference is checked at the time the stub is generated, it can be "fixed" later by editing the field expander properties and un-checking it.
|A problem has been resolved that meant the Test button in the SQL Query action would not operate correctly if the query had been modified to use a list tag instead of a single-value tag.
|A problem has been resolved that meant Rational Integration Tester would display a red cross on the root of an xml message with an error saying that the root did not exist in the schema. This was caused by a different namespace prefix being used to the one that Tester used even though both prefixes resolved to the same namespace URI. The root of the xml instance document is now recognised as equivalent to the root defined by the schema.
|In previous versions of Rational Integration Tester when a DateTime is read from an Excel spreadsheet Test Data Set it was assumed that the date is in GMT and then converted to 'local' time. If the user is not in a GMT timezone then the DateTime that is seen in RIT will not be the same as shown in the spreadsheet. In the UK this will also result in different behavior if the test is run during British Summer Time. Typically the user will experience this problem by the message created by RIT having a date/time that is some hours different to the date/time in the spreadsheet where the difference is equivalent to the user's local time from GMT. Rational Integration Tester v220.127.116.11 has been changed to interpret dates read from Excel spreadsheet test data sets as 'local' time. This means that if a message is constructed using the value from Excel then it will appear as per the spreadsheet. This is a change in behavior which could break existing tests. However, the current behavior is wrong and, for those countries that have daylight saving time, leads to differences in behavior of a test depending on when it is run. It is therefore thought unlikely that any users would want the current behavior as it stands. Note that this only affects data where the underlying Excel cell is a DateTime, not where it is a string. If a user needs to revert to the old functionality then this can be done via a new JVM argument which forces Tester to use a particular timezone when interpreting DateTimes from Excel. This must be specified in Library Manager for Rational Integration Tester and the Agent if that is being used. For example, to specify GMT (reverting to the previous behavior): -Dcom.ibm.rational.rit.excel.timezone=GMT Other timezones can be used by specifying the timezone code as shown in the TZ column here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
|Previously, the Compare File action would fail if one of the files was semi-colon (;) delimited. This problem has been resolved.
|A problem has been resolved that meant if a user added a failure path to a Message Switch >Message Case then it could not be saved with any actions below it. From version 126.96.36.199 all new failure path actions created will operate correctly. However, projects containing existing failure paths are corrupt. In order to be able to save a failure path with sub-actions the tests will need to be opened, existing failure paths (under message cases) deleted and then saved and reopened before a new working failure path can be added otherwise the new failure path or the actions added will not be saved correctly.
|A problem which meant that the Formatting settings of a Field Editor were not displayed correctly after the editor was saved and re-opened has been fixed.
|Various problems with http-reply based requirements created from Recording Studio or Create Requirement from MEP have been resolved. These include empty version fields (should be 1.1/1.0) and StatusCode, ReasonCode and rcvdTimestamp fields having child elements.
|Previously, if a Data Model's data was edited and saved using LibreOffice then Rational Integration Tester would no longer be able to read the data model correctly. This was caused because LibreOffice defaults to using tab-separators rather than the comma-separators RIT was expecting. A change has been made to RIT so that if it cannot read the file using comma-separators it will attempt to use tab-separators. This resolves the problem.
|A problem has been resolved that meant it was not possible to create stubs using the Timer behaviour in Rational Integration Tester 8.5.1.
|In previous version of Rational Integration Tester the link between tags and fields in Test Data Iterator actions was by column number even though a name would be displayed in the RIT user interface (assuming there were column header names). This meant that if an iterator was set-up and used and a new column was added in-between two existing columns the iterator mappings would then be incorrect. This has been resolved in version 126.96.36.199 and RIT will now attempt to map by column name first (assuming headers are available). If it cannot find the name then it will revert to using column number.
|A problem has been resolved that could cause Test Data Lookup actions to fail if two tests were simultaneously iterating through tests data sets.
|Two problems related to file encoding and CSV tests data sets have been resolved. Firstly, the character encoding is now set correctly on the created CSV file. Previously, if Rational Integration Tester put non-ASCII characters into the test data set then the file encoding was not set correctly and other applications would fail to show the correct text. Additionally, a problem has been resolved that meant cached CSV test data sets that used encoding types other than UTF-8 would not be parsed correctly by Rational Integration Tester.
|A problem has been resolved that could cause corruption in test data due to Rational Integration Tester inconsistently escaping the quote character in CSV files. For example, if a received message contained 123"456 then, when test data was created (from Recording Studio, for example) then RIT would correctly escape the quote resulting in the CSV file containing 123""456. However, the data was not being un-escaped when the test data was read meaning that parameterised tests and stubs would send/receive incorrect data.
|A problem has been resolved that meant the Test Data Lookup action could fail to find a value that was in the data set if multiple stubs were accessing the same data set concurrently.
|The Expand All button in the Message Difference Window is now sensitive to the currently selected node.
|It is now possible to repeatedly click on the Delete Selected button on the Rational Integration Tester Task Monitor. Previously the mouse had to be moved off it and back on in order to click it again.
|A problem has been resolved that meant Rational Integration Tester was failing to treat two string fields containing xml QNames as equivalent if they used different namespace prefixes even though the prefixes resolved to the same namespace URI. Tester now supports QName values through the use of a new QName field type which will validate QName equivalence correctly.
|A problem has been resolved that could result in a test suite that contains tests with Run Command actions appearing to hang. Specifically, the issue occurred most often if one of the tests runs an external command that took a long time to complete.
|Previously, when using the Message Difference Window to compare a received message against the case actions with a switch (e.g. a stub with multiple events for the same operation) viewing cases after looking at the default case could give inconsistent results. This has been fixed.
|Incorrect configuration of LTPA providers and identifies now returns better error information to the user allowing them to work out what the problem is. The LTPA provider configuration now also contains a test button.
|In previous versions of the Rational Integration Tester CICS agent, enabling the agent had a noticable impact on the elapsed time and CPU time of DPL invocations where the program(s) linked to were not being recorded or stubbed. The impact has been significantly reduced in version 220.127.116.11.
|A problem has been resolved that meant, in some circumstances, stubs could not be run when non-ascii characters were used as part of the components / operations / stub names.
|A problem has been fixed that meant for every CICS DPL invocation that was made with the Rational Integration Tester CICS Agent enabled, the message "INFO: RITMain has been invoked" was logged to the STDERR log file for the JVMServer. The message is no longer output on each invocation.
|A problem that meant a stored procedure call learnt from recording JDBC calls to Microsoft SQL Server would fail when using the internal database for virtualization has been resolved. This was caused by a problem in using the correct 'case' for the stored procedure name when it was quoted.
|A problem has been resolved that mean when editing the contents of a learnt database table (using JDBC Virtualisation) if the query that was used to 'learn' the table was edited immediately before the editor (e.g. Excel) was opened then the edited query would not be used.
|When using the integrated database for JDBC database virtualization with WebSphere Application Server applications may fail to get database connections in WAS with the following text being reported in the in the WAS SystemOut.log: "Missing property 'simulationConnectionURL' for data source. Define the value using a 'simulationConnectionURL' custom property on the data source" There are two options to work around the issue: a) Use the WAS admin console to define a custom property called simulationConnectionURL on the data source. The value of the property is not important. Note that each time Tester is used to disable and re-enable the data source for virtualization the workaround must be repeated. b) Within Tester, go to the physical database resource, Stub Settings tab. Uncheck the 'use integrated database' check box, and fill in a dummy value for the database URL. Then re-select 'use integrated database' and click OK to close the resource. Then open the WAS physical resource, choose the Data Sources tab, and disable the GH JDBC Driver for each of the data sources. Re-enable the GH JDBC driver to push the new configuration onto WebSphere.
|The setupJDBCProvider.py script provided to install and configure the Rational Integration Tester JDBC driver with WebSphere Application Server (WAS) now correctly uses the Java 5 based com.greenhat.jdbcdriver.jar driver when used against WAS 6.1.
|A problem has been resolved that meant JDBC recording and virtualization could not be used against WebSphere Application Server if WAS contained two data sources defined at the same scope, and with the same JNDI name.
|Additional information has been included in the Rational Test Control Panel diagnostics log for the JDBC proxy in order to make problem-solving easier.
|Rational Integration's Tester Java Virtualization solution now offers better compatibility with JBoss. When used with JBoss the following start-up parameter must be used for the JBoss server: -Djboss.modules.system.pkgs=com.ibm.rational.rit.javabase.linkage RIT's Java Virtualization solution will not operate if JBoss is configured to use the IBM Java Runtime.
|A problem has been resolved that meant processes executed using sudo were not being terminated by Rational Integration Tester.
|Date Released
19 November 2013
|Rational Performance Tester Agent
|RPT playback hangs on 16th attempt to access page requiring digital certificate
|Rational Integration Tester
|A problem has been resolved that could cause performance test to fail if the load-generation test was data-driven using a data source within the project folder structure.
|Previously, when using the StartStub Ant task, if there were multiple versions of a stub then the earliest (oldest) version would be started. From version 8.5.1 if no version is specified then the most recent version will be used instead. The StopStub Ant task has also been updated so that all versions of a stub running will be stopped if no version is specified, rather than just the earliest.
|Ant scripts generated from Rational Integration Tester have a hard coded version specific reference to the ghTester.ant jar file. In release 8.5.1 this has been changed to look for any ghTester.ant jar file. If Rational Integration Tester and Agent are installed on the same machine, at different version levels, it may be necessary to edit the generated ant script to hard code a specific version.
|In Detailed Reports, action names that contained tags would sometimes show a future value of the tag rather than its current value. This has been corrected.
|A problem has been resolved that meant, in some circumstances, having stub performance optimizations enabled (set on the properties tab of a stub) could cause the storing of values into tags from fields in the received message to fail. Tags are now populated correctly. Users should note that these stub optimisations are not suitable for use with data-driven repeating elements.
|In previous versions of Rational Integration Tester Sift and Pass Through stubs using the Publish and Subscribe Message Exchange pattern would send a publish message but also pass through the message. This issue has now been fixed.
|Previously, when starting a stub with multiple operations where an existing single operation stub is already running then the single operation stub would have been incorrectly stopped. This problem has now been resolved.
|A number of improvements have been made to the performance (response time) of parameterized (data driven) stubs. These improvements are particularly significant around the use of repeating elements. Note that in order to get the best performance from stubs the log level should be set to 'None', either in Tester or on the Rational Test Control Panel stub starter.
|If a machine (typically a virtual machine) is very slow or overloaded, the agents may not start up quickly enough to register for correctly for the performance test. In this case, the performance test will fail due to a time out error. The error in the console will state that the "TestEngine did not start." In order to fix this problem, users should add a -D startup option to Rational Integration Tester using the Library Manager (on the Application page in the JVM arguments text). Tthe parameter: -Dgreenhat.ptc.te.start.timeout=300 should be specified where 300 is the number of seconds before RIT will time-out. This value can be increased to allow the agents more time to start-up. Note that this setting is made in RIT (the Performance Test Controller), not on the Agents.
|A problem that meant the Environment drop-down in the Scenario Editor displayed environment names containing dots incorrectly has been fixed. For example, "My Environment 2.5" would be displayed as "My Environment 2". This problem was also present in the "Run..." dialog.
|When a certification suite is published to Software AG's CentraSite product the Test-Results field now contains a URL link to the RTCP results gallery page for the suite (assuming the project has an RTCP URL defined for it).
|In previous versions of the Rational Test Control Panel temporary files created by the application during normal use were not removed if the product was uninstalled. This problem has now been resolved.
|In previous versions of Rational Test Control Panel console log line output from stubs would appear in the wrong order in the Results Gallery view if the Results Database was hosted on Oracle. This issue has now been fixed
|A problem that meant the drop-down menu for rows in the Rational Test Control Panel VIE dashboard would extend of the bottom of the screen, obscuring some options, has been fixed.
|In previous versions of Rational Test Control Panel the test suite report in the Results view could sometimes appear in a frame that was too small. This issue has been fixed.
|A problem has been resolved in Rational Test Control Panel that could cause the error "org.apache.openjpa.persistence.InvalidStateException: This operation cannot be performed while a Transaction is active." to be shown within the user's browser. This was caused by a race condition if two audit log entries were made at exactly the same time.
|In previous versions of Rational Test Control Panel the Help URL could end up set incorrectly if a "localhost" URL was used as the first URL to access the server after it had been started. This issue has now been fixed.
|Rational Test Control Panel now runs on (and ships with) WAS Liberty rather than TomCat. This means that the location where database driver files must be copied for use by RTCP has changed. Typically this drivers must be added if RTCP is going to be used to show information from the Results Database. The location where the drivers must be copied to is now: \usr\servers\RTCPServer\apps\RTCP.war\WEB-INF\lib
|A problem has been fixed that meant, on occasion, JDBC database stubs did not appear in the Results view of Rational Test Control Panel.
|A problem has been resolved that meant, in some cases, trying to start a stub from the RTCP dashboard after an agent has disconnected resulted in the stub failing to start.
|A problem which meant that a failed security handshake when connecting to an HTTP stub that uses SSL resulted in the stub's count of handled requests to increment has been fixed.
|A change has been made to the URL shown in the header of a message based on a REST URL schema to make it clearer to users that the URL will be populated at runtime. Previously, the URL in the header would be shown as a hard-coded value (based on the messages from which it was created) with the URL in the body being parameterized. This could be confusing to users as it was not clear that the parameterized URL would be used at runtime. The URL in the header is now shown using a generalized form with {} replacing parts that vary; for example: /RTCP/examples/phonebook/{id} in place of /RTCP/examples/phonebook/1.
|A problem that meant that the content-type header was being corrupted by Tester when creating MIME-based messages (e.g. from Recording Studio or from a Requirement) has been resolved.
|In previous versions of Rational Integration Tester the Message Editor would show red-crosses against messages after the initial application of Multipart MIME schemas. This problem has been resolved and the message will now validate correctly.
|In previous versions of Rational Integration Tester the 32-bit version of WebSphere MQ API exits were not provided for the Solaris operating systems. This meant that locally bound 32-bit applications could not connect to the Queue Manager once the RIT 64-bit exits were installed. 32-bit exists are now available for Solaris SPARC and x86.
|In previous versions of Rational Integration Tester, when using Sift and Pass Through with WebSphere MQ, it was possible in some circumstances for the message ID in the messages being received by the Queue Manager to be overwritten. This would then result in the reply message not having the correct expected response IDs. This issue has been resolved.
|Significant changes have been made to Tester's support for UDP in version 8.5.1. It is now possible to run tests when RIT is installed on the same machine as the UDP server and support for multicast (tests and stubs) has been added. Users should be aware that there is a known problem with stubs that subscribe to UDP transports. Specifically the 'hit count', showing how many messages the stub has received will continually tick up even if the stub is not receiving any messages. This does not affect the functionality of the stub.
|In previous versions of Rational Integration Tester, the General menu in the logical view of architecture school allowed the creation of a number of schema types which have no logical component. These have now been removed from the menu. Users should create schemas from within the Schema Library view.
|A problem that meant the scrollbar on the Filters dialog in Logical View could disappear when the dialog was resized making it impossible for the user to scroll through the selections has been resolved.
|Previously it was not possible to create a new resource in Logical View that contained a '.' character. However, it was possible to subsequently edit the name to include the '.'. This has been changed for consistency and it is now possible to use a '.' character when creating the resource.
|A problem has been resolved that meant that WSDL files created by certain applications (such as TIBCO Designer) were not being imported into Rational Integration Tester correctly. This occured where multiple WSDL element references in the schema definition only differed by their namespace. In this scenario these element references were not being treated as unique by RIT and could be overwritten. These WSDL files now import correctly.
|The DFDL parser that is bundled with Rational Integration Tester has been upgraded to version 18.104.22.168. Amongst other fixes this means that Rational Integration Tester can now import DFDL files from directory paths that include spaces.
|A problem has been resolved that could cause an IndexOutOfBoundsException to occur when synchronizing an XSD into Rational Integration Tester that defines an attribute without a type. RIT will now default to using a string type where no type is specified.
|A problem has been resolved that meant an error would occur if a user attempted to apply a CHIPS schema to a Byte Array within the Message Editor.
|A change has been made to the URL of physical database transports that are created when Tester synchronizes with WebSphere Application Server. The current schema is now included in the URL. This means that if the WAS data source uses a customised current schema then the physical database resource will target the correct schema without modification.
|Performance improvements have been made to filtering in Recording Studio.
|The Java Agent now filters and matches host names case-insensitively when recording or routing Java messages.
|A problem that meant a user could skip to the summary page of the Recording Studio stub wizard without providing all the necessary data has been resolved.
|In previous versions of Rational Integration Tester a problem existed that meant if a recorded message consisting of only a header (no body) was exported from Recording Studio and then re-imported then the header information would incorrectly appear in the body section. This problem has been resolved for new exports and messages consisting of only a header will be imported correctly. However, existing exported events will still import incorrectly as the problem occurred during the export.
|A problem that meant that the 'first' Requirement created from Recording Studio would sometimes not show in the Test Factory view until a second requirement was created has been resolved.
|A problem that meant attempting to open a saved chart resulted in a NullPointerException when it contained Log Measurement counters has been fixed.
|A problem that meant the Message Difference Window could show differences between certain messages containing repeating elements when there were no differences has been resolved. Tests involving such comparisons would still (correctly) pass; the defect was in the way that the MDW re-evaluated the messages. Typically the errors would manifest as additional repeating elements shown in the Message Difference Window.
|In previous versions of Rational Integration Tester, changes to the "iterations" field of the "Iterate Test Data" action editor were not saved if the user had not removed keyboard focus from the field before saving the dialog. This has been fixed.
|A fix has been made to the SQL Query action so that the Interval and Timeout parameters to the "Retry Query until assertion passes" option on the dialog are disabled unless the Retry check box has been selected.
|The SQL Query action no longer allows a user to delete the Equality validation check if it is the only one present. The user must now uncheck it if they do not want it to run. Previously a user could delete it but Tester would restore it when the action was re-opened which was confusing for users.
|A problem that meant SQL Query Actions were not being marked as edited when values were changed directly within the table's cells (as opposed to using the Edit Cell button) has been resolved.
|An issue has been resolved that meant if a schema containing elements was applied to a message using the Retain Data option then RIT would re-order the message such that the choice option was placed as the first element.
|Tag values are now expanded correctly when used in messages based on CHIPS and FedWire schemas. Previously the tag values were not inserted into the messages correctly at run-time. Note that because these schemas are fixed-width if the user choose the 'Treat as plain text' option then tags will be truncated.
|A problem which meant copying and pasting text nodes in the message editor could lead to an error dialog being displayed (and nothing being copied) has been resolved.
|In previous versions of Rational Integration Tester an error could occur if a message action was linked to a requirement, the message content then changed and the dialog then saved choosing the 'Discard' option. This has been resolved. Additionally, an error that meant requirements could not be saved if the dialog was showing the Documentation tab has been resolved.
|In Rational Integration Tester 8.5.0 if a user specified Simulate Error in the pass-through settings for a stub's operation that used the CICS transport then the chosen CICS return code was not correctly saved resulting in a return code of 0 being used. This issue has been resolved and the entered return code is now used.
|In previous versions of Rational Integration Tester if an environment variable was used to reference a test data file and a user switched into an environment where the variable was undefined or empty then tests would continue to run for a few iterations and would appear to pass. This problem has been resolved. In 8.5.1 if the file does not exist the test will fail with an appropriate error message showing the file path/name before and after tags are resolved.
|Previously, Rational Integration Tester could sometimes appear to hang while running a test that published many thousands of messages over EMS. This problem no longer occurs although users should note that the -Dcom.ghc.ghTester.gui.console.trim=true Library Manager JVM option may need to be used to order to prevent memory being used up holding the messages within the console output.
|The Rational Test Virtualization Server Agent's configuration file now informs the user that to add additional "attributes" to the Agent they must insert new elements.
|In previous versions of Rational Integration Tester adding the Java agent configuration to Websphere Application Server's startup configuration would prevent WAS from initializing correctly. This has now been rectified, although users should not that it is necessary to modify the Java security policies. Details are provided in the readme file located with the JavaAgent jar file in the RIT installation.
|In previous versions of Rational Integration Tester adding the Java Agent configuration to the Glassfish startup configuration would prevent the server from initializing correctly. This issue has been resolved.
|In previous versions of Rational Integration Tester there was a problem that meant, in some circumstances, when running a suite of tests against a webMethods Integration Server stub the stub would respond once and then shut down with subsequent tests within the suite being directed to the live service. This problem has been resolved.
|Previously, if a user cancelled a stub that contained multiple operations then a console message was output indicating that the stub had failed rather than been cancelled. This issue has been resolved and the console message now accurately reflects the cancellation.
|A problem that meant HTTP responses with a 204 NO CONTENT status code were not recorded by Rational Integration Tester's HTTP proxy has been resolved.
|A problem that meant the version string from a JDBC Proxy running inside WebSphere Application Server would not be displayed correctly in the Agent's view of Rational Test Control Panel has been resolved.
|With previous versions of Rational Integration Tester it was not possible to set up SQL recording or database stubbing for JDBC data sources in IBM WebSphere Application Server with cell, node, server or cluster scope if those data sources had the same JNDI name as application-scoped data sources. This problem has been resolved and it is now possible to set-up such sources for SQL recording and database stubbing.
|In previous releases of Rational Integration Tester problems could occur when virtualizing MySQL databases using the embedded simulation database (Derby). The problems occurred because MySQL and Derby apply different case-sensitivity rules for SQL statements which could lead to SQL statements accepted by the MySQL driver being rejected by Derby (the embedded simulation database). This version of Rational Integration Tester attempts to improve compatibly by adjusting the structure of the embedded simulation database as it is created to use upper-case column and table names which ensures that all application SQL that does not use MySQL quotes (`) will work with the embedded simulation database. For applications that do use MySQL quote characters in SQL it is recommended that a second MySQL database be used for virtualization instead of the embedded Derby database.
|The user interface for the database stub editor has been improved. In previous versions of Rational Integration Tester, only recorded queries that were suitable candidates for editing the stub were shown in the Edit Database Stub dialog. This led to confusion as the contents of the dialog did not match the list of recorded queries in the stub. The dialog has been improved, displaying all of the queries in the stub, and providing additional user feedback if the user selects a query that is not a suitable candidate for editing the stub.
|With previous versions of the Rational Integration Tester JDBC driver problems could occur when the location of the simulation database location changed. This is most likely to occur when users are working with the embedded simulation database and a pool of agents because the embedded database runs co-located with the agent. It may also occur when several team members are collaborating and have their own environments defined in the Rational Integration Tester project. The effect of the problem was that the JDBC Driver would continue to attempt to use the old simulation database connection instead of the new location resulting in warnings being emitted to Rational Test Control Panel along with stub failures. These issues have now been resolved and the driver correctly handles a change in This has now been fixed.
|A problem involving using recorded queries to edit MySQL database stubs has been fixed. In previous versions of Rational Integration Tester, editing a MySQL stub using a SQL SELECT that included table aliases but that did not include a WHERE clause would fail. This now works.
|Two new options have been added to the GHTesterCmd command line tool to delete results from project Results Databases. This functionality makes it easier for customers to script the deletion of results. The two new options are : delete-all-results-keeping and delete-all-results which, respectively, allow for selective deletion or complete deletion of results in the specified database.
|It is now possible to use repeating elements within a Test Data Set where the parent ID stays the same on each row of data. Previously the parent ID column had to contain NULL on subsequent 'child' rows. Where this new functionality is used Tester will use the change in parent ID column value to indicate the end of the repeating data block. The child elements must still be grouped together as rows immediately following the parent in the Test Data Set. This feature makes it easier to use repeating elements from data queried from a database as the NULL structure is difficult to create in that case. This functionality was requested in devWorks RFE 28813.
|If a project only contains a single environment then Rational Integration Tester will now automatically pick this environment when the project is loaded. If there is more than one environment Tester will not pick one and the user must do it. This is to avoid users running tests against production environments by mistake. This functionality was added in response to devWorks RFE 28176.
|A Rational Integration Tester install now includes an addNumbersClient application which can be used against the provided addNumbersServer application to demonstrate basic test and virtualization. The addNumbersClient can be found in examples/AddNumbers/Client. The provided start-up scripts contain information showing how to configure the client to use the RIT HTTP proxy for recording, dynamic routing and sift-and-pass-through functionality.
|Rational Integration Tester's RQM Test Adapter now supports connecting to RQM servers where TLS 1.2 has been enabled. No additional user configuration is required.
|In previous versions of Rational Test Control Panel it was not possible to see the list of available stubs unless an Agent was connected because the Start Stubs dialog could not be accessed. It is now possible to open the Start Stubs dialog even when there are no Agents connected, although the stub cannot, obviously, be started.
|The logic used to select agents when starting stubs via the Rational Test Control Panel REST API has been modified such that it will use separate agents for multiple versions of the same stub in order to support scaling out stubs for and increased performance. The error reporting has also changed.
|Previously, when an SQL Query action failed due to a mismatch between the expected value and the value returned from the query the console output would display the mismatched values. This has been enhanced so that the column and row which contain this value are also displayed. In addition, if the failure occurs due to a mismatch between the number of expected columns and the number of actual columns returned from the SQL query the number and names of actual/expected columns are now shown. This enhancement was implemented in response to devWorks RFE 35672.
|Three example IBM WebSphere MQ security scripts (for the Windows platform) are now provided in the \tools\IBM\MQ directory of the Rational Integration Tester install. These provide examples of how to script the addition of the WebSphere MQ authorities required in order for the various Tester/MQ technologies (Sift And Pass Through Stubs, Alias Recording and Dynamic Mirror Queue Recording) to operate without having to grant full administration authority to the user that Rational Integration Tester uses. These scripts are provided as-is for example purposes and will require modification by a suitably competent IBM MQ administrator to take into account specific platform and security configuration.
|Rational Integration Tester has been enhanced to allow users working with IBM WebSphere MQ to override the Reply Queue that a stub will send a response to. In previous versions RIT always honoured the MQ Reply Queue header provided in the request message. This made it difficult for users to force the stub to send the response to a different queue without having to use a Publish action rather than Send Reply. A new "Override Reply Queue" check-box has been added to operations using IBM WebSphere MQ as a transport. When this is checked the value from the Queue field will be used as the reply destination overriding any value from the incoming message. When the box is not checked then the value from the incoming message will be used in preference to the value in the Queue field (which is the default behaviour to be consistent with previous versions).
|A change has been made to Rational Integration Tester such that when editing TCP/UDP Server transports, the tabs containing settings that are only relevant to TCP are disabled when UDP is the selected protocol.
|In previous versions of Rational Integration Tester there were two "Record Selected Item" options available within the Logical View of Architecture School. The first was in the main toolbar and the second was on the context menu of a selected item. This term was considered confusing as although it did add an Event Monitor and switch to the Recording Studio perspective it did not actually start the recording. A user still had to select the "Start Recording" option in Recording Studio which had an identical icon. In order to reduce confusion the options in Logical View have been renamed to "Add Event Monitor" and the icons have been changed to differentiate them from the "Start Recording" option in Recording Studio.
|In Rational Integration Tester 8.5.0, the editor for the CICS Server physical resource displayed the CICS Transaction Gateway settings on the first tab. This has been changed so that the CICS Transaction Server settings appears on the first tab and the CICS Transaction Gateway settings on the second. The order of radio buttons on the Recording & Stubs tab has also changed. The changes do not affect the requirements for using the CICS Server resource and do not require any changes to existing projects.
|The RIT preference "Show header information panels in editors" (in the General category) is now obeyed when editing physical and logical components in Architecture School.
|Rational Integration Tester 8.5.1 supports the 2014 version of the SWIFT messaging standards. As RIT can only support one version of the SWIFT schema that means that the 2013 SWIFT messaging standards are no longer supported.
|In previous versions of Rational Integration Tester, WebSphere Application Server synchronization did not recognize Message-Driven Beans within enterprise applications. This has now been rectified and synchronization will recognize Activation Specifications and create the appropriate queue and transport bindings in RIT.
|To remove ambiguity, the database to which Rational Integration Tester writes test/stub results is now referred to as either the "results database" or the "project results database" throughout the application. Previously it was sometimes also referred to as the "project database".
|Recording Studio now allows for searching within the header of messages. Previous versions of Tester only allowed for searching within the body. A check box has been added to the Finder panel in Recording Studio If selected before starting a search then message headers will be searched as well as bodies. Note that changing the value of the check box after running the search will not update the existing results unless the search is re-run. The default behaviour is not to search the headers. i.e. a user must opt-in by selecting the check box. This selection will be remembered within a single session of Tester.
|It is now possible to filter used a Regular Expression (RegEx) in Recording Studio. For example, the using the following RegEx would show only messages containing Fred, Orange or London: (?=.*Fred)(?=.*Orange)(?=.*London) It is then possible to use the Finder panel in Recording Studio to search within the filtered set to see where the occurrences of Fred, Orange or London are. This technique can be used to quickly find messages in large sets of recorded events which is particularly useful in Java Virtualization.
|When saving messages from recording studio and choosing to create a stub the default selection for storing data has been changed from "in a data model" to "as hard coded values".
|Rational Integration Tester's Test Suite editor has been enhanced to allow users to temporarily disable non-root scenarios, tests, performance tests, or nested test suites. If a non-root scenario is disabled then the complete sub-tree (from that scenario) will be ignored when the test suite runs. If a nested test suite is disabled then the contents of the whole nested test suite will be ignored when the test suite runs. This enhancement was implemented in response to devWorks RFE ID 28368.
|A new feature was added in GH Tester 5.4.0 (and is therefore present in Rational Integration Tester from versions 8.0.0 onwards) that causes Tester to automatically map new columns it finds in Test Data Sets if a tag exists with the same name as the column. This feature was implemented to allow a user to add a new column to a spreadsheet and a tag to a linked-requirement before re-running all the tests linked to the requirement. At run-time the test engine automatically detects the new column and tag and maps them without the user having to edit every test in turn to add the mapping. This makes it significantly faster to add new mapped values into messages. This feature works well but it has a potential side-effect for legacy users of GH Tester. Specifically, if a user of GH Tester 5.2.11 or earlier has a Test Data Set containing column names that are identical to tags then, when the tests are run in Rational Integration Tester, the tag will be automatically mapped to the column in the data set which may unex
|The "Run..." options dialog for tests now contains labels for the the selection of "Run now locally", "Run now remotely", or "Run later" as the "execution preference" field.
|The Timings column in the Advanced View of Rational Integration Tester's stub editor has been removed. It is now possible to specify per operation response-time configuration in the Properties tab. Note that previous versions of RIT did not save the data set-up in the Timings column so there is no migration of data into the Properties tab.
|Improvements have been to Rational Integration Tester's HTTP proxy to deal with malformed http requests where // separators are found within the URL rather than just as the host name separator. Previously such URLs would be modified by the proxy such that the destination system would not correctly recognise them.
|A problem has been resolved that meant if Rational Integration Tester's HTTP proxy received an HTTP request where there was no url_path element specified it would reduce it to a blank string resulting in invalid content being sent to the destination.
|Previously, when enabling an Oracle, Microsoft SQL Server, or MySQL database for SQL recording and database stubbing within IBM WebSphere Application Server a user had to manually create both data sources for connecting to the live and simulation databases. The set-up of the data source for connecting to the simulation database has now been automated, and the user has to manually create only the data source for connecting to the live database on IBM WebSphere Application Server. The integrated Derby database can now also be used as a simulation database.
|Rational Integration Tester and the RIT Agent version 8.5.1 ship with a version of the Derby database drive, so users no longer need to add the Derby driver using Library Manager. Library Manager has been updated to show that Derby is available and pre-installed.
|In previous versions of Rational Integration Tester it was only possible to use the database stub editor to add a new table into a database stub when the live database was available. This meant that the database stub editor could not be used effectively when the live database was stopped, or could not be accessed on the network. This has been resolved and it is now possible to add tables (defined using a spreadsheet) without access to the live database.
|In previous versions of Rational Test Control Panel if a scenario was saved that contained multiple instances of the same stub then when it was loaded back again it may not have loaded as-expected. RTCP is now consistent in the way it saves and loads scenarios containing multiple instances of a stub running on different agents. RTCP will always attempt to start up multiple copies of the stub on different agents in order to scale-out and improve performance.
|Stub scenarios that contain instances of a stub running on multiple agents (for scaling out of stubs) can now be imported into a Rational Integration Tester suite from Rational Test Control Panel.
|When starting a stub from the VIE dashboard in Rational Test Control Panel users may now specify a number of agents for the stub to start on rather than having to select specific agents. If the stub is later saved into a scenario, the number of requested agents is recorded as part of that scenario so the exact same agents do not need to be available to start the scenario again; just sufficient quantity.
|Rational Integration Tester, Test Control Panel, the RIT-Agent and the Platform Pack now require IBM's Installation Manager 1.70 or later to be installed.
|The MQ API Exits to support zero-environment recording are now supported on the zLinux platform.
|A new -D option has been added that allows the Java "Object" as an Any type in Tester schemas. This can be useful in some circumstances when using Plain Old Java Objects (POJOs) with Rational Integration Tester. Any existing Java Object schema will have to be rebuilt to take advantage of this change. This option is off by default but should a user require it then they should use: -Dgreenhat.schema.mapper.testAny=true Note that setting this property may result in a change of behavior when using other types of schema. The useabiltiy of the right-click schema menu has also been improved when there are a large number of Java Object definitions in a schema. Should a user require the old menu behavior to be used then the following -D flag can be used to revert to pre-8.5.1 functionality: -Dgreenhat.java.object.dontConvertMetaData=true
|A number of performance improvements have been made to the agent that is installed into CICS for Tester's CICS DPL Virtualization solution. These reduce the processing required in the CICS TS environment when DPL calls are made that Tester is neither recording or virtualizing.
|Date Released
24 September 2013
|Rational Integration Tester component
|In Rational Integration Tester 8.5.0, if a user changed the action type to 'Function' in the field editor and then clicked Ok, the change would not be saved. This problem has been corrected.
|Log file monitoring settings are now remembered in the WebSphere Application Server resource in logical view
|Rational Integration Tester could send an XML message that made use of a namespace without correctly declaring it. The consuming application would then fail to parse the XML correctly and the service could not be tested. This problem has been resolved.
|The "Run Command" action failed in Windows 2003 environments. This was caused by changes intended to support multiple DOS codepages. This problem has been resolved and Run Command will now execute successfully in Windows 2003.
|Extra console logging was being sent from the Agent to RTCP, this logging information was not being used and was using up network bandwidth unnecessarily. This change will provide a performance benefit in situations where the machine running the Agent is network traffic constrained.
|Synchronization with a WebSphere Application Server running on localhost no longer generates multiple HTTP endpoints in logical and physical views for any web services running on that host.
|If an Identity Store was referenced from a WebSphere Application Server physical transport and that Identity Store had a path that used the %%PROJECT/ROOT_DIRECTORY%% form then RIT would fail to connect to the WAS instance. However, if the identity stored had been specified using an absolute path a connection could be made. From versions 22.214.171.124 onwards Identity Stores that reference the project path can be successfully used in connections to WebSphere Application Server. This problem has been resolved.
|Use of the Iterate-While action could lead to unexpected results when the action condition contains ECMAScript. This is because the action was being called once before the while loop first iterated. If the ECMAScript contained side effects (such as decrementing the value in a tag) then the user would not see the expected results as in the first iteration the script would be called twice thus decrementing the tag by two rather than the expected one. This has been resolved, the action script is now only called on actual iterations.
|If a user created a subfolder under a Service Component in Rational Integration Tester, created a stub inside that subfolder and then published the stub to Rational Test Control Panel then, although the publication process would complete successfully the stub would not show in the RTCP dashboard. This problem has been resolved.
|In some circumstances, having stub performance optimizations enabled (set on the properties tab of a stub) could cause the storing of values into tags from fields in the received message to fail. Tags are now populated correctly.
|Date Released
13 August 2013
|Rational Integration Tester component
|Discarding a change to a linked message no longer causes a test to be marked as dirty in Rational Integration Tester.
|Previously, Results Gallery did not render some Unicode characters in specific fields properly when Oracle or MySQL databases were used. This problem has been resolved. Note: The databases themselves must be set up in the appropriate Unicode mode. For more information about this, see http://pic.dhe.ibm.com/infocenter/rithelp/v8r5m0/topic/com.ibm.rational.rit.install.doc/topics/t_ritinst_creat_proj_db_oracle.html and http://pic.dhe.ibm.com/infocenter/rithelp/v8r5m0/topic/com.ibm.rational.rit.install.doc/topics/t_ritinst_creat_proj_db_mysql.html.
|Attempting to record an IBM WebSphere MQ-based operation (by using (dynamic) mirror queue recording) where the operation does not have a queue name defined for it now causes Rational Integration Tester to display an error message stating that it is not possible to record in this way without a queue name. Previously, Rational Integration Tester would start recording all queues, which is not the behavior that users would have expected.
|On Microsoft Windows systems, the taskbar button that appears when the Rational Integration Tester splash screen appears now says "IBM Rational Integration Tester". Previously, "GH Tester" was displayed.
|Previously, data entered on the Agent window when setting up a performance test was not saved unless the Counters table or Hosting agent values were changed. This problem has been resolved.
|A number of problems caused by Byte-Order-Marks in UTF16/UTF-16LE text have been resolved. For example, previously when UTF16LE encoded messages were received over HTTP they were not being decoded correctly.
|If a user attempts to record Type 1 IMS messages by means of the Rational Integration Tester TCP proxy, the text "IMS Requests with OTMA headers are not supported" is now displayed in the recorded message header. Previously, it was not clear to users why the recording was not working correctly.
|A number of English strings displayed when deleting test results in Results Gallery have now been externalized and translated correctly.
|In Recording Studio, if an invalid RegEx expression is used to create a filter rule, an error message about the invalid RegEx expression is no longer displayed for each and every row.
|In Architecture School, if a physical web server resource is configured with a host name containing an IDN, the host name is now correctly decoded/encoded when recording and stubbing against that server.
|Previously, a race condition that meant test suites containing IBM WebSphere MQ-based stubs did not always successfully stop the stubs at the end of tests (and would then be stuck at 99% complete). This problem has been resolved.
|Previously, if a user created a fixed-width record layout and defined a field as "center align" with no pad-left character but with a right-pad character, the right-pad character was added to the left, which caused invalid padding character results because the correct padding character was being added to wrong side. The pad character is now added correctly to the right side. Therefore this problem has been resolved.
|Previously, opening the Iterate and Iterate-While test actions (without making any changes) could trigger the dirty state of a test. This problem has been resolved.
|Previously, failures would occur in Results Gallery if users attempted to view the detailed report for a test suite or test cycle that included a message containing extended Unicode characters. This problem has been resolved.
|Previously, performance tests did not run correctly if the currently selected environment's name contained extended Unicode characters. This problem has been resolved.
|Previously, Rational Integration Tester bound to Identity Stores by using absolute file paths instead of project-relative (assuming that the identity store was held within the project directory structure). This caused project portability problems. Identity Store paths can now be project-relative. Therefore, this problem has been resolved.
|Previously, the Rational Integration Tester plugin for Jenkins/Hudson displayed results in a very small screen area which made it difficult to view the results. This problem has been resolved.
|The Run window that is displayed when users right-click a stub in the Test Factory or Test Lab perspectives and click "Run…" now contains a Date Picker button instead of the non-functional "Choose" button.
|The addNumbers server application that is provided in the examples\add numbers directory of the Rational Integration Tester installation directory now looks up and reports its IP address correctly in the URL on the user interface. This means that the WSDL URL can be pasted into Rational Integration Tester.
|Some changes have been made to improve the reliability of the opening of Microsoft Excel when editing database stubs from within Rational Integration Tester. If users have set up a mapping between the .csv file type and Excel on the Applications page of the (Project) Preferences window or selected the application in the "Launch Command" field on the External File Association window when editing the stub, Excel should now open correctly.
|Previously, if a user installed Rational Integration Tester 8.5.0 or Rational Integration Tester Agent 8.5.0 on any supported version of Microsoft Windows and another user who was not an administrator attempted to run the application or Library Manager, an error message was displayed. This problem was caused by the installation process setting security on a number of .ini files so that only the user who installed Rational Integration Tester (or another administrator user) could run the applications. This problem has been resolved in Rational Integration Tester 126.96.36.199 and Rational Integration Tester Agent 126.96.36.199. For more information, see http://www.ibm.com/support/docview.wss?uid=swg21638548
|Previously, when using the Rational Integration Tester Java virtualization agent to record Java invocations in a Java 6 application, a redundant warning message was displayed when users stopped recording. This warning message is no longer displayed.
|Previously, Rational Integration Tester could fail to record events in Recording Studio by means of proxies because of a deadlock in Rational Test Control Panel. The problem was indicated by Rational Integration Tester displaying indefinitely a message window stating that a recording rule was being set up. This problem has been resolved.
|A problem that caused the error "Fatal error: com.ghc.tags.TagNotFoundException: tag named "Birthdate[0]" was missing from store" when running a test after upgrading a GH Tester 5.2 project to Rational Integration Tester 8.0 has been resolved. The issue was caused by the use of repeating elements and tags.
|Previously, uninstalling Rational Integration Tester 8.5.0 on the Apple Mac platform did not delete symbolic link files created during installation. The symbolic link files are now deleted correctly during uninstallation. Therefore, this problem has been resolved.
|If users start performance tests without having configured any load-generation engines, a meaningful message is now displayed by Rational Integration Tester.
|In Rational Integration Tester 8.5.0, the Apache Derby database installation that is part of the installation of Rational Integration Tester or Rational Integration Tester Agent installation writes a run-time log to the install directory. This has been changed to use a user-specific directory instead of the installation directory.
|Previously, in some cases (particularly when editing byte streams) the Message Editor stripped double CRLF sequences. For example, if a user edited the binary stream 474554202F696E6465782E68746D6C20485454502F312E310D0A486F73743A207777772E6578616D706C652E636F6D0D0A by adding another "0D0A": 474554202F696E6465782E68746D6C20485454502F312E310D0A486F73743A207777772E6578616D706C652E636F6D0D0A0D0A and then clicked OK to close the Message editor, the added "0D0A" would be missing if the user subsequently reopened the Message editor. This made it difficult to create requests where such sequences are required. This problem has been resolved.
|A change has been made to the way Rational Integration Tester trusts SSL certificates. This is to avoid unnecessarily requiring a root certificate in the identity store.
|Previously, when cloning a stub in Rational Test Control Panel, a Rational Integration Tester Agent was offered twice if there was more than one engine available for that agent. This problem has been resolved.
|When cloning a stub in Rational Test Control Panel, users can now use the Filter Agents button to help with Agent selection. Previously, nothing happened when the button was clicked.
|A number of problems were introduced in Rational Integration Tester 8.5.0 which meant that users would not always see the behavior they were expecting when switching between the docked Test Action editor and the Pop-up Test Action editor. These problems have been resolved.
|A number of project portability issues caused by the use of "\" in file paths have been resolved. Previously, if users entered a path on a computer running Microsoft Windows (for example, a project relative path) and then opened the same project on a computer running Linux, the path resolution failed because "\" needs to be "/" on Linux systems. Rational Integration Tester now convert the separators in the path automatically.
|Previously, recorded messages could become corrupted when using packet capture (pcap) to record HTTP traffic and a reply with Content-Length of 0 was received by Rational Integration Tester. This problem has been resolved.
|Previously, after saving a test data set, the 'dirty' indicator was not reset, which meant that Rational Integration Tester would not disable the Save icon. This problem has been resolved.
|Previously, stubs could not be published to a Rational Test Control Panel instance hosted on a computer with an IDN host name (host name containing non-ASCII characters) if that stub had previously been published at a lower version number. Users would see error "[CRRIT8242E] Could not connect to the server". This problem has been resolved.
|Previously, it was not possible to configure a test suite in Rational Integration Tester to use stubs from a Rational Test Control Panel domain that contained Unicode characters. This problem has been resolved.
|The email results publisher now support SMTP email servers specified with IDN server names (containing non-ASCII characters). Previously, an error would occur if an attempt was made to run a suite published by means of an SMTP email server.
|Previously, any database stub started from Rational Test Control Panel could result in an exception being logged every five seconds to the console log of Rational Test Control Panel. However, there were no adverse effects on the stub, which would run as expected. The exception logged would be in the format "java.lang.NullPointerException at java.io.File.
|In Rational Integration Tester 8.5.0, importing a DER key and certificate into an identity store caused the key to be configured with a blank password. This was acceptable unless the key was being used for mutual authentication or if the Rational Integration Tester HTTP proxy was being used because the proxy requires the correct value of the password. In Rational Integration Tester 18.104.22.168, the import process now results in the use of the password that protects the Java keystore (JKS).
|Rational Integration Tester can now import PEM certificates.
|When importing an existing keystore, any certificates with the same password as the keystore are now unlocked automatically, so users do not have re-enter the same password again.
|Previously, when using the Identity Store window (in the Physical View of the Architecture School perspective) of Rational Integration Tester, if the importation of a certificate was cancelled, the cancellation did not terminate cleanly and empty window was displayed. This problem has been resolved.
|The certificate provided with the Rational Integration Tester HTTP proxy server has been updated to include the Basic Constraint extension, which is required by Oracle WebLogic application servers. Previously, the absence of this extension meant that HTTPS communication between a client and an Oracle WebLogic server could not be recorded (in plaintext) by means of the Rational Integration Tester HTTP proxy.
|Rational Test Control Panel now limits the activity log to 2,500 entries. This is to prevent performance problems, especially at start-up. It is not anticipated that a user would want to look through a large number of entries because the activity log is intended to be a snapshot of what is happening 'now'. When the log reaches this new limit, Rational Test Control Panel will now purge older entries automatically. When this happens, an entry will be put in the activity log to alert users about what has happened.
|Previously, an error could occur if a user used an IDN (non-ASCII) server name to create a physical IBM WebSphere Application Server instance and then synchronized Rational Integration Tester against that server. This problem has been resolved.
|A change in the log level made on the Rational Test Control Panel agents page will now take affect within five seconds. Previously it could take up to 30 seconds for a Rational Integration Tester proxy to detect the new log level.
|A number of changes have been made to the Rational Integration Tester HTTP proxy to avoid exceptions occurring during HTTP CONNECT parsing. Typical symptoms will include a failure of the live system or stub to receive the message from the client and an Null Pointer Exception in the console output of the proxy.
|A number of problems have been resolved that caused Rational Integration Tester to hang when launched on OS X. This problem has been observed after upgrading OS X to 10.8.4 or later. Rational Integration Tester now uses the IBM Java runtime, which has resolved most of the problems. Some users still report application hangs if Rational Integration Tester is run from the launchpad. These problems can be avoided by running Rational Integration Tester from the Finder, or the launch bar (having pinned the application to the bar from Finder), or from a command prompt.
|Previously, the contents of the Assert tab in an SQL Query test action (in Test Editor) could not be edited. This problem has been resolved.
|Operations created from recorded JavaScript Object Notation (JSON) events now have a schema root set automatically. This resolves a problem that could cause an exception when creating stubs from recorded JSON events in Recording Studio.
|Previously, if users applied a schema to XML added to a message by means of the Import XML menu option in the Message editor, the contents of the message were lost after the editor was reopened. This problem has been resolved.
|Previously, if Rational Integration Tester was synchronized against an instance of IBM WebSphere Application Server where the canonical name was 'local host', web services would not be synchronized into Rational Integration Tester. This was caused because Rational Integration Tester was deliberately ignoring 'local host' variants of services because normally WebSphere Application Server provides two copies of each service: local host and host name qualified versions. However, in the case where the server had been set up only on local host, this meant that all services would be ignored. Rational Integration Tester now attempts to detect this scenario and operate accordingly.
|A change has been made to the way in which the Rational Integration Tester HTTP proxy processes HTTP redirects to support clients using older versions of the Apache HTTP Client library (specifically 4.0 beta). This version of the library makes some assumptions about the persistence of a redirected HTTP connected which were not previously supported by the Rational Integration Tester HTTP proxy.
|A change has been made to the Rational Integration Tester Scenario Editor (within the Test Factory perspective) to prevent it from opening as an unnecessarily wide window. Changes have also been made to allow columns widths to be resized correctly.
|Previously, an exception would be logged to the console output of Rational Integration Tester Agent if it was started on a computer where the host name contained non-ASCII characters (for example, IDN host names).
|Previously, if Open Office was used to edit a stored procedure within a database stub and the stored procedure contained either an OUT SYS_REFCURSOR (Oracle) or OUT CURSOR (DB2) parameter, subsequent edits would fail and even though the stub would start the stored procedure call would not return the expected results.
|If a Java virtualization agent routing rule is deleted manually in Rational Test Control Panel, the console output of stubs that were using that rule will now show the removal.
|Previously, an intermittent problem that could cause Rational Integration Tester to hang when applying a schema to an empty message. The problem appeared to occur more often on the Linux platform. This problem has been resolved.
|Previously, a Null Pointer Exception could be caused when attempting to record an IBM WebSphere MQ-based operation using dynamic mirror queue recording. This problem has been resolved.
|Previously, if users attempted to open a database stub without first selecting an environment, a Null Pointer Exception could occur. Now, a meaningful error message is displayed.
|The imagery used within message trees to indicate which type of integer a field is (short, integer or long) has been changed to avoid confusion.
|Previously, a failure would occur when learning a JDBC stub against an Oracle database if a stored procedure call returned a result set containing a NUMBER type. The user would see an error stating "ORA-01727: numeric precision specifier is out of range (1 to 38)". This problem has been resolved.
|Previously, if a user used Linux/LibreOffice to edit the contents of a database stub (for example, a table), the changes could be lost because Rational Integration Tester would think that users had saved the modifications before they actually had saved them. This problem occurred only if there were LibreOffice processes already running at the point when the Database Stub Editor launched another instance of LibreOffice.
|Some users have experienced problems when performing multiple agent-based recordings in Recording Studio when environments are locked in Rational Integration Tester. The root cause of the issue is that Rational Test Control Panel allows Rational Integration Tester and Rational Integration Tester Agents to publish rules to Rational Test Control Panel when the environment is locked but does not allow the rules to be deleted. This can lead to inconsistencies when recordings or stubs are stopped because the recording/routing rules that have been created cannot then be removed. For an HTTP or JDBC stub, this means that the stub can start correctly but when the stub stops, a stale rule is left in Rational Test Control Panel. For JDBC recording, with simultaneous learning of a new stub, when the learn process ends the stub fails to delete the rule and as a side effect the recording rule is also not cleaned up. A change has been made to enable Rational Integration Tester and Rational Integration Tester Agents to delete rules, even when the environment is locked, while still preventing locks from being overridden from Rational Test Control Panel itself. This resolves the problems that are seen when the environment gets into an inconsistent state.
|Previously, regular expression store actions could be cleared within the field editor of a Run Command action. This problem has been resolved.
|Previously, Rational Integration Tester could hang when deleting a RegEx specified on an assertion on a column within a SQL Query test action. This problem has been resolved.
|Previously, it was not possible to add a column to a previously learnt table in a database stub. This problem has been resolved.
|Previously, it was not possible to view test suite results from Rational Test Control Panel for test suites containing tests created for WebSphere Application Server service components within Rational Integration Tester. This problem has been resolved.
|Previously, a performance test could hang after all the iterations were run if the test used tests from across multiple service components. Now, a performance test of this type will run but at the end of the test it will freeze at 100% complete and the results do not appear in Results Gallery. Additionally, the Rational Performance Tester Agent will now become non-responsive and will need to be restarted.
|A number of translation defects across Rational Integration Tester and Rational Test Control Panel have been resolved.
|A change has been made to ensure that Recording Studio searches (press CTRL+F in Recording Studio) will run even if a computer running Rational Integration Tester has only one available processor core. Previously, although the Find window would appear, search would not run if Rational Integration Tester could not find a separate processor core upon which to run the search.
|A change was made in Rational Integration Tester 8.5.0 which meant that default protocol used for SSL based commas become SSL rather than TLS, which had been the default for all versions of Rational Integration Tester previously. This introduced an incompatibility with the Rational Integration Tester HTTP proxy which meant that a Rational Integration Tester test that attempted to make an HTTPS connection by means of the proxy would fail. This change has been reversed and the default is now SSL again.
|A number of minor string concatenation changes have been made to provide better translated text.
|Date Released
14 June 2013
|Rational Integration Tester component
|Rational Test Control Panel now checks that files uploaded to its Stub Publication interface are valid Tester stubs before saving them. This prevents the upload of arbitrary code.
|Rational Integration Tester now supports floating licences on AIX (32-bit and 64-bit)
|Previously, for Linux installations, an
|The sample fixed-width font shown in the font-selection preference dialog box is now a fixed width font.
|When installing Rational Test Control Panel in user-mode on Linux one directory was defaulting to /var/rtcp which the user was unable to write to. Previously users had to manually change this directory before finishing the installation. This directory name now defaults to /home/
|The documented installation steps for the z-based MQ API Exit have been updated to correct some errors and omissions.
|The Rational Integration Tester Installation Plan in the documentation has been updated to deal with some errors and omissions.
|When creating a test data set using the Test Action Wizard the user now has more control over the way in which NULL tags are to be handled.
|Tester will now only show resources that can be stubbed when a user is selecting services to stub in the References panel of the Test Suite Scenario Editor.
|The Sleep Action dialog box has been updated so that it clearer when the range (min, max) values are applicable
|A problem that meant Unicode characters (e.g. Russian) in XML could cause a message to fail to be published has been resolved as part of the general Unicode compliance work.
|A problem that meant a large amount of user-entered data could be cleared out of a message-editor when the transport is changed has been resolved. For example, in previous versions, if an EMS transport was re-selected then JMS headers and message properties would be blanked out and would require re-entering.
|In previous versions if a user is has the "Run From Memory" preference set and creates tests and stubs using the MEP wizard then those tests/stubs may fail if they are run before the editor is opened for them. Errors would not be seen if the "Run From Disk" preference was selected or the user opened the editor for the test/stub (regardless of whether they simply closed the editor without making any changes). This problem was caused by the wizard not correctly populating the tests/stubs and has been resolved.
|Within a test or stub it is now possible to create an over-ridden environment tag if the environment tag already exists with that name.
|The JAR file definitions in Library Manager for WebSphere MQ and Web Sphere Application Server have been updated to ensure a clean separation between the two applications. This avoids a problem whereby selecting WebSphere Application Server in Library Manager could prevent Interceptor-based recording from working again MQ.
|The wlclient.jar file has been removed from the Library Manager definitions for Oracle's WebLogic server. This jar file is not required by Tester and its inclusion can prevent JMS from operating correctly against WebLogic if IIOP is disabled.
|A problem that meant configuration values from LibraryManager.xml were not correctly applied to a new (or updated) version of Tester or the Agent until Library Manager was run and ok pressed has been resolved. The installation process now correctly reads this file and makes the appropriate configuration settings.
|In previous versions if a test uses the textFileContent() function in a script with an invalid file name then, although the test will fail, there will be no indication to the user why the failure occurred. This problem has now been resolved and the console output will contain a message indicating the root cause of the failure.
|Previously, both paths of a decision were executed if the "Allow tests to continue even if a step fails..." check box was selected on the Config tab of the Scenario Editor window. This problem has been resolved.
|A problem has been fixed that meant, in certain scenarios, automatic tag mapping did not cause the action editor to be 'dirty' which would result in the user losing tag-mapping changes
|In some circumstances when a stub attempts to send an invalid FIX message the error would be incorrectly shown as an Infrastructure warning which could lead to user confusion. The problem is now reported correctly.
|A problem that meant the red error border shown around the location and version cells in the stub selection part of the scenario editor would not clear properly has been resolved.
|Teardown steps are now correctly executed when a test or stub is cancelled.
|Tester has long supported the use of the -Dcom.ghc.ghTester.gui.console.trim argument to automatically clear out the contents of the console output window when it reaches a certain size (as it releases memory). A problem has been resolved that meant the trimming would not occur if the messages being output to the console were themselves individually very large.
|A problem has been resolved which could result in messages being captured in Recording Studio from an z-based MQ Queue Manager showing as MQDEAD admin messages rather than the correct message.
|The MQ API Exit for the z platform now returns the correct code when an error occurs. Previously the value 0 would always be returned.
|Rational Integration Tester 22.214.171.124 included a fix that re-enabled validation of messages published by Rational Integration Tester. This fix had the adverse side effect of preventing negative testing in some circumstances because it was no longer possible to publish invalid messages. This problem has been resolved, so it is now possible to use Rational Integration Tester for both publish-validation and negative-testing.
|In previous versions if a user had replaced the standard Tester report logo image with an image of their choosing then it may not be used correctly during the File Publishing process. This is because logo file written to disk contains a timestamp. This problem has been resolved.
|A problem that meant copybooks would not build properly after being added to the schema library has been resolved.
|A problem has been resolved that meant, in some circumstances, Tester would incorrectly fail validation of a JSON message containing an array with 'n' entries saying that the schema definition only allowed for 1.
|Additional checking has been added to Tester when it attempts to load a .NET assembly to find serialiazable objects. This is to try and prevent error conditions occurring in non-Tester code when the assemblies are used.
|gzip content-encoding on HTTP messages is now handled correctly. Previously, although Tester would unzip the content the header would not be removed on the internal content which could lead to downstream problems.
|Parsing of XML files with !DOCTYPE DTD references could appear to hang Tester for a file. This was caused by Tester attempting to look up the DTD reference. If Tester was able to retrieve the file then it would follow references in that file and so on. The overall result is that Tester could appear to hang. As the DTDs themselves are not required at that point in the processing Tester no longer attempts to follow the references.
|A problem has been resolved that meant if a user re-parented a component on the logical view canvas then it would automatically zoom to 100%. The automatic zoom will no longer occur.
|A problem has been resolved with the Tester plug-ins for HP Quality Center that mean Version Control would not be enabled within QC for Tester tests. This requires specific set-up and configuration on the client machine; please see the HP QC installation guide.
|A race condition has been fixed in the code that draws log measurement values on Performance Test charts. Although IBM has been unable to reproduce the originally reported issue this may resolve a problem some customers were seeing whereby such values were not appearing on Performance Test charts.
|In previous versions of Tester almost all entries in an Agent log file started with the confusing term "WaitForExit". This is the name of the Java method that the log file entry was being made from and, as such, was being logged correctly. However, it added no value and was confusing for users. It has been removed to improve the readability of the log file.
|In some circumstance chunked HTTP recorded by the Tester proxy would still contain chunk-length information when the message body was displayed in Recording Studio. This would lead to problems when creating stubs and tests. This information is now correctly removed.
|A number of memory leaks have been fixed during the creation of stubs from Recording Studio. These leaks were encountered when creating stubs from large (e.g. 400+) message pairs and would cause subsequent stub creation to be slow and to eventually fail.
|A problem that could result in MQ-based operations and stubs created from Recording Studio operating in 'Watch' mode rather than 'Participate' mode has been resolved.
|A problem has been resolved that could cause Recording Studio to automatically switch to showing the Triggers tab (rather than the Event Monitors tab) if a recording is in progress when the user switches to the Recording Studio perspective.
|In some circumstances a yellow warning triangle would be shown against an Event Monitor (in Recording Studio) for proxy-based http recordings. If a user clicked on the warning triangle they would be shown spurious Error Processing Event messages that had not prevented normal operation. These spurious warnings have been removed.
|Deleting all events in Recording Studio could take a long time to complete. This now operates more quickly.
|XML Schemas using the nillable attribute are now processed correctly by Rational Integration Tester.
|A problem has been fixed that could result in an error being displayed when executing a test suite that stated that data was being truncated when inserting into the ACTION.DISPLAY database column. This was caused by the pasting in of Unicode text (such as text copied from Microsoft Word) into Tester as the byte-count of the text is longer than the character count. The text is now correctly truncated before Tester attempts to insert it into the database.
|The IBM WebSphere Application Server resource in Physical View can now be given a name (consistent with other resources).
|A problem that meant, in some circumstances, a user would have to open, edit and save tests created from Recording Studio before it would run has been resolved. This problem was caused by the Receive Reply formatter not being set correctly by the Recording Studio wizard.
|A number of performance improvements have been made to perspective switching. The amount of internal processing and disk-access has been reduced so users should find this is a much quicker operation.
|It is now possible for Tester's RQM adapter to connect to RQM servers that have been configured to require SSLv3 rather than TLS. Previously such as connection would fail.
|A problem has been resolved that meant if a stub starts with a transition based on a behavior's event (e.g. onStart()) then input tag overrides defined in Rational Test Control Panel are not applied to the stub.
|A number of problems that could result in an error when starting multiple stubs (from RTCP) at the same time (or near-simultaneously) have been resolved. Previously one or both of the stubs could fail to start or would be 'stuck' in the Deploying state.
|Stub configuration information set up in a Test Suite Scenario is now correctly passed to Rational Test Control Panel and used when starting up the stub.
|An error that meant stubs containing the + character in their name could not be started from an Ant task has been resolved.
|A change has been made in Rational Test Control Panel to resolve a problem starting stubs that some users had experienced when using Google's Chrome browser. Previously users had to click on exactly the right spot on the green + icon to start the stub. The entire icon should now be clickable by users.
|Some problems around the case-sensitivity names of Rational Test Control Panel domain names have been resolved. Users should note that domain names are case-sensitive so publishing to domain 'qa' is different to publishing to domain 'QA'.
|The way in which Tester connects to a WebSphere Application Server 6.1 ND system that is configured with client authentication enabled has been improved to try and avoid connection failures. Additionally, better error reporting has been provided to try and help users when certificate-errors do occur.
|In previous versions Rational Integration Tester's JDBC Virtualization capability will sometimes create Stored Procedure housekeeping tables in the user's default schema rather than the specified schema. This can result in failures to start stubs. This problem has been resolved and the schema is now created in the specified schema.
|Error reporting in failure conditions when attempting to connect to a WebSphere Application Server for the purposes of JDBC Database Virtualization set-up has been improved in order to assist with problem-solving.
|Previously, HTTP/1.0 messages sent to an Apache Tomcat 7 server by means of the Rational Integration Tester HTTP proxy could cause socket connections to be dropped. This has been resolved.
|Previously, if the Rational Integration Tester Agent was installed as a service on a computer running Microsoft Windows, stubs could bind to the same port as a "live" service already running on the computer instead of detecting that the port was already in use and moving to a different port instead. This could result in a stub receiving only some messages or not receiving any messages. The problem was caused by IPv4 and IPv6 interaction between Java and the Windows operating system. The problem has been resolved by adding specific "–D" arguments to the Java virtual machine (JVM) used to run the agent as a Windows service. These arguments cause a stub to fail to bind to a port already in use, which means that the stub will allocate a new port and messages will be received correctly.
|Previously, if an HTTP message received by Recording Studio by means of the Rational Integration Tester HTTP proxy contained an escaped URL, Rational Integration Tester could, in some circumstances, remove the escaping automatically. This meant that the message could no longer be replayed against the system under test causing failures to occur. This problem has been resolved and Rational Integration Tester no longer removes the escaping.
|Previously, an HTTP message captured in Recording Studio by means of the Rational Integration Tester HTTP proxy and containing URI-escaped characters in the URL string (already escaped by the sender) could be escaped again by Rational Integration Tester. This caused failures to occur when attempting to reply to recorded traffic in tests or stubs. This problem has been resolved and Rational Integration Tester no longer escapes message content that it recognizes as being already escaped.
|FIX groups are now correctly populated based on DataDictionary order.
|A race condition that meant some messages could be missed by Tester at the start of recording a FIX conversation has been fixed. As the first few messages contain important information this problem could result in the failure to record any FIX messages.
|Drag and drop of the 'output' message within a stub's business logic action editor has been disabled as it leads to unwanted side-effects. Users must use the move-up/move-down actions to move the 'output' message. Note that Send Reply / Publish actions explicitly added by the user are not affected by this change.
|It is no longer possible for a user to edit the output message in a stub if it is linked to a requirement. Previously the user was able to edit the message but at run-time the stub would (correctly) use the message from the linked requirement, ignoring the user's changes.
|A problem that meant not all Tester components were logging to the log file correctly has been resolved. This was caused by the entry "com.ibm.rational.level = WARNING" being missing from the various logging.properties files shipped by Tester and affected components developed since the IBM acquisition of Green Hat. The installed files now contain this missing entry.
|Tester now supports the 'default' server when recording messages flowing though the CICS Transaction Gateway.
Table of Contents:
|Date Released
05 July 2013
|Rational Integration Tester component
|Previously, HTTP/1.0 messages sent to an Apache Tomcat 7 server by means of the Rational Integration Tester HTTP proxy could cause socket connections to be dropped. This has been resolved.
|Rational Integration Tester 220.127.116.11 included a fix that re-enabled validation of messages published by Rational Integration Tester. This fix had the adverse side effect of preventing negative testing in some circumstances because it was no longer possible to publish invalid messages. This problem has been resolved, so it is now possible to use Rational Integration Tester for both publish-validation and negative-testing.
|Previously, for Linux installations, an
|Previously, both paths of a decision were executed if the "Allow tests to continue even if a step fails..." check box was selected on the Config tab of the Scenario Editor window. This problem has been resolved.
|Previously, if a user installed Rational Integration Tester 22.214.171.124-126.96.36.199 or Rational Integration Tester Agent 188.8.131.52-126.96.36.199 on any supported version of Microsoft Windows and another user who was not an administrator attempted to run the application or Library Manager, an error message was displayed. This problem was caused by the installation process setting security on a number of .ini files so that only the user who installed Rational Integration Tester (or another administrator user) could run the applications. This problem has been resolved in Rational Integration Tester 220.127.116.11 and Rational Integration Tester Agent 188.8.131.52. For more information, see http://www.ibm.com/support/docview.wss?uid=swg21638548
|Previously, an HTTP message captured in Recording Studio by means of the Rational Integration Tester HTTP proxy and containing URI-escaped characters in the URL string (already escaped by the sender) could be escaped again by Rational Integration Tester. This caused failures to occur when attempting to reply to recorded traffic in tests or stubs. This problem has been resolved and Rational Integration Tester no longer escapes message content that it recognizes as being already escaped.
|Previously, if an HTTP message received by Recording Studio by means of the Rational Integration Tester HTTP proxy contained an escaped URL, Rational Integration Tester could, in some circumstances, remove the escaping automatically. This meant that the message could no longer be replayed against the system under test causing failures to occur. This problem has been resolved and Rational Integration Tester no longer removes the escaping.
|Previously, if the Rational Integration Tester Agent was installed as a service on a computer running Microsoft Windows, stubs could bind to the same port as a "live" service already running on the computer instead of detecting that the port was already in use and moving to a different port instead. This could result in a stub receiving only some messages or not receiving any messages. The problem was caused by IPv4 and IPv6 interaction between Java and the Windows operating system. The problem has been resolved by adding specific "–D" arguments to the Java virtual machine (JVM) used to run the agent as a Windows service. These arguments cause a stub to fail to bind to a port already in use, which means that the stub will allocate a new port and messages will be received correctly.
|In Rational Integration Tester 126.96.36.199 or earlier, importing a DER key and certificate into an identity store caused the key to be configured with a blank password. This was acceptable unless the key was being used for mutual authentication or if the Rational Integration Tester HTTP proxy was being used because the proxy requires the correct value of the password. In Rational Integration Tester 184.108.40.206, the import process now results in the use of the password that protects the Java keystore (JKS).
|Rational Integration Tester can now import PEM certificates.
|When importing an existing keystore, any certificates with the same password as the keystore are now unlocked automatically, so users do not have re-enter the same password again.
|Previously, when using the Identity Store window (in the Physical View of the Architecture School perspective) of Rational Integration Tester, if the importation of a certificate was cancelled, the cancellation did not terminate cleanly and empty window was displayed. This problem has been resolved.
|The certificate provided with the Rational Integration Tester HTTP proxy server has been updated to include the Basic Constraint extension, which is required by Oracle WebLogic application servers. Previously, the absence of this extension meant that HTTPS communication between a client and an Oracle WebLogic server could not be recorded (in plaintext) by means of the Rational Integration Tester HTTP proxy.
|Previously, stub hit counters, which show the number of messages that a stub has processed, in Rational Test Control Panel were not updated for multi-operation stubs. This problem has been resolved.
|Date Released
28 March 2013
|Rational Integration Tester component
|Validation actions that fail on published messages (Send Request, Publish) are now displayed on the Console window of the Test Factory perspective and will now cause tests to fail. Previously, such actions did not fail, so there was no output about them on the Console window and tests would continue executing. Consequently, tests created in earlier versions of Rational Integration Tester that were previously receiving warnings on a publish action message may now fail.
|Previously, custom-delimited record layouts could cause exceptions when viewing recorded messages in the Recording Studio perspective if the messages contained null values. This problem has been resolved.
|The behavior of the up and down arrow buttons at the top of the Message Differences Window has been improved to make it more consistent. The arrow buttons are used to select differences for analysis.
|The Results (gallery) page of Rational Test Control Panel no longer displays an error if users choose to display the results of one or more tests that include multiple failed iterations.
|To facilitate the successful importation of a greater range of COBOL Copybook files, byte order mark (BOM) detection in Copybook files has been improved when setting the encoding type.
|Rational Integration Tester now populates Financial Information eXchange (FIX) groups in the order defined by the FIX data dictionary used.
|Previously, the error message "An unexpected error occurred: Invalid column index" could be displayed when Rational Integration Tester executed a database stored procedure with multiple output parameters. This problem has been resolved. However, if any users have encountered this error in Rational Integration Tester 184.108.40.206 or earlier, they must complete the following actions after installing Rational Integration Tester 220.127.116.11: (1) remove all .gsc files from in the .rit8 directory, and (2) refresh the database schemas within RIT. If users need assistance with either of these steps, they could contact IBM Support.
|The Results (gallery) page of Rational Test Control Panel now displays correctly in Microsoft Internet Explorer 8.
|A number of performance improvements have been made to the Recording Studio Events Wizard when creating test data sets and parameterized (data-driven) stubs.
|Previously, a race condition error that could cause application messages to be missed when a FIX stub first establishes a session. This problem has been resolved.
|Rational Integration Tester tests can be linked to HP Quality Center. In GH Tester 5.2.11 or earlier, it was possible to display snapshots of linked tests in HP Quality Center and to refresh the tests by clicking the Refresh button on the Test Script tab on the HP Quality Center application window. This functionality did not work properly from GH Tester 5.4.0 to Rational Integration Tester 22.214.171.124 inclusive. This problem has been resolved.
|Previously, errors that occurred when importing invalid COBOL Copybook files were displayed to users, so they were not notified that the files were invalid. This problem has been resolved. Thus, file import errors are now displayed when Refresh is selected.
|Rational Integration Tester 18.104.22.168 includes an IBM WebSphere MQ API Exit (64-bit) for IBM AIX that will work correctly on IBM AIX 6 (64-bit only) and IBM AIX 7 (32-bit and 64-bit). Previously, Rational Integration Tester 126.96.36.199, 18.104.22.168, and 126.96.36.199 supported only IBM AIX 7. However, 32-bit versions of the Rational Integration Tester IBM WebSphere MQ API Exit are not provided for IBM AIX, and the Rational Integration Tester IBM WebSphere MQ API Exit does not support IBM AIX 5.
|Previously, when using the Rational Integration Tester HTTP proxy to record TCP traffic, a "NullPointerException" error could lead to a failure to record any TCP traffic by means of the proxy. This problem has been resolved.
|A problem that meant a field editor could not be opened for the root node of a publish action if specific DFDL schemas were applied has been fixed.
|Operations created from recorded JavaScript Object Notation (JSON) events now have a schema root set automatically.
|Data Format Description Language (DFDL) schemas containing "xsd:choice" elements now import properly into Rational Integration Tester.
|Previously, changes to stored procedure test steps were not being saved correctly because Rational Integration Tester was not detecting the changes. This problem has been resolved.
|Previously, an HL7 message for a given HL7 DFDL schema was not parsed correctly by Rational Integration Tester. This problem has been resolved.
|If a failure occurs during the publication of stubs to Rational Test Control Panel after a domain has been created, the orphaned domain will now be deleted.
|The Edit or Create Test Data wizard now correctly adds existing tag names as columns in any spreadsheets that the wizard creates.
|The Start Stub ("+" icon) on the VIE Dashboard page of Rational Test Control Panel is now easier to use in Google Chrome. Previously, only the top few pixels responded to a click of the "+" icon. It is now possible to click anywhere on the icon.
|The "AddNumbers" sample web service that is implemented within Rational Test Control Panel now looks up and reports its IP address correctly. Previously, it always reported its IP address as 0.0.0.0.
|Previously, errors could occur while recording IBM WebSphere MQ messages using dynamic mirror queues if the WebSphere MQ transports had been created in Rational Integration Tester 126.96.36.199 or earlier and the transport was not re-opened before recording started. This problem has been resolved. The migration of Rational Integration Tester project files data has been improved to prevent such errors from occurring.
|Previously, when running Rational Integration Tester on Linux, characters could be displayed too low on some text boxes, causing the bottommost few pixels to disappear. This problem has been resolved.
|Previously, there could be an error when creating tests from recorded JDBC database events in the Recording Studio perspective. This problem has been resolved.
|A documentation defect has been corrected in Rational Integration Tester Reference Guide for IBM z/OS. The defect related to how the file containing the IBM WebSphere MQ for z/OS Intercept Exit should be unpacked on z/OS. The updated document is included with Rational Integration Tester 184.108.40.206 (refer to the docs folder in the Rational Integration Tester installation directory after installing the release) and should be the only version of the document used if deploying the exit on z/OS.
|Previously, a Rules Cache file of zero bytes being could be written to disk if problems occurred during file write, which would mean that the Rational Integration Tester project would not load.
|Previously, an error could be displayed when using a docked action editor to save changes to a Switch action. This problem has been resolved.
|Previously, the Rational Integration Tester HTTP Proxy could not be chained to another HTTP proxy when using HTTPS traffic. This problem has been resolved.
|Previously, a test containing two MQ subscribers (based on correlation IDs) with timeouts could demonstrate inconsistent behavior when a user attempted to stop the test. The problem was caused by having only a small timing window in which Rational Integration Tester could receive an MQ message just after the timeout, which meant that the message would be removed from the queue but not processed by Rational Integration Tester. If multiple subscribers were in a test, this could lead to unexpected behaviour. This issue has been resolved.
|Date Released
06 February 2013
|Rational Integration Tester component
|Additional validation has been added to response delay timings in the Rational Test Control Panel stub launcher to prevent users from entering invalid values.
|Improvements have been made to way in which host names are extracted from HTTP traffic during recording and stubbing to ensure they are identified correctly.
|Changes have been made to the base Oracle results database script to ensure that it creates all tables in a variety of Oracle database tools correctly.
|Previously, a WebSphere MQ stub configured to 'discard' a message that it did not process could pass it through (back onto the queue). This has been resolved.
|Previously, recording XML messages with empty nodes (from an operation) could cause failures, high memory or high CPU usage within Recording Studio. This has been resolved. A fix for this issue was previously released as iFix 32070.
|X12 segments and loops are now processed correctly into messages.
|The 22.214.171.124 fix pack of Rational Integration Tester would fail to install on Microsoft Windows XP if three standard environment variables (APPDATA, USERPROFILE and USERPROFILE) were missing. Rational Integration 184.108.40.206 can be installed on Windows XP successfully without these environment variables being present, although users will not be offered the ability to configure License Borrowing.
|In Rational Integration Tester 188.8.131.52, a number of test actions and the Stub Editor would always open in the 'dirty' state meaning that the user would be prompted to save on close even if they had not made any changes. This has been resolved.
|In Rational Integration Tester 18.104.22.168, ECMAScript tag substitution could lead to problems if users had tags with the same name as reserved ECMAScript keywords. For example, if a user defined a tag called "Date", a script containing "var d = new Date()" would cause an error to be raised. This has been resolved and ECMAScript keywords now take precedence. If users requires access to a tag with a clashing name, they should use the tags["
|Previously, there was a race condition that could cause individual stub worker threads to stop responding to messages. A user would experience this by seeing that some messages were never responded to, although the stub generally would appear to be responding. Over a long period of time, with a high volume of messages, more worker threads could get into this condition and the percentage of messages 'lost' by the stub would increase. This problem has now been resolved.
|If a user assigns the root node of an outgoing message (Publish or Send Request) to a tag, the tag value will now contain the full message in the form that it is actually published in. Previously, the tag may have contained the message in an internal format. For example, for SOAP messages, only the __INPUT__ version of the message was stored in the tag, not the full SOAP message including the headers.
|In earlier versions of Rational Integration Tester 8.0.1.x, feature enablement codes were not always being written to file correctly by Library Manager. This has been resolved.
|Further changes have been made to the plug-in JAR file that provides recording and stubbing for Software AG webMethods Integration Server (wmIS) to allow it to operate correctly against wmIS 6 servers.
|Previously, Rational Integration Tester integration with RQM failed if the RQM user password specified in the Agent.config file of Rational Integration Tester Agent or on the Quality Management tab of the Project Settings dialog box of Rational Integration Tester contains symbols that require HTTP encoding. This has been resolved.
|Previously, a Send Reply action contained within a data-driven stub created by using the Recording Studio Save wizard could have scalar header actions disabled on the Value tab. Unless users edited the Send Reply step to enable the header actions, missing headers could cause transport-level failures to occur whenever a data-driven stub of this type was used. This has been resolved.
|Date Released
21 December 2012
|Rational Integration Tester component
|Some functions (such as DBQuery()) are not supported for use within a field in the message editor. In previous versions of Rational Integration Tester an exception would be shown to the user that did not make it clear what the problem is. A proper error message is now displayed, advising the user of the problem and the workaround. The workaround is to use the function in a previous step and store the result in a tag.
|The Rational Integration Tester Results Database script failed on MySQL if the database's default character set was UTF-8. This is because some columns were 1 character too large for this encoding type. This problem has been resolved.
|If a user re-synchronizes Rational Integration Tester with a WSDL file that contains references to other XSD files, then Rational Integration Tester will now re-read the XSD files from disk rather than using the previously cached version. Previously Rational Integration Tester had to be re-started to force it to re-read the XSD files.
|The Message Difference Window now correctly shows XML elements containing slashes.
|Rational Integration Tester now uses POSIX-style separators in project relative paths, meaning that projects are more compatible across Windows and Unix.
|Changes have been made to try and prevent problems occurring with wmIS subscribe actions after a long-running recording has taken place.
|RegEx auto-suggestions in the Message Difference Window now correctly take into account line feeds in the source messages.
|A number of fixes have been made to the logical view diagramming component within Architecture School. These include: new objects no longer appear at the top left hand corner of the diagram, no longer automatically zooming to too high a level, deleting the last child item makes the parent return to a normal state rather than remaining as a container, and moving an item between parents no longer causes drawing issues.
|A problem that meant Results Gallery in Rational Test Control Panel would not show results correctly if a suite's remote stubs had not started has been resolved.
|A problem has been resolved that could lead to a 2052 error code being raised on a z/OS WebSphere MQ Queue Manager when recording of queues was stopped in Rational Integration Tester.
|Results Published reports are now generated even if the test suite failed to run. The generated report will contain details of the failure.
|The Message Difference Window now correctly marks an expected message as modified if it is changed with a field editor, meaning the change is saved when the window is closed.
|The project settings dialog box for the Results Publisher now makes it clearer that the user is entering a directory for files to be written to.
|If a user of Rational Test Control Panel requests that an environment is unlocked while another unlock request is already in progress, then an appropriate message is now shown to the user.
|Problems with the layout of the formatting tab for value fields in a field editor on some platforms have been resolved.
|The list of schemas shown by Recording Studio when a user right-clicks on a node in a message and chooses "Show As" is now sorted correctly in an ordered list.
|When using the Message Difference Window with stubs, the window now correctly updates the differences panel when switching between filter and validate modes.
|A defect has been fixed that meant it was possible for a user to get the stub editor event table into a 'locked' state where no changes could be made (although the stub editor could still be closed).
|A defect has been fixed that meant, in some circumstances, the Transport was appearing disabled in a messaging action (e.g. a Publish action).
|It is no longer possible to view the About box before logging in to Rational Test Control Panel. Version information has been added to the Login dialog box.
|The correct action type is now chosen by Rational Integration Tester when adding a new filter action in a message editor for a stub's input event.
|On some platforms, root/administrator privileges are required to bind to an IP port less than 1024. If a user created a stub that listened on a port lower than 1024, then it could silently fail to start due to Rational Integration Tester having insufficient privileges. Should this situation occur then an error message is now output in the console.
|It is now possible to successfully upgrade and rollback service-based components on Windows using Installation Manager. Prior to 22.214.171.124, service-based components on Windows had to be uninstalled and the new version installed as the upgrade process did not work correctly. Upgrades from 8.0.1 (or rolling back to 8.0.1) will now work correctly. Please note that upgrading from versions prior to 8.0.1 will not work and still requires the older version to be uninstalled first. It is also not possible to rollback to versions prior to 8.0.1. See the known issues in the download document for further details.
|As part of the switch to the IBM JRE (at version 8 of Rational Integration Tester) the product also changed from using Java 6 to Java 7. The behavior of a UI control widely used by Rational Integration Tester (JTextPane) changed significantly in Java 7. Specifically, the way line breaks were automatically added changed. This adversely affected Rational Integration Tester when messages without spaces in are displayed. Changes have been made in 184.108.40.206 of Rational Integration Tester to workaround the change in behavior of JTextPane and restore the previous user experience in terms of word-wrapping and scroll bars. Note that Rational Integration Tester will only line-break on word boundaries (white-space), not in the middle of words.
|Protocol Buffer messages are now being expanded correctly.
|Content typed into the message editor is now recursively expanded. For example, entering
|A defect has been fixed that meant a schema could not be selected for an already-expanded text node. This was a regression issue and the functionality has now reverted to the correct behavior.
|A regression error has been fixed that meant Rational Integration Tester was allowing users to pick a Schema for a node in a message editor that could not have a schema (such as an integer).
|A defect has been fixed that meant an exception occurred when a user tried to create a Test from recorded TCP/IP traffic using the Recording Studio Save wizard.
|If an agent computer cannot connect to the Results databases, then this is reported back in the Performance Test console. Previously it was not clear to the user why the test had been cancelled.
|It is now possible to change the type of a message action when the action editor is docked.
|Changing the watch mode setting between Watch and Participate in an EMS-based messaging action now correctly triggers the dirty state, meaning the action can be saved.
|A problem that meant a schema refresh for SAP IDOCS would fail if version 3.0.8 of the SAP JCo library was used has been resolved.
|Copybooks containing the characters -- within comments are now correctly parsed.
|A defect has been fixed that meant a dialog box could be shown to a user multiple times after editing the pass-through properties for a stub if they then pressed Ctrl+S.
|The JAR files for the embedded Eclipse help for the Rational Test Virtualization Server Reference, Rational Performance Test Server Reference, and Rational Performance Test Server Getting Started Guides are now installed.
|A defect has been fixed that meant the Find feature was not scrolling the message editor correctly when used with large messages.
|Rational Test Control Panel will no longer allow a user to remove a disconnected agent if that agent had been running stubs in a locked environment.
|Non-admin users can now save new results database definitions in Rational Test Control Panel.
|If a user configures a stub to pass-through the message back to itself, then the stub execution will now stop with an appropriate error message.
|The Schema Library 'reload' button now refreshes the currently selected schema. Previously, users had to navigate to a different schema type and back again to see the changes.
|A defect has been fixed that meant if a stub had both a default pass-through configured, and an explicit pass-through action was executed, then the default could also be executed.
|The ByteArray Field Expander now correctly deals with new line characters in entered (or pasted text). Previously, they were converted to nulls.
|A defect that could cause exceptions to occur when Rational Integration Tester processed a Copybook containing binary types has been fixed.
|A defect has been fixed that meant Copybook messages containing tags did not always expand properly.
|Recording Studio now correctly recursively expands content.
|The character encoding chosen by a user for a copybook within Recording Studio is now remembered and re-used correctly.
|A defect that meant it was not possible for Rational Integration Tester to learn a new database table from the database stub editor has been resolved.
|The authentication type field on the Rational Test Control Panel Security Configuration page in the Rational Test Control Panel Installer is no longer editable.
|A problem that meant HTTP performance tests could fail due to the operating system running out of ephemeral IP ports has been resolved.
|Alias types are now correctly interpreted when a user chooses to apply a schema for a node. For example, if a type is an alias for 'String' then the appropriate string-based schemas are now offered to the user.
|The dbQuery(), replaceTags(), textFileContent() and lookupTestData() functions can now be passed as a second argument to the round() function.
|The MQ JAR files in Library Manager were incorrectly referencing com.ibm.mq.deafultconfig.jar which is not part of the client-side MQ installation. This dependency was not used and has been removed.
|The stopScenario ant task example provided with Rational Test Control Panel (for stopping a scenario of stubs on Rational Test Control Panel) now works correctly. Previously it failed with error : "stopScenario doesn't support the "name" attribute".
|A defect has been fixed that meant a messaging action's technical description was not being correctly updated when Overwrite Expected Message was used within the Message Difference Window.
|A problem has been fixed that meant if an unknown tag had been added to the rules cache URI field in the project settings, then the project couldn't be opened again. Rational Integration Tester now logs a warning and reverts to the default base URI.
|Font style changes (i.e. re-coloring of the tag's name) now occur immediately as the tag's name is typed into tag-aware text fields.
|A problem has been fixed that meant stubs started from Rational Test Control Panel would wait no longer than 4,000ms (4 seconds) before replying, regardless of the setting the user had configured. Stubs will now correctly honor response delays of greater than 4,000ms.
|In previous versions of Rational Test Control Panel, if no security model was selected (i.e. no requirement for users to login), then some administrative tasks would fail. This has been resolved; under this security model, all users are administrators and can perform all tasks.
|Record Layout editors no longer open in the dirty state. The save icon will now not be enabled until a change is made.
|A defect that meant an exception would occur if a stub attempted to send an HTTP reply with a binary payload has been fixed.
|The installation script used to install the Rational Integration Tester JDBC driver into IBM Websphere Application Server (WAS) did not work on WAS 6.1. This problem has been resolved.
|In the 8.0.1 release of Rational Integration Tester, dragging and dropping a folder of XSDs into Schema Library would attempt to import them as DFDL schemas. This incorrect behavior has been fixed and they now import as XSDs.
|A defect that meant Rational Integration Tester would only attempt to import the first item found in a PFX file has been resolved. Note that the Oracle and IBM JVMs return a different 'first' item, so customers might have experienced this defect as getting a different item from the PFX file when upgrading from Rational Integration Tester 5.x to Rational Integration Tester 8.x.
|A defect has been fixed that meant an exception would occur in test execution when an Action Group was used to run subscribe actions in parallel and more than one of the actions time-out. This behavior was not seen if no, or exactly one, time-out occurred.
|The Save icon in the toolbar is now correctly disabled after the user says no to saving changes in schema library (and the changes are reverted)
|Rational Integration Tester no longer outputs repeated log file entries stating: "com.ibm.rational.rit.CTGRequestIntercept interceptOpen, SEVERE: CTGRequestIntercept encountered exception during gateway opening when problems occur connecting to the CICS Transaction Gateway." The error is now only logged once per connection attempt.
|A defect has been resolved that meant stubs could not be saved if they contained Base64 byte arrays (with no schema applied).
|A defect has been fixed that meant tests using (empty) Base64 encoded messages would fail when the Run From Memory project setting was selected.
|JVM options -Djava.net.preferIPv4Stack=true and -Djava.net.preferIPv6Address=false have been added to the default Rational Test Control Panel start-up scripts to avoid IPv4/6 port-clash problems that could sometimes occur when Rational Test Control Panel and an agent were run on the same machine.
|An issue that meant the z/OS MQ exit could sometimes abend on start-up has been resolved.
|A fix has been made for an issue that meant it was possible for a user to get a message editor into a state where they can't OK the editor.
|Library Manager has been changed to log output by default. This is to assist in error-diagnosis during installation and initial configuration.
|A defect that meant some Unicode character sets were not rendered correctly in the message editor has been fixed.
|It is not possible to configure LDAP/AD authentication within Rational Test Control Panel so that users and groups can be searched for under different root nodes. A 'User Search Root' field has been added to both the Active Directory and LDAP configuration pages in the Rational Test Control Panel installer. To preserve existing functionality, if this field is left blank, the existing search root value (renamed to 'group search root') will be used for both users and groups.
|When tests are created from CICS Transaction Gateway recordings, Rational Integration Tester will now correctly use the commarea length and the TPN from the messages.
|The MDW console now correctly shows a "filtering disabled" message instead of a "validation disabled" message when disabling filters.
|A defect that meant integration tests created using the Recording Studio Save wizard would have disabled subscribe actions has been resolved. The subscribe actions are now enabled by default.
|A change was introduced to the Software AG wmIS components in release 8.0.1 that had the unintended consequence that recording and stubbing no longer worked against wmIS version 6. This was because wmIS 6 uses an earlier version of Java. The implementation of the server components has been modified in release 22.214.171.124 to try and avoid this problem.
|A race condition between Rational Test Control Panel and Rational Integration Tester meant that, in some cases, recorded events would not show in Recording Studio even though it appeared to have started recording and the message was successfully picked up by the proxies. This was particularly likely when recording FIX traffic as if the initial session-establishment messages were missed by Rational Integration Tester then no further messages would be shown. This problem has been resolved by enabling Rational Integration Tester to store up messages it receives before it is ready. This will then be processed rather than being lost. This means that there might still be a delay between Recording Studio appearing to be ready to record and events actually appearing (of up to ten seconds). However, events captured during that time will then be displayed.
|Date Released
20 November 2012
|Rational Integration Tester component
|In previous releases, if an agent registered with Rational Test Control Panel was stopped and then started again in a short space of time then two agents would appear in Rational Test Control Panel. It was not clear to the user which was the running one. This has been changed so that Rational Test Control Panel now recognizes a re-started agent and only shows the one, preventing confusion.
|Generating an ANT script from within Rational Integration Tester no longer outputs (irrelevant) error messages to the console during successful processing.
|Clicking Ok in the Trigger properties dialog box is now consistent with the other editors, in that re-running the trigger with the dialog box still open will pick up the changes.
|Irrelevant Tibco-related exception logs are no longer shown in the Agent console output when running a performance test that is not Tibco-related.
|Rational Test Control Panel hover-text help for stub-deployment errors is now displayed if the user is running Firefox 10.
|Operation stub filters are now included in HTTP routing rules.
|When the last project is removed from a Rational Test Control Panel environment the environment itself is now automatically removed.
|Fixing validation issues from the Tester console (for a stub) now works even if the stub editor is open. Previously if the editor was open the 'fix' would be lost when the stub editor was closed.
|The Create/Edit Test Data Set test action and wizard are now named consistently. The action's icon has also changed.
|The Edit Environments dialog box's default height is now limited to avoid it being too high for the user's display.
|The formatting tab of the Field editor has been re-worked to improve usability.
|Changes have been made to the http transport to try and ensure http messages appear in recording studio in the correct order.
|The SQL Query action no longer allows non-database transports to be selected as the Database Server.
|In the Agent list within Rational Test Control Panel the type of an agent is now displayed (Rational Test Virtualization Server, Rational Performance Test Server, Probe). This allows a user to understand what the agent is licensed to do.
|The Create Test From MEP wizard will now prompt for an environment (if none was previously selected) before attempting to execute the generated tests.
|On Windows, the Start menu contains new Start/Stop icons and a link to the login page when Rational Test Control Panel has been installed.
|Upgrading a Rational Test Control Panel instance now preserves all settings and logs. However, please note that as per the known issues section it is not possible to upgrade Rational Test Control Panel on Windows if it was installed a service.
|Rational Test Control Panel URLs have been changed from using the pipe character to using the forward slash in order to improve browser compatibility and readability.
|If tag was inserted into an ECMAScript function using the right-click tag-menu then the tag would have %% around it. This is not required for using tags in ECMAScript and would cause the function to fail. The tags[tagname] notation is now used. Although in many cases just tagname would be sufficient the explicit form ensures failures will not occur if the tagname matches an ECMAScript reserved word or existing variable.
|In previous Rational Integration Tester releases a blank page was displayed during the installation process on 32-bit Solaris. This has been fixed.
|The JSON boolean field editor claimed to accept a value of "1" as "true" and "0" as false. The only valid Boolean values in JSON are "true" and "false", so attempting to use 1 and 0 would not give the behavior expected. The text has been changed to make this clearer.
|A problem that could lead to failures occurring when parsing JSON arrays has been resolved.
|Null handling in the JSON schema has been improved. Fields of type long, double and Boolean can now contain null values, the string type works correctly with null values and when data-driving it is possible to map tests-data-set 'nulls' to JSON nulls.
|It is now possible to use tags in message editors for all JSON field types, not just string.
|The REST schema icon has been changed to avoid confusion with the JSON schema icon.
|On Solaris, Library Manager no longer outputs java.lang.UnsatisfiedLinkError exceptions to the console if pcap was not installed.
|A number of fixes have been made to resolve memory leaks.
|A problem has been resolved that could cause valid FIX Messages created from recorded messages (using Recording Studio) to show red-crosses in messages editors.
|On Windows, uninstalling a component that was running as service (e.g. the Rational Integration Tester Agent) will now correctly stop the service first.
|Users have experienced difficulty in configuring the Rational Integration Tester Agent so that it logs errors to a file. Additionally, in earlier releases not all information would be sent to a log file. Some important information was only output to the console window which could not be seen if the Agent was running as a service on Windows. A default Agent installation will now log to the .rit8 directory for the Agent. This is controlled by settings in the Agent.properties file.
|The Recording Studio New Trigger Wizard now enables the Next/Previous buttons at the correct time.
|Changing the "Continue on Fail" checkbox in the Suite Scenario Editor now correctly marks the scenario as 'dirty' meaning that the user will be able to save it.
|In earlier release, when deleting nodes using the Field editor a user is warned about removing an XML node even if the content was not XML. This has been resolved.
|A more readable error message is now displayed to the user if they attempt to open a test data file (from within the Tests Data Set editor) that does not exist.
|Running an empty test or stub now report different messages. Previously both stated "The test contained no test actions"
|Changes have been made to the Linux installation to solve some specific cases where Library Manager would not run because pcap could not be loaded.
|The SSH setting dialog box will now revert changes made if you choose Cancel after testing the settings.
|A defect that could cause the WS-Security Editor Up/Down Buttons to behave erratically has been resolved.
|ANT scripts generated from within Rational Integration Tester now include the HTTP bindings (and other settings) from Library Manager as -D arguments which ensures the Tester instance they start operates as expected.
|The HTTP/TCP Proxy registration file has been modified to provide additional information about the meaning of the forward element.
|When a stub is stopped (cancelled) from within Rational Integration Tester it no longer reports an error message on the cancel, nor ticks up the usage count by 1.
|It is no longer possible to set a logical component's parent as itself in the Logical View of Architecture School.
|The Logical View within Architecture School no longer allows an operation to have a dependency on itself.
|Messaging actions within Test Templates now contain the Linked Requirement UI controls. Previously it was possible to link a requirement to a Test Template (by dragging the requirement on top of the Test Template) but it was then impossible to alter those links from within the test actions.
|It is now possible to delete dependencies from within Architecture School's Logical View. Previously the component's properties dialog box had to be used to achieve this.
|Various usability issues have been addressed during a Rational Test Control Panel installation when a previous workspace already exists.
|On non-Windows platforms the full path to the Rational Integration Tester Agent no longer needs to be provided in the Agent.config file. In previous releases the
|An error that could cause an exception stating that a string cannot be cast to A3 type while running a webMethods test has been resolved.
|Changes have been made to the multiple Save buttons on Notes tab in Results Gallery to avoid user confusion.
|During installation the Rational Test Control Panel Security Configuration panel now correctly remembers the chosen authentication type if the user goes back to it after passing through it.
|In previous versions it was possible for a non-administrator user to issue a command against Rational Test Control Panel (using a browser) that would execute an admin-level function. The user would need to know the format of the request to make. This is no longer possible.
|Pasting WSDL file paths into Logical View that have quotes around them and that are within the project structure now generate correct paths within Tester. Previously a trailing quote would be left at the end of the path.
|A number of errors could occur when pasting XML content into the SOAP header editor have been resolved. Cancel now works correctly if a user backs out of the editor.
|A problem that meant importing a .p12 certificate into Rational Integration Tester failed after entering a (correct) password has been resolved.
|Due to a change in behavior of a UI control in Java 7 the field viewer in Recording Studio did not automatically add a horizontal scroll bar. This made it impossible to see very wide data. Tester will now automatically turn on word-wrap if it notices the longest string is wider than the dialog box.
|In previous releases Rational Integration Tester would fail to start-up if Library Manager hadn't already created the .rit8 directory (or there was an existing .ghTester5 directory for Rational Integration Tester to migrate from). Rational Integration Tester will now automatically create the .rit8 directory itself if it is not present.
|Changes have been made to the way that Overwrite Expected Message operates to avoid multi-threading issues resulting in Tester appearing to 'hang'. Repair operations that were previously being handled asynchronously are now performed synchronously.
|URLs copied from Internet Explorer using the "Copy Shortcut" menu item can now be correctly pasted into Tester.
|JBDC recording and stubbing has been modified to try and work more reliably in cases where localhost is being used as the database hostname.
|A number of fixes have been made to editors to ensure they correctly notice when fields are changed and enable saving.
|Default configurations applied to message actions (e.g. transport) are now saved correctly and allow a test to be run immediately. Previously the user had to change a field in the editor in order for the defaults to be used within a test.
|Custom FIX messages now contain the correct message type when they are published.
|Tester can now import WSDL files containing empty
|Adding an operation to a service component in Logical View no longer automatically expands all other service components.
|The Agents view in Rational Test Control Panel now shows HTTP and HTTP(S) routing and recording rules separately.
|A scroll bar has been added to the suite selection view in Rational Test Control Panel.
|A defect has been fixed which could result in the Recording Studio Save Wizard failing to complete if the user chose "Add Trigger to menu" option and clicked Finish.
|If a Test Suite Scenario was configured the "Allow tests to continue even if step fails" option then this flag was being incorrectly passed into stubs run within Rational Integration Tester defined in the scenario. This could lead to confusing pass/fail results being reported to the user. This was capability is only intended for use in Tests and the issue has been resolved by ensuring that stubs do not use this setting.
|If a Results Publisher was configured to use a Custom JUnit report then an error would occur when a suite using this published was run stating "JUnit Report.xsl was not found. This has been resolved.
|The Agent.config file contained formatting that made it difficult to read using Notepad on Windows. This has been resolved.
|The HTTP/TCP proxy registration.xml no longer contains Unix newlines characters when installed on Windows.
|The stub editor no longer requires a user to press Enter after changing field values in the output tab before saving.
|It is now possible to round-robin route messages to http based stubs. This behavior requires either multiple copies of the same stub to be started via Rational Test Control Panel, or a stub started in Rational Test Virtualization Server and Rational Integration Tester where the Rational Integration Tester project is registered against the same Rational Test Control Panel instance (including domain/environment) that was used to start the Rational Test Virtualization Server-based stub.
|In Logical View, deleting the last child from a container node now reverts the node to a normal node, rather than leaving it as an empty contained.
|A problem has been resolved that meant Pending Database Writes were not reported correctly when running a performance test. The 'heartbeat' message on the Rational Integration Tester console would always report zero pending writes regardless of the actual number. This made it difficult for users to realize that the bottleneck in running the test was the writes to the results database. The correct value is now reported. Tester uses a queue to write performance data to the results database so that the write does not immediately block the generation of load. However, if load is being generated faster than it can be written then the queue depth will increase. The pending database writes value shows the length of this queue. When it gets to a certain size then load generation will slow down. Increasing/high pending values indicate that the database being used to capture results is not fast enough to keep up with the load generation.
|Date Released
05 November 2012
|Rational Integration Tester component
|The HP Quality Center Change Management integration to allow defects to be raised in QC from Rational Integration Tester has been updated to provide improved compatibility across QC9.2 - QC11 including fixpacks. Please note that this integration can only be used from the Windows 32-bit version of Rational Integration Tester. This is because HP only supply 32 bit integration DLLs which a 64 bit installation of Rational Integration Tester cannot use.
|The WSDL Operation parameterOrder attribute no longer causes an error during WSDL synchronization.
|A problem that could result in the MIME node formatter constructing corrupt payloads has been resolved.
|Tag values used within MQ filters are now honored correctly
|Stubs no longer suppress compilation errors occurring within their message cases.
|A preference has been added to limit the number of optional fields from the schema definition that will be created during wizard processes to prevent memory issues with very large schemas.
|When a Java Object schema contains a java.util.Collection field Tester will use a java.util.ArrayList as the implementation when building an Object instance to prevent errors.
|SOAP Headers now show correctly in the Field Properties editor. The editor now allows arbitrary SOAP Headers and attributes to be created.
|Minor documentation updates to: Rational Integration Tester Reference Guide, Rational Integration Tester Integration Guide for HP Quality Center, Rational Integration Tester Reference Guide for Java Objects and Rational Integration Tester Platform Pack Installation Guide.
|Date Released
04 September 2012
|Rational Integration Tester component
|A problem that meant an error could occur when an HTTP based stub received a GET (as opposed to a POST) has been resolved.
|HTTPS recording and virtualization is now supported where the server requires a client-certificate to be presented for authentication. HTTPS recording and virtualization is also now supported where the client uses HTTP which much be converted to an HTTPS connection in order to establish a connection to the server.
|Tester now supports schema mapping where children can have the same name but different types. Comments in XSD elements are also now allowed.
|Virtualization and Performance Reference Guides are now included in an installation of Rational Integration Tester.
|A problem has been fixed that meant recording of HTTPS traffic could stop if a client dropped a connection.
|When configuring a stub to use SSL users are now informed if the settings are invalid due to a list of trusted CAs not having been specified.
|HTTPS recording now supports protocols other than SSLv3.
|A problem that could cause EBCDIC new line characters from being corrupted within the bytes formatter has been resolved.
|Promoted byte[] fields are now displayed correctly in Recording Studio.
|A problem that resulted in blank data model mapping panels being shown in the Recording Studio Save wizard has been resolved.
|Single-Sign-On between Rational Integration Tester and Microsoft Windows Active Directory now works correctly. This means that secured projects run from the command line or from HO Quality Centre can now be opened.
|If an assert action within a failure path is inside an iterator then if the assertion failed once then all subsequent iterations would follow the failure path regardless of whether the assertion passed or failed. The failure path within the iterator is now only executed if the assertion itself fails.
|It is now clearer how to configure Rational Integration Tester to use JMS over MQ if WebSphere Application Server 6 (WAS) JDNI is being used. Previously users had to add entries into Library Manager manually. There is now a new provider section to the "IBM WebSphere Application Server" section of Library Manager to allow configuring of the WAS jar files needed to access WAS JNDI. This is called: "IBM WebSphere Application Server 6.0 (JNDI access)" and allows the 4 jar files required to enable WAS JDNI lookup to be configured. Customers upgrading from 5.x version of GH Tester to Rational Integration Tester will need to reconfigure Library Manager to set-up MQ/JMS jars.
|In certain cases, when using the Message Difference Window with messages containing repeating elements erroneous additional fields could be added to the expected message of the tests. This problem has been resolved.
|Schemas can now be be resolved in TIBCO BusinessWorks DesignTime libraries.
|It is now possible to select a specific agent when scheduling a test to run via the Rational Test Control Panel.
|The security configuration dialog box no longer appears during a silent installation of Rational Test Control Panel.
|When the Installation Manager is used to install Rational Integration Tester or Agent and the user selects to run the Library Manager at the end of the installation then Library Manager will now run correctly even if Installation Manager is still running.
|If an unknown content type is encountered when processing an MQ message it is now shown as such to the user and can be republished.
|A fix has been made to correct a problem that meant, in some circumstances, messages based on record layout schemas would show red crosses in the message editor.
|Some user experienced problems that meant Log Values from Performance Testing were not shown in a chart's counter tree even though they are present in the database. Changes have been made to the product to try and avoid this problem from occurring.
|To prevent Rational Test Control Panel's dashboard from becoming stuck in the "deploying" state, improvements have been made to how Rational Test Control Panel detects errors when agents and stubs are starting.
|The End Timed Section action editor now correctly triggers the dirty flag meaning that a user can save the action.
|Receive Reply Defaults are now saved correctly when a default (non-modified) message is saved.
|Automatically adjust IDoc recording/subscribe date-time values to the server timezone. Note that the IDoc query ABAP interface has changed to support this feature. It will therefore be necessary for existing users of Rational Integration Tester's SAP support to update to the new ABAP source, and create the new interface structure: ZRGTITS_SEL_UPDTIMSTMP. Source files for both these actions, as well as the other dependent structures, can be found under /tools/SAP along with installation instructions.
|The MQ Transport no longer requires access to the command queue for simple put/get messaging operations. Command queue access is only required for recording where PCF messages need to be sent (for Queue Alias, MirrorQ and Record-the-transport recording techniques).
|A fix has been made to ensure that the database stub editor does not show duplicated queries.
|Cancelling an Iterate action now longer finishes and fails a test (but correctly marks it as cancelled).
|Date Released
11 July 2012
|Rational Integration Tester component
|Publishing SOAP messages using WS-Security headers now works correctly.
|A problem that could cause Rational Integration Tester to freeze when adding an environment has been fixed.
|Fixes have been made to delimiter handling when parsing and formatting Fedwire messages to prevent the publishing of invalid transfer messages.
|The Function action now uses multi-line technical description.
|A fix has been made to ensure that subscribe actions using the Fedwire and CHIPS field expanders validate correctly.
|An XML schema can now be applied to an xsd: any element. This provides support for XML fragments within xsd:any typed elements.
|Improvements have been made to Recording Studio's memory management and it now releases cleared-out events from memory more quickly.
|Correlation IDs are now preserved when messages are exported from Recording Studio and then reimported.
|The "Open" button on the Data Source (file) editor now opens the file specified in the dialog box text box instead of the file name with which the resource was last saved.
|When a new schema is added to the Schema Library it is now opened automatically. If multiple schemas are dragged into the Schema Library, the last one in the set will be opened.
|A registered agent is now displayed on Rational Test Control Panel's Agents page even if no domains have been configured.
|To prevent Rational Test Control Panel's dashboard from becoming stuck in the "deploying" state, improvements have been made to how Rational Test Control Panel detects errors when agents and stubs are starting.
|Rational Test Control Panel's domain selection page now displays a "Loading" dialog box.
|Changing the ordering of tests within a suite now triggers the "dirty" state, which enables the suite to be saved.
|Improvements have been made to the breadcrumb consistency when searching and viewing results on the Rational Test Control Panel's Results page.
|When editing data from a database stub in an external editor, it is now possible to add a column (by specifying column name in the spreadsheet) when the underlying database is Oracle.
|JDBC Recording has beenfixed to ensure that SQL can still be recorded when Stored Procedure parameters are in use.
|The FIX Transport configuration screen now allows "TargetSubID", "TargetLocationID", "SenderSubID", and "SenderLocationID" to be set.
|"Create Test from MEP" now works correctly when using Operations created from TIBCO BusinessWorks synchronization.
|FIX Message groups within groups are now correctly identified.
|There is now enhanced support for Microsoft SQL Server data types within JDBC Virtualization. There is also support for the following SQL Server specific types: unique identifier columns, date and time, character and binary strings, numerics and row version.
|Added functionality to allow the creation of requirements messages derived from an Operation's MEP type.
|Added check for 'null' string as correlation ID when grouping events in Recording Studio Save Wizard.
|Fixed memory usage indicator defect.
|Fixed a number of JDBC virtualization issues : incorrect upper-casing of MS SQL Server table and column names; display of NULL parameters on SQL calls in recording studio; injection of NULL values into the simulation database during learn processing.
|Fixed red-cross issue when copy and pasting within a message structure.
|Using the Run Command action with a command spanning multiple lines now runs correctly on Unix. Previously the command had to be on a single line. This problem did not exist when running under Windows.
|The File Comparison action now provided additional information when result truncation occurs. The lower limit at which result truncation occurs has also been increased.
|New Message Actions now correctly copy Transport fields from their Operation.
|A problem that could occasionally cause a Concurrent Execution Exception when attempting to open the Message Differencing Window has been fixed
|The wording shown when linking Requirements has been clarified.
|The banner text for Requirements has been clarified.
|It is now possible to call Stored Procedures with parameters in test actions when Rational Integration Tester has been configured to use the Microsoft SQL Server JDBC Driver.
|The various components now register and display 220.127.116.11 as their version.
|A problem that meant uninstalling the Rational Integration Tester could sometimes leave the prunsrv.exe file has been fixed.
|A user must now make a 'license type' selection when installing the Rational Integration Tester Agent. This is to avoid the 'default' installation of a Performance Test Agent occurring when a user (who wants to use stubs) simply clicked Next through the installation process.
|Date Released
05 June 2012
Related information
V.R.M.F. Maintenance Stream Delivery Vehicle glossary
Software Product Compatibility Reports
Fix Central