Welcome
Administrator Guide
Typically, a user with the administrator role is responsible for certain tasks including installation, configuration, and integration of the product. This guide lists all such topics.
HTTP/TCP proxy setup
The process of configuring applications to use the HTTP/TCP proxy varies according to the application.
Configuring Apache Tomcat to use HTTP/TCP proxy
You must modify the Java™ virtual machine (JVM) so that Apache Tomcat can use an HTTP/TCP proxy. You can configure Apache Tomcat by configuring JVM options in the Tomcat startup script.

Release Notes
This document includes information about the new features introduced, features deprecated or removed, defects fixed, and known issues identified in this version of HCL DevOps Test Virtualization (Test Virtualization). You can also find the installation and upgrade instructions along with the contact information of HCL Customer Support.
System Requirements
This document includes information about hardware and software requirements for Test Virtualization.
Getting Started
This guide provides an overview and describes the tasks to get you started with Test Virtualization.
Administrator Guide
Typically, a user with the administrator role is responsible for certain tasks including installation, configuration, and integration of the product. This guide lists all such topics.
- Installation of DevOps Test Integrations and APIs Agent
  You can find information about installing HCL DevOps Test Integrations and APIs Agent (Test Integrations and APIs Agent) from the HCL DevOps Test Workbench (Test Workbench), HCL DevOps Test Virtualization (Test Virtualization), or HCL DevOps Test Integrations and APIs (Test Integrations and APIs) package.
- Installation of DevOps Test Virtualization Control Panel
  You can find information about installing HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) from the HCL DevOps Test Workbench (Test Workbench), HCL DevOps Test Virtualization (Test Virtualization), or HCL DevOps Test Integrations and APIs (Test Integrations and APIs) 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.
- Upgrading DevOps Test Integrations and APIs Agent
  In general, you can upgrade from earlier versions of HCL DevOps Test Integrations and APIs Agent (Test Integrations and APIs Agent) to the most recent version without having to uninstall the software. Use the Installation Manager Update option to upgrade the software.
- 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.
- Configuring DevOps Test Integrations and APIs Agent
  After you install HCL DevOps Test Integrations and APIs Agent (Test Integrations and APIs Agent), you must edit or modify the attributes in the Agent.config file for the features that you want to test by using the agent. You need to configure the libraries to enable testing the SUT based on certain technologies and also set up the required proxies for enabling testing.
- Running DevOps Test Integrations and APIs Agent on Microsoft™ Windows™
  On computers running Microsoft™ Windows™, the agent is typically installed and run as a Windows service.
- Running DevOps Test Integrations and APIs Agent on Unix-like systems
  On Unix-like systems, you can start HCL DevOps Test Integrations and APIs Agent (Test Integrations and APIs Agent) by running the Agent executable in the root of the Test Integrations and APIs Agent installation directory (for example, /opt/HCL/DevOpsTestAPIAgent).
- Troubleshooting: DevOps Test Integrations and APIs Agent
  You can use workarounds to common problems that you might encounter when you install and run the HCL DevOps Test Integrations and APIs Agent (Test Integrations and APIs Agent).
