Home
Troubleshooting
While working with HCL OneTest™ API, you might encounter some problems that you can easily troubleshoot.
Logging references
You can use the following list of logging-related information to help you find information about the logs that are supported by HCL OneTest™ API. All of the programs use the Java logging framework. For details, see the Java logging framework documentation.
Debugging with the JVM console
You can use the HCL OneTest™ API JVM console to debug any errors that might occur while you are working with HCL OneTest API.

Troubleshooting
While working with HCL OneTest™ API, you might encounter some problems that you can easily troubleshoot.
- Troubleshooting: Installation and configuration
  You can troubleshoot some of the problems that you might encounter when you are installing, configuring, or running HCL OneTest™ API.
- Global problem notifications
  Problems can occur at a time when HCL OneTest™ API cannot display an error message. Instead, a warning icon is displayed. Double-clicking the icon reveals a list of errors.
- Working with HCL OneTest™ API logs
  To configure the HCL OneTest™ API logs, including those for the RunTest command when run from the command line, update the HCL OneTest API logging properties file.
- Working with HCL OneTest™ API Agent logs
  To configure the HCL OneTest™ API Agent logs, including those for the RunTests command when run from the command line, update the HCL OneTest API Agent logging properties file.
- Working with RQMAgent logs
  To configure the RQMAgent logs, update the RQMAgent logging properties file.
- Locating the logging properties files
  When you install HCL OneTest™ API, HCL OneTest API Agent, or HCL® Quality Server including the HTTP/TCP proxy, several logging properties files are added to each installation's home directory.
- Logging references
  You can use the following list of logging-related information to help you find information about the logs that are supported by HCL OneTest™ API. All of the programs use the Java logging framework. For details, see the Java logging framework documentation.
  - Locating the logging properties files
    When you install HCL OneTest™ API, HCL OneTest API Agent, or HCL® Quality Server including the HTTP/TCP proxy, several logging properties files are added to each installation's home directory.
  - Working with HCL OneTest™ API logs
    To configure the HCL OneTest™ API logs, including those for the RunTest command when run from the command line, update the HCL OneTest API logging properties file.
  - Working with HTTP/TCP proxy logs
    To configure the HTTP/TCP proxy logs, update the proxy logging properties file.
  - Working with HCL OneTest™ API Agent logs
    To configure the HCL OneTest™ API Agent logs, including those for the RunTests command when run from the command line, update the HCL OneTest API Agent logging properties file.
  - Working with RQMAgent logs
    To configure the RQMAgent logs, update the RQMAgent logging properties file.
  - Debugging with the JVM console
    You can use the HCL OneTest™ API JVM console to debug any errors that might occur while you are working with HCL OneTest API.
- 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.
- Troubleshooting: Installation and configuration
  You can troubleshoot some of the problems that you might encounter when you are installing, configuring, or running HCL OneTest™ API.
- Troubleshooting: transports, tests, and resources
  Workarounds and solutions for transport diagnostics, creating and running tests, and saving and renaming objects are contained in this topic.
- Troubleshooting: HCL OneTest™ API Agent
  You can use workarounds to common problems that you might encounter when you install and run the HCL OneTest™ API Agent.
- Troubleshooting: HCL® Quality Server
  You can use workarounds to troubleshoot common problems that you might encounter when you use HCL® Quality Server.
- Troubleshooting: HCL OneTest™ Virtualization
  You can use workarounds to common problems that you might encounter when you use HCL OneTest™ Virtualization.
- Troubleshooting: Software AG webMethods
  You can use workarounds to problems that you might encounter when you use the Software AG webMethods.
- Troubleshooting: Websphere MQ
  You can use workarounds to problems that you might encounter when you use IBM® WebSphere® MQ with HCL OneTest™ API.
- Troubleshooting: WebSphere® Application Server
  You can use workarounds to problems that you might encounter when you use IBM® WebSphere® Application Server products with HCL OneTest™ API.
- Troubleshooting: WebSphere® Portal
  You can use workarounds to problems that you might encounter when you use IBM® WebSphere® Portal products with HCL OneTest™ API.
- Troubleshooting: TIBCO
  You can use workarounds to common problems that you might encounter when you are testing TIBCO products in HCL OneTest™ API.
- Troubleshooting: Java™ method transport
  You can use workarounds to common problems that you might encounter when you use the Java™ method transport of HCL OneTest™ API.
- Troubleshooting: Java™ applications that use JDBC
  You can use workarounds to problems that you might encounter when you test Java™ applications in HCL OneTest™ API.
- Troubleshooting: HTTP and Web Services
  You can use workarounds to common problems that you might encounter when you use HTTP and Web Services.
- Troubleshooting: TCP UDP sockets
  You can use workarounds to common problems that you might encounter when you use TCP and UDP transports.
- Troubleshooting: Testing on IBM® z/OS®
  You can use workarounds to common problems that you might encounter when you use IBM® z/OS® with HCL OneTest™ API.

Debugging with the JVM console

You can use the HCL OneTest™ API JVM console to debug any errors that might occur while you are working with HCL OneTest™ API.

Accessing the JVM console from the GUI

If the HCL OneTest™ API GUI is running, to open the JVM Console, click Help > About > JVM Console.

Accessing the JVM console from the command line

Open a command window and navigate to the HCL OneTest™ API installation folder.
Run the IntegrationTester -console command. The Java console is opened.

Accessing the JVM console through HTTP

Open the Library Manger. In the JVM Arguments field of the Application pane, add the following line: -Dgreenhat.http.port=8999
Note: If port 8999 is already in use, specify a different port number.
Open the IntegrationTester.ini file that is available in the installation folder.
After the -vm parameter value line, add the following entries:
```
-consoleLog
 -debug
```
Note: The Java console window is displayed when HCL OneTest™ API is started and is closed when HCL OneTest™ API is closed.
To view the Java console, open a browser and specify the following URL: http://localhost:8999/ConsoleOutput? in a browser.