Installation considerations for DevOps Test Integrations and APIs
HCL DevOps Test Integrations and APIs (Test Integrations and APIs) is installed as part of the HCL DevOps Test Workbench or HCL DevOps Test Integrations and APIs product offering.Consider the requirements discussed in this section before installing Test Integrations and APIs.
Read the following information before you install Test Integrations and APIs:
- Hardware and software requirements
- Networking considerations
- Security considerations
- Installing systems, transports, and technologies supported by Test Integrations and APIs
- Library Manager settings
- Upgrading the database schema
- Windows Packet Capture feature
Hardware and software requirements
For a complete list of system requirements, see System Requirements for DevOps Test Integrations and APIs 2024.03 (11.0.1).
Networking considerations
Note if Test Integrations and APIs 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 Library Manager.
Security considerations
Ensure that you review the security considerations for installing the software. For more information, see Security considerations for DevOps Test Integrations and APIs.
Installing systems, transports, and technologies supported by Test Integrations and APIs
In Test Integrations and APIs, 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 Test Integrations and APIs. Library Manager is an application that is installed with Test Integrations and APIs 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 Test Integrations and APIs, 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 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
Test Integrations and APIs version | Database schema version |
---|---|
Releases of 9.x.x version | 1.9.24f |
Releases of 8.7.1 version | 1.9.24f |
Releases of 8.5, 8.6, 8.7 versions | 1.9.24e |
Releases of 8.0 version | 1.9.24d or 1.9.24e |
Green Hat Tester 5.4 | 1.9.24d or 1.9.24e |
Windows Packet Capture feature
If you intend to use the packet capture feature in Test Integrations and APIs 10.5 or later, you can install the Win10PCAP feature from the Win10PCAP website.