- HTTP/TCP proxy setup
  The process of configuring applications to use the HTTP/TCP proxy varies according to the application.
  - Modifying the configuration settings of the HTTP/TCP proxy
    To change the server address, log level, and other settings, you can modify the registration.xml file of the HTTP/TCP proxy.
  - Configuring a HTTP(S) reverse proxy or TCP port forwarding
    The reverse proxy capability allows applications that are unable to configure HTTP(S) forward proxying to address the proxy directly and have it forward these requests to a configured destination, which is also applicable for forwarding TCP-based communications.
  - Advanced HTTP and TCP proxy configuration
    The HTTP protocol runs on top of the TCP protocol, but provides extra information about the message destination. For that reason, the two proxies are configured differently.
  - Configuring Apache Tomcat to use HTTP/TCP proxy
    You must modify the Java™ virtual machine (JVM) so that Apache Tomcat can use an HTTP/TCP proxy. You can configure Apache Tomcat by configuring JVM options in the Tomcat startup script.
  - Configuring WebSphere® Application Server to use HTTP/TCP proxy
    You must modify the Java™ virtual machine (JVM) so that WebSphere® Application Server can use an HTTP/TCP proxy. You can do this change by setting some JVM options through the administrative console.
  - HTTP/TCP proxy logs
    To help you troubleshoot HTTP/TCP proxy problems, a number of logging methods are available for the HTTP/TCP proxy.
  - Starting and stopping the HTTP/TCP proxy
    To route and record HTTP(S) and TCP traffic with Test Virtualization Control Panel and Test Integrations and APIs, you must start the HTTP/TCP proxy. If the proxy is installed as a Windows service, you can configure it for an automatic start on start of the system or for a manual start on demand.
  - Programmatic custom certificate creation in proxy
    When an HTTPS connection is established with an HTTP/TCP proxy, the certificate that is presented to the client by the proxy is retrieved from an existing keypair that represent the intended endpoint or is generated as the default certificate by the proxy and is signed by the private key in the keystore that is configured in the registration.xml. Ordinarily, this mechanism is sufficient. If full control over the generation of certificates is required, an alternative advanced approach is available. The approach requires that custom code is written to generate and sign the required certificates.
- 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.
- Administration of DevOps Test Virtualization Control Panel
  HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) is a server-based web application providing a central repository for virtualized services. The Test Virtualization Control Panel allows you to use virtual services published with HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to create, share, and deploy virtualized test environments in HCL DevOps Test Virtualization (Test Virtualization).
- Integrations
  HCL DevOps Test Virtualization (Test Virtualization) supports integration with various other tools for deployment automation tools.
Tester Guide
This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing.
Test Manager Guide
This guide describes the tasks that you can perform for tracking the quality of the application. This guide is intended for Test Managers.
Security Considerations for DevOps Test Virtualization
You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
Notices
This document provides information about copyright, trademarks, terms and conditions for product documentation.

Configuring Apache Tomcat to use HTTP/TCP proxy

You must modify the Java™ virtual machine (JVM) so that Apache Tomcat can use an HTTP/TCP proxy. You can configure Apache Tomcat by configuring JVM options in the Tomcat startup script.

Before you begin

You must have the required privileges to edit the Apache Tomcat startup script.

Procedure

Locate the Tomcat startup script.
The location of the script depends on the OS you are using. The location can be as follows:
- In Microsoft™ Windows™, at %CATALINA_HOME%\bin\catalina.bat
- In Unix-like systems, at $CATALINA_HOME/bin/catalina.sh
Open the catalina.sh file for editing and add the following JAVA_OPTS option for the proxy:

JAVA_OPTS="-Dhttp.proxyHost=<Hostname or IP address of HTTP/TCP proxy>-Dhttp.proxyPort=<Port number specified during installation>-Dhttps.proxyHost=<Hostname or IP address of HTTP/TCP proxy>-Dhttp.proxyPort=<Port number specified during installation>-Djavax.net.ssl.trustStore=/opt/tomcat/bin/greenhat.jks -Djavax.net.ssl.trustStorePassword=passphrase"
Note: If you are setting up a HTTP/TCP proxy to support both HTTP and HTTPS, use the properties as http.proxyHost for the HTTP proxy and https.proxyPort for the HTTPS proxy.

For example, if you have installed Test Virtualization Control Panel on a computer with the IP address as 101.25.87.99 and are using the default port 3128 for both HTTP and HTTPS, the options you set in the catalina.sh file are as follows:

JAVA_OPTS="-Dhttp.proxyHost=101.25.87.99 -Dhttp.proxyPort=3128 -Dhttps.proxyHost=101.25.87.99 -Dhttps.proxyPort=3128 -Djavax.net.ssl.trustStore=/opt/tomcat/bin/greenhat.jks -Djavax.net.ssl.trustStorePassword=passphrase"
Save and close the file.
Restart Tomcat for the changes to take effect.