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.
Limitations of packet capture
You must be aware of certain limitations of packet capture.

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.

Limitations of packet capture

You must be aware of certain limitations of packet capture.

Prerequisite

In the Library Manager, Application page, the Default Network Device field must be set to a physical interface.

Packet capture basics

Packet capture refers to the interception of a data packet as it travels across a network. Packet capture (as opposed to using an External Proxy Server) is an option when setting the Recording mode for the following transports:

TCP
FIX
HTTP

Packet capture requires specialized software:

On Windows™ systems, Network Packet Capture is not included in the Rational® Integration Tester installation program. If you want to install the Network Packet Capture feature at the time of installation of Rational® Integration Tester, you must select the Network Packet Capture option.
Note: If you want to enable the Network Packet Capture feature anytime after you install Rational® Integration Tester, you can use the Modify option in Installation Manager to modify the software package.
See Installation of Rational Integration Tester.
On non-Windows systems, libpcap is typically installed by default. If necessary, you can download the latest package from http://www.tcpdump.org/.

If you choose Packet Capture as your Recording mode, Rational® Integration Tester calls the appropriate packet capture software automatically.

Limitations

Although packet capture is simpler than using an external proxy server, be aware of the following limitations:

Your system administrator might not allow the use of packet capture software due to security concerns with intercepting traffic.
On non-Windows systems, root permissions are required to access the network port in promiscuous mode, and thus to run packet capture.
Packet capture does not work with wireless network adapters. Make sure that the Default Network Device in Library Manager is set to a physical interface.
You can record only those messages that are sent from, or received by, the system running Rational® Integration Tester. You cannot record messages between remote systems.
Packet capture cannot access messages that are sent locally on a Windows™ system, because these messages go through the internal loopback connector. For more information about the internal loopback connector, see http://wiki.wireshark.org/CaptureSetup/Loopback.