Updated Agents

The following Agents have been modified as part of the HCL OneTest API 10.0 release. After you upgrade HCL OneTest API and HCL OneTest Virtualization you must update the agents that you use.


You can download the files from the "Tools" page of HCL Quality Server (accessed by a browser) or from the Tools subdirectory of the HCL Quality Server installation directory. In either case, note that Agents that include a registration.xml file now have the HCL Quality Server setting in that file automatically set to the hostname of the server where HCL Quality Server was installed.


The table shows the agent technology updated in this release. In the table, you can find the installation instructions to complete the upgrade. All tools are part of HCL OneTest API unless otherwise noted.



Ant: HCL Quality Server Apache Ant tasks

Installation instructions

CICS: CICS Transaction Server Agent

Installation instructions

JDBC: JDBC driver

Installation instructions

MQ: API Exit for WebSphere MQ (z/OS)

Installation instructions

List of fixes






In previous releases, attempts to start a stub on a HCL OneTest API Agent installed on AIX and configured to use agent-mode licensing failed. This problem was fixed. 



Previously, in some circumstances, EDIFACT messages were corrupted when published such that colon separators become plus signs. This problem was fixed.



Previously, you could not stop an engine process for virtual services from the new dashboard. This problem was fixed.



HCL OneTest API 9.2 introduced new code to clean up stale stub intercept rules. In some circumstances this could lead to an exception when creating connections to a Queue Manager. This problem was fixed. 



Previously, HCL OneTest API failed to recognize or expand WebForm content containing lowercase percent encoded octets. This problem was fixed.



When synchronizing WS-Policy WSDL definitions, RuntimeExceptions will not occur when the definition contains PolicyReferences in the WS-Policy declaration.



In the message editor, when dealing with HTTP based messages, toggling the Message Type between Byte Array and Text no longer corrupts the message structure.



Previously, when subscribing to files within an iterate action, HCL OneTest API would not release all threads used for consuming the file, potentially causing an OutOfMemory exception. This problem was fixed.



Previously, some foreign product translations included a double quote (“) character instead of a single quote (‘) character. For example Studio d”enregistrement instead of Studio d’enregistrement. This problem was fixed.



The Rational Quality Manager Adapter was changed to continue to send log messages after pausing when Rational Quality Manager is busy.



Previously, when building a message by using an XML Schema, the HCL OneTest API message editor would not allow more than one child to be added to a node representing a repeating XSD sequence with a single element child. This problem was fixed.



If the project database is restarted, HCL Quality Server cannot reconnect and Results queries fail with the following error: 

“An error occurred whilst fetching executions for suite (No more data to read from socket).” 

This problem was fixed. 



When using an onward proxy in the HTTP/TCP proxy, if the onward proxy fails to handle the request, the error is not passed back to the client and the client connection is dropped. This problem was fixed.



Row count validation errors no longer occur when appending to list tag values within an SQL Query action when cell assertions are disabled.



An HTTP request with a URI containing non-standard characters (for example, '<' and '>') can now be handled by the HTTP proxy.



If HCL Quality Server is stopped and started while HTTP stubs are running on an Agent, duplicate routing rules can be incorrectly created in HCL Quality Server every 30 seconds. This problem was fixed.


In some cases, non-ASCII characters in an environment name prevented HCL Quality Server from displaying the assets published to that environment. This problem was fixed.


Previously, the Rational Quality Manager adapter batched messages together to reduce the rate at which messages were sent to Rational Quality Manager when executing a test. However Rational Quality Manager imposes a maximum message length of 250 characters which was being exceeded. This problem was fixed.


When multiple IMS monitors record the same message, the reply message is now properly recorded for all monitors.


When starting an application with the JDBC driver configured, the application can hang if a connection to HCL Quality Server cannot be established. This problem was fixed.


A MySQL constraint violation exception no longer occurs when you delete results from the Results Gallery.


The previous MySQL Connector/J driver class was deprecated (com.mysql.jdbc.Driver) and the new driver class added (com.mysql.cj.jdbc.Driver). This requires the latest MySQL Connector/J version when using MySQL as the results database. The deprecated driver can still be used with MySQL physical component connections.


Previously, the HCL Quality Server Infrastructure dashboard under the Engines tab did not show the correct values for the Log Directory, Project Location and Process ID following a restart of the server. This problem was fixed.


Recording and routing rules were changed to be consistent irrespective of whether their host resolves to a loopback address. This might in general make matches occur more frequently, but is unlikely to cause regressions since loopback is rarely used in production.


In some situations the Delete Results dialog box could display with some of its contents obscured. This problem was fixed.


Previously, using HCL OneTest API with the IBM JRE , Git integration failed when connecting to a remote peer using HTTPS. This problem was fixed with the move to using OpenJDK™ 8 with OpenJ9.


When results are deleted by using the Results Gallery or the command line, the following exception no longer occurs: "Unknown column 'execution_id' in 'field list'"


Previously, the Agent name was truncated on the HCL Quality Server Infrastructure dashboard and Network dashboard with no way of viewing the full name. This problem was fixed.


Operations created from recorded Type-1 IMS Connect events now contain the proper message type in the headers on the MEP and Stub tabs.


The jTDS JDBC driver version was updated in Library Manager from 1.2 to 1.3 due to a defect discovered with database virtualization.


MongoDB physical view descriptions are no longer incorrect when only the default values are used.


Previously, the MQ message type was not set correctly by the IBM WebSphere MQ exit for z/OS. This problem was resolved.


When renaming a resource such as a test whose name contains a '.' character, the name shown in the dialog is truncated. This problem was fixed.


Previously, the IntegrationTesterCmd failed to detect when the value of an option was blank. This problem was fixed.


When setting headers in the Email transport physical resource, the values configured are not saved. This problem was fixed.


In previous releases, in some circumstances updating how a reference should be resolved in a Test Suite Scenario could result in an invalid Data Drive configuration. This problem was fixed.


Previously in HCL OneTest API, when validating an XML message by using the Schema validation action, a schema taken from the XML document would always be included even when the 'Specified' option was chosen. The problem was fixed.


When exporting resources from HCL OneTest API, the exported zip file no longer contains empty folders.


Previously, the "Add a new condition" list for the File Schema window incorrectly contained the entry "[CRRIT3613E] This option no longer exists. Please contact support." This problem was resolved.


Previously in HCL OneTest API, when synchronizing with a Swagger definition by using a URL, relative references would fail to resolve. The problem was fixed.


The default way that the Integration Tester Agent installs as a local service on Windows 2016, that is with "This account", now works.


When sending messages by using the Email transport, if the data is already a message the resulting email will be received as a text encoded MIME message in the body. This problem was fixed.