Home
Troubleshooting
While working with HCL DevOps Test Integrations and APIs (Test Integrations and APIs), you might encounter some problems that you can easily troubleshoot.
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.
Debugging with the JVM console
You can use the Test Integrations and APIs JVM console to debug any errors that might occur while you are working with Test Integrations and APIs.

Troubleshooting
While working with HCL DevOps Test Integrations and APIs (Test Integrations and APIs), 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 DevOps Test Integrations and APIs (Test Integrations and APIs).
- Global problem notifications
  Problems can occur at a time when Test Integrations and APIs cannot display an error message. Instead, a warning icon is displayed. Double-clicking the icon reveals a list of errors.
- Working with DevOps Test Integrations and APIs logs
  To configure the HCL DevOps Test Integrations and APIs (Test Integrations and APIs) logs, including those for the RunTest command when run from the command line, update the Test Integrations and APIs logging properties file.
- Working with DevOps Test Integrations and APIs Agent logs
  To configure the HCL DevOps Test Integrations and APIs Agent (Test Integrations and APIs Agent) logs, including those for the RunTests command when run from the command line, update the Test Integrations and APIs 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 Test Integrations and APIs, Test Integrations and APIs Agent, or Test Virtualization Control Panel 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 Test Integrations and APIs. All of the programs use the Java logging framework. For details, see the Java logging framework documentation.
- 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 DevOps Test Integrations and APIs (Test Integrations and APIs).
- 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.
  - Debugging with the JVM console
    You can use the Test Integrations and APIs JVM console to debug any errors that might occur while you are working with Test Integrations and APIs.
  - Limitations of topology discovery
    You must be aware of certain limitations in Topology discovery.
  - Limitations of packet capture
    You must be aware of certain limitations of packet capture.
  - WSDL versioning considerations
    Managing WSDL versions is a common problem that is faced by web services developers. Some guidance is provided to help address the problem.
  - Troubleshooting: COBOL copybook schemas
    You can use a workaround to problem that you can encounter after you import a COBOL copybook schema into Test Integrations and APIs.
  - Troubleshooting: WSDL schemas
    You can use some workarounds to problems that you might encounter during and after the import of a WSDL schema into HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
  - Troubleshooting: Messages
    You can use a workaround to a problem that you might encounter when you work with message fields.
  - Troubleshooting: Rational® Quality Manager
    You can use workarounds to common problems that you might encounter when you work with Rational® Quality Manager.
- 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).
- Troubleshooting: DevOps Test Virtualization Control Panel
  You can use workarounds to troubleshoot common problems that you might encounter when you use HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel).
- Troubleshooting: DevOps Test Virtualization
  You can use workarounds to common problems that you might encounter when you use HCL DevOps Test Virtualization (Test 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 DevOps Test Integrations and APIs (Test Integrations and APIs).
- Troubleshooting: WebSphere® Application Server
  You can use workarounds to problems that you might encounter when you use IBM® WebSphere® Application Server products with HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
- Troubleshooting: WebSphere® Portal
  You can use workarounds to problems that you might encounter when you use IBM® WebSphere® Portal products with HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
- Troubleshooting: TIBCO
  You can use workarounds to common problems that you might encounter when you are testing TIBCO products in HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
- Troubleshooting: Java™ method transport
  You can use workarounds to common problems that you might encounter when you use the Java™ method transport of HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
- Troubleshooting: Java™ applications that use JDBC
  You can use workarounds to problems that you might encounter when you test Java™ applications in HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
- 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 DevOps Test Integrations and APIs (Test Integrations and APIs).

Debugging with the JVM console

You can use the Test Integrations and APIs JVM console to debug any errors that might occur while you are working with Test Integrations and APIs.

Accessing the JVM console from the GUI

If the Test Integrations and APIs 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 Test Integrations and APIs 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 Test Integrations and APIs is started and is closed when Test Integrations and APIs is closed.
To view the Java console, open a browser and specify the following URL: http://localhost:8999/ConsoleOutput? in a browser.