Home
Administrator Guide
This guide describes how to install HCL OneTest™ API. After you install the software, you can perform administration tasks such as configuration and integration of the product. This guide is intended for administrators.
Configuration of HCL OneTest™ API
Working with Library Manager
HCL OneTest™ API uses a plug-in architecture to provide support for various middleware and messaging technologies, so the list of third-party products with which it interacts can become large. You can manage this list by using Library Manager. When support for a new architecture or messaging plug-in is required, you use Library Manager to add that support.
Firewalls, VPNs, and multihomed machines
Special considerations apply when you install HCL OneTest™ API on systems with firewalls, virtual private networks (VPNs), or connections to more than one network.

Administrator Guide
This guide describes how to install HCL OneTest™ API. After you install the software, you can perform administration tasks such as configuration and integration of the product. This guide is intended for administrators.
- Installation of HCL OneTest™ API
  You can find information about installing HCL OneTest™ API from the HCL OneTest Studio or HCL OneTest API package.
- Installation of HCL® Quality Server
  You can find information about installing HCL® Quality Server from the HCL OneTest™ Studio, HCL OneTest Virtualization, or HCL OneTest API package.
- Uninstalling the product software
  When you no longer require the software, you can use either Installation Manager or the stand-alone installer to uninstall the products that you have installed.
- License management
  Licensing for your HCL software is administered through HCL® License & Delivery portal. This portal is FlexNet-based web application to manage software entitlements and licenses.
- Configuration of HCL OneTest™ API
  - Installed directories
    When you install HCL OneTest™ API, the following directories are created and populated under the installation directory.
  - User file storage
    HCL OneTest™ API projects store user files, and can be created in any location to which a user has access. However, using a remote or network location can reduce HCL OneTest API performance significantly, so it is recommended that HCL OneTest API is installed on a local drive.
  - Changing the display language
    When you want to use the product in a different language other than the display language of your computer, then you can change the language of the product by using the command-line interface. You can find the information to change the language in Linux or Windows.
  - Configuring the project results database
    Historical test data is stored in the HCL OneTest™ API project results database. It is difficult to estimate the space that is required as the number and type of tests to be run varies. When you create the project results database, 50GB is probably a good starting point.
  - HTTP/TCP proxy setup
    The process of configuring applications to use the HTTP/TCP proxy varies according to the application.
  - Setting up the JDBC proxy
    After you install the JDBC proxy, you must deploy the proxy into the Java™ virtual machine (JVM) of the relevant applications, set up the proxy for use, and verify that it is deployed.
  - HCL OneTest™ API tool packages
    To enable HCL OneTest™ API to work with certain technologies, you must configure the required libraries by using the Library Manager and also install and configure HCL OneTest API tool packages that are provided with HCL® Quality Server.
  - Working with Library Manager
    HCL OneTest™ API uses a plug-in architecture to provide support for various middleware and messaging technologies, so the list of third-party products with which it interacts can become large. You can manage this list by using Library Manager. When support for a new architecture or messaging plug-in is required, you use Library Manager to add that support.
    - Firewalls, VPNs, and multihomed machines
      Special considerations apply when you install HCL OneTest™ API on systems with firewalls, virtual private networks (VPNs), or connections to more than one network.
    - Configuring HTTP watch mode (Unix-like installations only)
      To complete installing HCL OneTest™ API on Unix-like systems, you must configure HTTP watch mode with Java™ Packet Capture (JPCAP).
    - Adding the libraries for database testing by using Library Manager
      To enable HCL OneTest™ API access to the database for testing, you must add various libraries to the configuration.
    - Custom providers
      In Library Manager, you can create new specific providers to supplement any of the existing third-party plug-ins or JDBC providers.
    - Configure default and custom provider library settings
      If you want to use providers such as JDBC, you must configure their library settings in Library Manager so that they work correctly with HCL OneTest™ API.
    - Resolving missing libraries errors
      If you see that required libraries for a specific provider are missing, you must fix the error.
    - Library manager command-line options
      Use the LibConfig executable on computers that do not have a graphical user interface.
    - Library manager GUI settings
      When you use a command line to configure HCL OneTest™ API, you can use an existing file as a template, and hence reuse those template settings.
  - Debugging failed Windows™ services
    If one of the programs fails to start as a Windows™ service, it can be difficult to determine the cause. Typically the service fails to start but gives no indication of why. The Windows Event log has nothing useful and the process might not have created its log file.
  - HCL OneTest™ API and HCL OneTest™ Server
    You can publish test reports for tests run on HCL OneTest™ API to HCL OneTest Server. You can create secrets collections for your project and store them securely on HCL OneTest Server that you can retrieve the secrets from HCL OneTest Server during tests at runtime.
- Administering HCL® Quality ServerHCL® Quality Server
  is a server-based web application providing a central repository for virtualized services. The HCL® Quality Server allows you to use virtual services published with HCL OneTest™ API to create, share, and deploy virtualized test environments in HCL OneTest Virtualization.
- Integrations
  HCL OneTest™ API supports integration with various other tools for quality management, change management, software configuration management, and deployment automation tools such as UrbanCode™ Deploy or HCL® Launch.

Firewalls, VPNs, and multihomed machines

Special considerations apply when you install HCL OneTest™ API on systems with firewalls, virtual private networks (VPNs), or connections to more than one network.

Firewalls, VPNs, or multiple network connections can create situations where an application cannot locate a particular address or cannot follow a particular route. In these cases, you must provide an address that the application can use.

In the following illustration, HCL OneTest™ API runs on Machine C, which is connected to Network A. Machine C also has a VPN connection to Network B, where a proxy server is running.

Machine C is connected to both Network A and Network B.

When you start a TCP server on Machine C, it binds to one or more addresses on the networks visible to it such as 192.168.0.8 and 203.0.113.5, and uses an ephemeral port number, such as 50136, selected at random from the available ports. A problem arises when you want an application on Machine B, such as the proxy server in this example, to connect to the server you just started. The application cannot see Network A and therefore is unable to route messages to 192.168.0.8. Similarly, Machine C might have firewall restrictions that allow only a known set of ports to be opened for connection.

The solution is to provide HCL OneTest™ API with a fixed address and fixed port number on which to start the server. For example, you might specify a bind address of 203.0.113.7 and a port number of 7120, and then configure the firewall to open port 7120 for connection. This enables the proxy server to route messages to 203.0.113.7:7120.

Bind addresses and port numbers are maintained in Library Manager. For more information, see Working with Library Manager.