Working with the 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.

Library Manager is an application that is installed with HCL OneTest API that is used to manage the libraries (Java™ JAR files) that are required by different plug-ins.

Important: If HCL OneTest API and its Agent are installed on the same computer, Library Manager must be run during the installation of both applications.

If you are using Microsoft Windows, Library Manager can be started from the HCL OneTest program group (default is HCL OneTest > Library Manager (set-up)).

Otherwise, you can start Library Manager with the LibConfig executable in the HCL OneTest API installation directory.

Important: Library Manager writes some of its configuration details to the user’s home directory, .integrationtester, and to the HCL OneTest API installation directory. To ensure that Library Manager can write to the HCL OneTest API installation directory, the user ID used to install HCL OneTest API must be used when running Library Manager.

On the Library Manager application window, HCL OneTest API properties and third-party plug-ins are listed alphabetically on the left side.

To view/modify a specific configuration, select it in the list. The settings for the selected entry are displayed on the right side of the screen.

When you complete configuring Library Manager, click OK to save any changes that were made and to apply the new settings. If HCL OneTest API is running, you must restart it to ensure that any changes that you made take effect.

Note: If Library Manager changes are not applied, you do not have sufficient user privileges. You must rerun Library Manager as a user with administrative privileges or as an administrator (whichever is applicable), depending on the operating system that is being used.

Application settings

Application settings are used to configure general properties of the HCL OneTest API application. Required values are populated with default settings when Library Manager is run for the first time. However, any of the default values can be modified.

Setting Description
Max memory usage The amount of memory (in MB) that is allocated to HCL OneTest API. Allocating more memory can increase the performance of the application.
HTTP Bind Address When HCL OneTest API or one of its Agents is running an HTTP-based stub, this value is the host name or IP address of the network adapter that it listens on. In most cases, you also enter the same information in the other bind address fields on this page. This setting is for use in an environment with a firewall, a VPN, or multiple network connections. For more information, see Firewalls, VPNs, and multihomed machines.
HTTP Proxy Port When HCL OneTest API or one of its Agents uses an HTTP proxy to make outbound HTTP connections, this value is the port number that is used to connect to the proxy. This setting is for use in an environment with a firewall, a VPN, or multiple network connections. The value must refer to a unique port number that is open in the firewall. For more information, see Firewalls, VPNs, and multihomed machines.
HTTP Proxy Server When HCL OneTest API or one of its Agents uses an HTTP proxy to make outbound HTTP connections, this value represents the host name or IP address of the proxy server. This setting is for use in an environment with a firewall, a VPN, or multiple network connections. For more information, see Firewalls, VPNs, and multihomed machines.
Environment Recording Port During recording, the proxies and intercept technologies send information back to HCL OneTest API over an HTTP connection. This field contains the port number that is used to connect to the proxy. This setting is for use in an environment with a firewall, a VPN, or multiple network connections. The value must refer to a unique port number that is open in the firewall. For more information, see Firewalls, VPNs, and multihomed machines.
Environment Recording Bind Address During recording, the proxies and intercept technologies send information back to HCL OneTest API over an HTTP connection. This value is the host name or IP address of the network adapter that it listens on. In most cases, you also enter the same information in the other bind address fields on this page. This setting is for use in an environment with a firewall, a VPN, or multiple network connections. For more information, see Firewalls, VPNs, and multihomed machines.
WMIS Server Port The port where HCL OneTest API listens for webMethods Integration Server requests. This setting is for use in an environment with a firewall, a VPN, or multiple network connections. The value must refer to a unique port number that is open in the firewall. For more information, see Firewalls, VPNs, and multihomed machines.
WMIS Server Bind Address The host name or IP address to which HCL OneTest API is bound for webMethods Integration Server requests. In most cases, you also enter the same information in the other bind address fields on this page. This setting is for use in an environment with a firewall, a VPN, or multiple network connections. For more information, see Firewalls, VPNs, and multihomed machines.
CICS® Stub Server Port The port where HCL OneTest API listens for CICS Stub Server requests. This setting is for use in an environment with a firewall, a VPN, or multiple network connections. The value must refer to a unique port number that is open in the firewall. For more information, see Firewalls, VPNs, and multihomed machines.
CICS Stub Server Bind Address The host name or IP address to which HCL OneTest API is bound for CICS Stub Server requests. In most cases, you also enter the same information in the other bind address fields on this page. This setting is for use in an environment with a firewall, a VPN, or multiple network connections. For more information, see Firewalls, VPNs, and multihomed machines.
IDB Client Port The port where the integrated simulation database listens for JDBC requests.

IMS™ Connect Stub Server Bind Address

The host name that is used for any IMS Connect stubs created by using HCL OneTest API. If a host name is not specified, HCL OneTest API uses localhost as the default value.

Security Policy Reserved for future use.
Original Software Path The path to the Original Software TestDrive testing module, version 6 or earlier. This path is used for running scripts and action maps with the GUI Interaction test action, where you specify the directory that contains the Programs folder.
Original Software v7 Path The path to the Original Software TestDrive testing module, version 7 or later.
Hewlett Packard Path The installation path of HP QuickTest Professional, which is required for running QTP scripts with the GUI Interaction test action.
CentraSite Publication fields The default fields to be made available for publishing test suite summary reports to a configured CentraSite server. For more information, see Testing Software AG CentraSite.
Feature Enablement Enter the code from a license to enable extended features.
Default Network Device The default, local network device to use for any direct network-related tasks, such as capturing HTTP packets. The properties of the selected device are displayed below the selection.
Networking
  • Prefer IPV4 : The application will prefer IPv4 addresses over IPv6 ones where possible.
  • Prefer IPV6 : The application will prefer IPv6 addresses over IPv4 ones where possible.
For more information see Internet Protocol IPv4 and IPv6
JVM Arguments Arguments to pass to the JVM used by HCL OneTest API and the command-line application. For example, to set the maximum amount of memory (in MB) allocated to the Java heap, you would use the format -Xmxmem_sizem, and specify a size, such as-Xmx512m.
Note: Each argument must be entered on a separate line in Library Manager.

Third-party plug-ins

The third-party systems (plug-ins) that HCL OneTest API supports are listed on the left side of Library Manager. For each plug-in, one or more providers can be configured. Generally speaking, a provider is a version of an application whose libraries are needed by HCL OneTest API to interact with the application. Each provider requires a specific set of libraries for use by HCL OneTest API.

Each plug-in is configured in two sections of Library Manager. The specific provider is selected in the upper portion of the screen. The libraries that are required by that provider are specified or customized in the lower portion of the screen.

In the example that is shown, the TIBCO Runtime Agent is selected and the JAR files are displayed. The support for TIBCO BusinessWorks is provided by an installation of the Runtime Agent that when installed shows in the specified default location on the C: drive.
TIBCO Runtime Agent is selected and the jar files are displayed.

For the provider you want to use with HCL OneTest API, select the check box next to the specific provider name. If you do not select the relevant check box, Library Manager does not apply the changes.

Note: For certain provider-types, only one specific provider at a time can be selected for use by HCL OneTest API.
Feedback