Installation considerations for HCL OneTest™ API

Hardware and software requirements

For a complete list of system requirements, see System Requirements.

Networking considerations

Note if HCL OneTest™ API will be running in an IPv4 or IPv6 networking environment. The Networking option in the Library Manager controls the IPv4/6 preference. For information about setting the networking preference, see Working with the Library Manager.

Security considerations

Ensure that you review the security considerations for installing the software. For more information, see Security considerations for HCL OneTest API.

Installing systems, transports, and technologies supported by HCL OneTest™ API

In HCL OneTest™ API, you can test numerous messaging and governance implementations, workflow, and database providers. The system or technology that is being tested must be installed and available to HCL OneTest™ API. Library Manager is an application that is installed with HCL OneTest™ API to provide support for various middleware and messaging technologies.

Library Manager settings

Library Manager settings and most user preferences are preserved during the uninstallation or reinstallation process. During the installation of HCL OneTest™ API, run Library Manager at the end of the process and confirm that the settings are correct. Perspective and dialog layout preferences are reset.

For information about Library Manager, see Working with the Library Manager.

Upgrading the database schema

If you uninstall and reinstall the software, you must ensure that the database schema version is compatible with the version of the software that you install. Until the database schema is upgraded, it is not possible to store results to the database.

This schema upgrade is required to provide Unicode compatibility for the Microsoft™ SQL Server database. When you upgrade, for Microsoft™ SQL Server, every varchar column that could contain Unicode characters is changed to an nvarchar column (while preserving the contents). For IBM® Db2®, Oracle and MySQL databases, the 1.9.24f upgrade does not change the structure of the database. Instead, it just marks the database as the 1.9.24f version to keep version numbers consistent across the four databases.

To upgrade the database schema, use the provided upgrade script for each of the four supported results databases. This script can be run only on a database that is already at version 1.9.24d. If your results database is an older version, you must run previous upgrade scripts to get it to 1.9.24e before you attempt the 1.9.24f upgrade. For more information, see Upgrading the project results database schema

See the following table for the database scheme version for each version of the software