| ID |
APAR |
Description |
| 51100 |
PI33025 |
Previously, when a Linked Requirement containing a WebSphere MQ message was dragged into the Test Tree, then, in some circumstances, all fields were incorrectly cleared. This problem has been fixed. |
| 51074 |
PI32902 |
Prior to version 8.5.1, Rational Integration Tester performed XML namespace identifier (Qname) validation by comparing the values as strings. This meant that elements with different namespace names (that resolved to the same URL) would fail comparison when, logically, they were the same. For example, <ns1:customer> was nor considered to be the same as <ns2:customer> when comparing expected and actual messages, even if the definitions of ns1 and ns2 resolved to the same URL.
In release 8.5.1, this was changed so that comparison was done using the resolved namespace names.
However, for some customers, this change introduced a problem in XML documents where the namespaces were not defined. In this case, Rational Integration Tester could not resolve the namespace identifier, and validation failed regardless of the string equivalence of the names. These users saw this as an undesired change in behavior.
Rational Integration Tester now falls back to string comparison if the namespace identifier cannot be resolved for the XML messages. This preserves pre-8.5.1 behavior in these cases while still providing correct validation when the namespace is defined.
|
| 51034 |
PI32784 |
Previously, Library Manager showed MS SQL Server versions 6.5, 7, 2000, and 2005 only. Version numbers were removed to avoid confusion as to which versions are supported. Use online information to determine the correct supported versions for Rational Integration Tester. |
| 50833 |
PI32267 |
Users are no longer permitted to create environments whose names differ only in case. A warning is displayed if such a duplicate name is entered. When publishing stubs to Rational Test Control Panel, environment name comparison is now also performed in a case-insensitive manner. |
| 50778 |
PI31985 |
Previously, the WebSphere MQ transport allowed only a fixed and limited list of possible cipher suites. This control was changed so that the user can enter a free form name for a cipher suite. |
| 50774 |
PI31970 |
Previously, the user interface did not indicate which set of Result Publisher Settings was the default for a particular Result Publisher. The default settings are now displayed in bold, and "(Default)" is appended to the displayed technical description. |
| 50773 |
PI31969 |
Previously, "Project Settings > Results Publishers" showed a check box to indicate which publisher, if any, was the default. This display was confusing because the value for the check box could not be changed in the project settings. The check box has been replaced with a "Yes" or "No" text field. |
| 50740 |
PI32431 |
Previously, two problems were observed when working with the results of an SQL Query action. 1) The Merge button was not always displayed when it should have been. 2) Rational Integration Tester could hang while attempting to merge results. Both problems have been resolved. |
| 50680 |
PI31722 |
Previously, optional fields in DFDL schemas were set to null by default, which could prevent the user from opening the root of a message. Optional fields in DFDL schemas now default to empty, which resolves the problem. |
| 50499 |
PI31302 |
Previously, the Store page of the Field Editor dialog box did not permit tagging for non-text XML fields such as decimal or dateTime. If the user attempted to tag these fields, the tag action was removed. The problem has been corrected. |
| 50204 |
PI31177 |
When a WebSphere MQ-based operation did not have the Stub page configured (meaning that the Stub page was not bound to a transport) then any attempt to create a WebSphere MQ sift and pass-through stub for a remote queue failed. Default values have now been put in place to resolve this problem. |
| 49684 |
PI29430 |
Previously, when recording remote queues using the MQ exit for z/OS, the wrong queue name was shown in Recording Studio when recording the whole transport. The queue name shown in Recording Studio was taken from the queue definition rather than the name of the queue to which the message was actually being sent. This problem has been corrected. |
| 49284 |
PI28541 |
Previously, values for the "Field is optional" and "Ignore rule cache" fields in a message were incorrectly cleared when an XML parent node was opened and closed in the message editor. The problem has been fixed. |
| 49280 |
PI28521 |
Previously, a stub that was created or modified in the Test Editor did not recognize any timeout as valid, resulting in an error condition when the stub was run. The problem has been fixed, and legitimate timeout values are now recognized. |
| 49065 |
PI34040 |
In previous versions of Rational Integration Tester, the CICS DPL Agent could cause an S0C4 ABEND when used in the IBM Rational Development and Test Environment for System z. This problem has been corrected. |
| 49044 |
PI27205 |
Previously, if a user attempted to configure a Results Database URL in Rational Test Control Panel that was longer than 255 characters, then it would be rejected. This has been corrected and results database URLs of up to 512 characters are now permitted. |
| 48928 |
PI27528 |
When modifying XML elements, optional field settings are now preserved where possible. |
| 48871 |
PI28732 |
Some customers experienced time-out errors when running tests from HP's Quality Center product by using the "Running Tester Instance Execution" method and alternating between Rational Integration Tester projects. This problem has been resolved. |
| 48784 |
PI27095 |
The Rational Integration Tester database creation script failed when used with DB2 version 9.5. A new script, specific for DB2 9.5, has been created. This script is named ghtester_db2_9.5.sql and is found in the scripts directory under the Rational Integration Tester installation directory, along with the other database scripts. |
| 48637 |
PI26795 |
Previously, the Test Connection option did not work correctly against EMS version 8.0. This problem has been resolved. |
| 48604 |
PI26776 |
Previously, it was possible to create multiple users in the same domain in Rational Test Control Panel whose names varied only in case. This problem created conflicts in Domain Level Security. The problem has been corrected, and case is now handled consistently in the domains. |
| 48391 |
PI26031 |
Previously, if individual tests were missing from a test suite (that is, the tests had been deleted after they were added to the suite), then when the suite was run, no errors or warnings were displayed. This could leave the user unaware that the tests the suite had run might not match expectations. The problem has been corrected, and a suite with missing (deleted) tests now fails, with a message about the missing tests displayed on the console. |
| 48361 |
PI26083 |
Previously, due to a limitation in the .xls Microsoft Excel file format, the maximum number of columns in an Excel data set supported by Rational Integration Tester was 255. Now, if the number of columns exceeds 255, Rational Integration Tester creates a file with an xlsx extension, which can support up to 16384 columns of data. |
| 47851 |
PI24704 |
Previously, Rational Integration Tester could not connect to an HTTP server that used Windows NT LAN Manager version 2 authentication (NTLMv2). Attempts to connect received a 401 error. In Rational Integration Tester 8.7, version 4 of the Apache HTTP client is enabled automatically, meaning that NTLMv2 authentication is no longer a problem. |
| 47656 |
PI31194 |
A typographical error was found in the dialog box for importing saved events from a file. Previously the message read:
Remove existing mointors and events
This message has been corrected to read:
Remove existing monitors and events
|
| 47440 |
PI23347 |
Previously, when the user stopped Rational Test Control Panel at the same time that tests continued to use a stub that was started in Rational Integration Tester, the stub failed to respond to new requests from Rational Integration Tester. This problem has been corrected. |
| 46974 |
PI21880 |
Previously, the "Search resource contents" feature in the Test Factory perspective returned correct results the first time it was used after a project was opened, but subsequent uses did not return any results. The problem has been corrected. |
| 46537 |
PI20586 |
When using the sift and pass-through feature with the HTTP proxy, messages that contained the HTTP header "Content-Encoding=gzip" were not understood by the live system because the contents of the message had already been uncompressed. This problem has been resolved and the message passed to the live system now contains compressed content. |
| 46242 |
PI19778 |
When clicking "Test Transport" on an HTTP transport within Rational Integration Tester, the results of using the transport in a client capacity and a server capacity are both displayed. Previously, if an error occurred in testing the transport as a client, information regarding the status of using the transport as a server might not have been displayed. This problem has been corrected. |
| 46041 |
PI18925 |
Previously, if the user opened a messaging test action such as Publish or Subscribe, but did not have the required library files in Library Manager, no error message was displayed to indicate that the action was unable to complete. This problem has been corrected, and an error message is now displayed. |
| 45469 |
PI16937 |
Previously, after synchronizing with a TIBCO BusinessWorks (BW) project, some of the private processes might not have message definitions. The problem has been corrected and the appropriate schema is now correctly applied. |
| 44852 |
PI14932 |
When recording SQL statements by using the Rational Integration Tester JDBC driver in "learn" mode, a user can now see a "Report" field in Recording Studio that shows which tables, rows, and stored procedures were learned or affected by each statement. This feature is accessed by selecting an SQL Event in Recording Studio. The detail panel under the event rows shows the SQL parameters and the new "Report" field. This feature enables a user to see if the driver has been able to learn anything with each statement. |
| 43322 |
PI11352 |
Previously, it was not clear what the "Is stored procedure?" check box on the SQLQuery and SQLCommand actions did. Hover text was added to clarify the purpose of the check box. |
| 39116 |
PM95961 |
Previously, it was too easy to delete a test by mistake. The "confirm delete" dialog box now has "no" selected by default. |
| 38375 |
PM93719 |
Previously, it was possible to use a floating point number in an XML integer field. Rounding could then cause the test to fail. Validation now provides a warning message if the user attempts to enter a floating point number in an integer field. |
| 36643 |
PI27486 |
Previously, if the user changed the proxy settings after running a test (for example, on the HTTP transport), the previous connection was still in place when the test was restarted. The connection would therefore not be made as the user might expect. This problem was corrected by automatically disconnecting if neither recording nor tasks are running. A warning message is displayed before the connection is reset. |
| 51712 |
|
Previously, any upgrade of Rational Test Control Panel caused all custom elements in the server.xml file to be duplicated. Although this problem did not affect functionality, it did mean that error messages were displayed if the user changed values in the server.xml file because duplicate, conflicting values were then found (for log level, as one example). This problem has been fixed and will not occur on upgrades from version 8.7.0.0 and later. The workaround is to manually correct the file. |
| 51594 |
|
Previously, if a service component had an unusually long name, and the component was expanded in the Logical view, then the beginning of the name was sometimes obscured by the "Collapse" icon. This problem has been fixed. |
| 51483 |
|
Rational Integration Tester uses the COM.GREENHAT.COMMAND.QUEUE WebSphere MQ message queue for internal commands when the MQ Exit for System z is used. Traffic on this queue should not be recorded or stubbed. Previous versions allowed this practice, but with 8.7 it is no longer possible to record or stub the command queue. |
| 51287 |
|
Previously, when running Library Manager on Windows Server 2012, no network adapters were listed in the Default Network Device drop-down list. The problem has been corrected. |
| 51142 |
|
Some SAP systems use non-standard indicators for null fields within IDocs. A typical example is the use of a slash to represent null. Previously, if Rational Integration Tester attempted to record or subscribe to an IDoc containing such a field, then it would fail. This problem has been corrected. |
| 50736 |
|
A number of fixes were made to the WADL synchronization process.
- The MEP type was set incorrectly. It is now always set to Request/Response.
- After synchronizing with a WADL file, the URL field in the operation signature was blank. As a result, the option to create tests from the message exchange pattern (MEP) was not available. The URL is now populated.
- If the source of the WADL was a file, the component name was "WADL". It is now the file name and URL name.
- If the source was a URL, the component name incorrectly had a .wadl suffix. This suffix was removed.
- The Logical view menu did not include WADL. It now does.
|
| 50735 |
|
Previously, if the number of log entries made by a single Rational Test Control Panel instance exceeded 2,147,483,647, then the process would fail. This problem occurred only if a large number of agents were registered with Rational Test Control Panel, and the agents ran under load for many hours.
The problem was caused by the use of an integer variable for the counter. The counter was changed to a long, resolving the problem.
|
| 50629 |
|
In previous versions of Rational Integration Tester, the HTTP Bind Address field in Library Manager was ignored when starting a Rational Test Control Panel stub. This behavior was contrary to the information supplied in the help.
The rules governing how a bind address is chosen (from Topic) state:
"Note: If you do not enter a value in this field, the address specified in the HTTP Bind Address field in the Application page of Library Manager is used. If there is no address specified in the HTTP Bind Address field in Library Manager, the transport will bind to all local addresses on the computer that hosts the TCP server."
In version 8.7, Rational Integration Tester does follow these rules. One result of this change is that, if an HTTP Bind Address is specified in Library Manager, the user can no longer establish a connection using localhost.
Note that the server can be forced to bind to localhost by specifying that host name in the server panel.
|
| 50556 |
|
A problem was found with the z/OS MQ exit support for alias queues. The recorded queue name showed the base queue name rather than the alias queue name. This problem has been corrected. |
| 50535 |
|
A problem with the CSS file that the Results Gallery uses resulted in some displays being illegible on Linux. The problem has been resolved. |
| 50471 |
|
Additional logging information has been added to the Rational Test Control Panel logs to make it easier to diagnose issues of missing or invalid security tokens. |
| 50417 |
|
The transaction code that is used by the Rational Integration Tester native CICS Agent (used for CICS LINK recording and virtualization) has been changed from EXCI to RITX to avoid clashes. The JCL file used at installation time has also been modified so that customers can change that transaction code if required. The installation instructions packaged with the Agent include details on how to change the code. |
| 50395 |
|
Previously, a recorded byte array that contained non-ASCII characters failed to match an identical byte array in a schema. The byte array recognition routine has been improved to accept non-ASCII characters, which resolves the problem. |
| 50224 |
|
Previously, the Portuguese "Falha" appeared in the Results Gallery instead of "Failed". The error has been corrected. |
| 49798 |
|
Previously, if a user attempted to run a test suite, stub, or performance test in Rational Integration Tester, and the results (project) database connection string was missing or badly configured, then a warning message that included technical details of a Java class was displayed. This has been changed so that, when attempting to run a stub or a test, a warning is displayed in the console instead. For performance tests, the dialog box, minus the class name, is still displayed. |
| 49674 |
|
Previously, when recording an IPIC request, Rational Integration Tester truncated any data in the COMMAREA that followed a null character (\x00). In some cases, the truncated COMMAREA caused a copybook expansion error. This problem has been corrected, and the COMMAREA size is now based on the length specified in the message header. |
| 49221 |
|
Previously, if a user wanted to specify certain configuration options when creating a WebSphere MQ transport, then it was necessary to enter the required bitmask numbers. A button marked with an ellipsis (...) now displays a drop-down list of all appropriate options for each of these fields using the correct MQ names. |
| 48878 |
|
Previously, if a message was sent to the HTTP Proxy with a "chunked" transfer encoding and a zero-length body, then the proxy failed to send the closing chunk size, which made the message unreadable. The problem has been corrected. |
| 48850 |
|
Previously, if very large strings failed validation, Rational Integration Tester attempted to output both strings to the console window. If the strings were in the multiple megabyte size range, then this display could cause CPU usage issues, as well as flooding the console with a huge amount of text. The problem has been corrected; if the string is extremely large, then a very much shorter message is now displayed, which shows the point in the message where the validation first failed. |
| 48837 |
|
Previously, if DB2 version 9.5 or 9.7 was used as a results database, searching for test cycles on the Rational Test Control Panel Results page failed with a DB2 SQL error. This problem has been corrected. |
| 48521 |
|
Previous versions of Rational Integration Tester ignored names specified in the subjectAltName (SAN) X.509 extension when validating a certificate received from a server during an SSL handshake. Any hostnames and IP addresses present in the SAN are now used to perform the validation. If there is no SAN, the common name (CN) for the subject of the certificate is used instead. |
| 48365 |
|
When recording CICS DPL events by using the CICS native agent in Recording Studio, the timestamps were not consistently correct. This problem has been resolved. |
| 48277 |
|
In all previous versions of Rational Integration Tester, the default timeout value for all request/reply actions was zero. This meant that the action would never time out. If no reply was received, then it might appear that Rational Integration Tester had hung, whereas it was in fact simply waiting forever. To avoid this situation, the default timeout value for these actions was changed to 5000 milliseconds. Users who run tests against slow systems may need to increase this value, or change it to zero to wait forever. Note that existing tests are not affected; only new actions will pick up the change. |
| 47968 |
|
Previously, if clicking the "Test Connection" button failed, only the connection failure message from the underlying client library was displayed. Now additional information is provided, including:
- Results of a ping of the host
- Results of the Hattempt to open the port
- Host IP address, host name (if resolvable), and port number
This information helps users to diagnose problems with the connection. |
| 47785 |
|
In version 8.6 of Rational Test Control Panel, if the user attempted to start a stub without selecting a version, no error was displayed and it was not clear to the user that the stub had not started. This problem has been corrected. |
| 47743 |
|
Some field actions in messaging actions cannot operate with multi-value tags (list tags). Previously the error message in the test console was quite cryptic, making it difficult to determine the cause of the problem. The error now shown is much clearer. For example:
Multi value tags can not be used in the Value Action: {3, 3, 3} (Action = "Value")
This situation typically arises when using a Lookup Test Data action and multiple matching rows are found. In such a case, all rows are returned in a list tag.
|
| 47407 |
|
Previously, when given one or more non-numeric parameters as input, the addNumbers example service shipped with Rational Integration Tester would return an HTML error page rather than a SOAP fault. This problem has been corrected and a SOAP fault is now generated, which allows users to get a better understanding of how to deal with this type of response. |
| 47246 |
|
Previously on MQ for System z, it was possible for invalid WebSphere MQ queue names to remain in the Rational Integration Tester managed namelist when the queue manager restarted or Rational Integration Tester failed to remove the invalid names for some other reason. This problem has been corrected, and queue names in the namelist are now validated. |
| 47016 |
|
Previously, if a stub was run that used Rational Test Control Panel to set up routing rules (such as an HTTP-based stub), then ports were allocated at stub compilation time to generate routing rules. However, if the stub failed to compile for any reason, then the port was not released. If the stub was configured to use a specific port (rather than allocate one on demand), then the stub could not be started again because the port was in use. The problem has been corrected, and the port is now opened only after the stub is successfully compiled, which means that the port is now released correctly. |
| 46285 |
|
Previously, word wrap was turned off by default in the Test Lab console, which was potentially confusing to new users. Word wrap is now turned on by default in the console, as it is in the message view and message editor. This setting can be changed if preferred. |
| 45772 |
|
Previously, when creating a new operation, the Message Exchange Pattern (MEP) type defaulted to Publish, which is not the most common scenario. The MEP now defaults to an appropriate value for the transport. In most cases, this value is Request/Reply. |
| 27573 |
|
Previously, when a test was run that contained input tags, no values were requested for the tags from the user. This made testing sub-tests difficult. This problem has been resolved, and the user is now asked to enter values for the tags when the test is run. |
| 27218 |
|
Previously, the default behavior for selecting event monitors in Recording Studio was to show operations only. This behavior has been changed, so that both the operation and physical resource filters are selected, which means that all resources are shown by default. The user can then filter by one or the other if desired. |