Home
Rational® Integration Tester
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.
Configuring HCL OneTest™ API
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.

Rational® Integration Tester
- Release Notes
  This document contains information about What's new, installation, known issues, and contact information of IBM Support.
- System Requirements
  This document includes information about hardware and software requirements for HCL OneTest™ API.
- Getting Started
  This guide provides an overview and describes the tasks to get you started with HCL OneTest™ API.
- 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 Rational® Integration Tester
    You can find information about installing IBM® Rational® Integration Tester from the IBM Rational Test Workbench or IBM Rational Integration Tester package.
  - Installation of Rational® Test Control Panel
    You can find information about installing IBM® Rational® Test Control Panel from the IBM Rational Test Workbench, IBM Rational Test Virtualization Server, or IBM Rational Performance Test Server package.
  - Configuring 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 and performance results from agents and probes are 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. For example, lengthy performance tests can generate large amounts of data. 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.
      - 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 HCL Quality Server and HCL OneTest™ API, 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.
    - 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.
    - 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 Server
    HCL 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.
  - Integrating
    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.
- 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.
- Troubleshooting HCL OneTest™ API
  While working with HCL OneTest™ API, you might encounter some problems that you can easily troubleshoot.
- HCL OneTest™ API reference
  HCL OneTest™ API is a scripting-free environment for developing tests for service-oriented architecture (SOA) messaging and business process integration projects. Tests can be built by recording existing system behaviors or from requirements, by entering the data to send and the data that is expected in return.
- Security Considerations
  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=<Host name or IP address of HTTP/TCP proxy>-Dhttp.proxyPort=<Port number specified during installation>-Dhttps.proxyHost=<Host name 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 HCL Quality Server 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.