Home
Troubleshooting Rational® Integration Tester
While working with Rational® Integration Tester, 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.
Troubleshooting: Rational® Quality Manager
You can use workarounds to common problems that you might encounter when you work with Rational® Quality Manager.

Troubleshooting Rational® Integration Tester
While working with Rational® Integration Tester, 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 Rational® Integration Tester.
- Global problem notifications
  Problems can occur at a time when Rational® Integration Tester cannot display an error message. Instead, a warning icon is displayed. Double-clicking the icon reveals a list of errors.
- Working with Rational® Integration Tester logs
  To configure the Rational® Integration Tester logs, including those for the RunTest command when run from the command line, update the Rational Integration Tester logging properties file.
- Working with Rational® Integration Tester Agent logs
  To configure the Rational® Integration Tester Agent logs, including those for the RunTests command when run from the command line, update the Rational Integration Tester 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 Rational® Integration Tester, Rational Integration Tester Agent, or Rational Test 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 Rational® Integration Tester. 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 Rational® Integration Tester.
- 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 Rational® Integration Tester JVM console to debug any errors that might occur while you are working with Rational Integration Tester.
  - 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 Rational® Integration Tester.
  - Troubleshooting: WSDL schemas
    You can use some workarounds to problems that you might encounter during and after the import of a WSDL schema into Rational® Integration Tester.
  - 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.
- Rational® Integration Tester Agent
  You can use workarounds to common problems that you might encounter when you install and run the Rational® Integration Tester Agent.
- Troubleshooting: Rational® Test Control Panel
  You can use workarounds to troubleshoot common problems that you might encounter when you use IBM® Rational® Test Control Panel.
- Troubleshooting: Rational® Test Virtualization Server
  You can use workarounds to common problems that you might encounter when you use IBM® Rational® Test Virtualization Server.
- 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 Rational® Integration Tester.
- Troubleshooting: WebSphere® Application Server
  You can use workarounds to problems that you might encounter when you use IBM® WebSphere® Application Server products with Rational® Integration Tester.
- Troubleshooting: WebSphere® Portal
  You can use workarounds to problems that you might encounter when you use IBM® WebSphere® Portal products with Rational® Integration Tester.
- Troubleshooting: TIBCO
  You can use workarounds to common problems that you might encounter when you are testing TIBCO products in Rational® Integration Tester.
- Troubleshooting: Java™ method transport
  You can use workarounds to common problems that you might encounter when you use the Java™ method transport of Rational® Integration Tester.
- 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 Rational® Integration Tester.

Troubleshooting: Rational® Quality Manager

You can use workarounds to common problems that you might encounter when you work with Rational® Quality Manager.

Table 1. Troubleshooting Rational® Quality Manager
Solutions and workarounds to problems with Rational® Quality Manager
Problem	Resolution
Rational® Integration Tester Agent V9.0 after configuring as a Rational® Quality Manager adapter to use TLSv1.2 does not connect to enable remote test execution.	Install Rational® Integration Tester V9.1.0 or later. Otherwise, for V9.0 add the following Java™ parameter: `-Dhttps.protocols=TLSv1.2` For Rational® Integration Tester, add it to `RQMAgent.ini`. For Rational® Integration Tester Agent, add it to the Library Manager JVM arguments. Note: To see what protocol is used by the Agent when connecting to Rational® Quality Manager, add the following Java™ parameter to `RQMAgent.ini` and `Agent.ini`. `-Djavax.net.debug=all`
After you execute tests or suites from Rational® Quality Manager, and click Test Results on RTCP (Click Here) from the Test Case or Test Suite Results window, a dialog opens prompting you to enter a database name. This dialog shows because you did not configure a project results database to use and so the connection to the database fails.	You must configure the project results database and publish the results database connection details from the Rational® Integration Tester project that contains the tests and suites to Rational® Test Control Panel. For more information, see Working with Rational Integration Tester resources in Rational Quality Manager.
When Rational® Integration Tester Agent is using an Asian locale, results from executing Rational® Integration Tester tests and suites in Rational® Quality Manager do not show in an Asian language.	Change the Asian locale to an English locale by using one of the following ways: Edit `Agent_installation_directory/RunTests.ini` and append the following lines: `-nl en` Edit `Agent_installation_directory/LibConfig` and add the following JVM argument: `-Duser.language=en_US` Export the Rational® Integration Tester tests and suites again and execute them from Rational® Quality Manager. The results show in English in Rational® Quality Manager.