IBM Support

WMB/IIB MustGather: problems with Adapters on Windows

Technote (troubleshooting)


Problem(Abstract)

You are experiencing problems with Adapters in WebSphere Message Broker (WMB) or IBM Integration Bus (IIB).
This mustgather document explains how to troubleshoot this problem by yourself, how to generate diagnostic data when the problem is happening, how to collect the available data from your system, and how to share that data with IBM support.

Environment

These instructions are for WebSphere Message Broker or IBM Integration Bus on Windows systems.
Return to the WebSphere Message Broker MustGather index for other systems.

Resolving the problem


Step 1: Self-guided Troubleshooting


  1. Consider Using the Test Client in trace and debug mode.

  2. A user level trace is intended to assist users with understanding how their ESQL is processed.
    It will also show a high level view of the message flow behavior.

  3. Check for known issues:

    WebSphere Adapter nodes
    Transport and connectivity samples
    Integrating WMB with SAP
    IBM Integration Bus support site



Step 2: Collect Data


  1. mqsidc
    See: mqsidc usage instructions
    • This command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, and IIB 9.0.
    • When running the tool, select the option for 'Broker Collector', when prompted.

  2. Project Interchange files for the problematic flow/set/ESQL/model

  3. Refer to Adapter troubleshooting mustgathers
  4. Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces can be used to gain a better understanding of the problem.
    • A user level trace is intended to assist users with understanding how their ESQL is processed. It will also show a high level view of the message flow behavior.
    • A service level trace is intended to be provided to IBM Support to assist in the diagnosis of your issue.
    • RFC traces:
      Steps to enable and collect the RFC Traces:
      1. Launch the Adapter Connection Wizard ,and proceed to the 'Service Generation and Deployment Configuration' window. In the SAP RFC trace configuration section:
      -Set the RFCTraceOn property to 'true'
      -Set the RFC Trace Level property to '8' , which outputs verbose debug messages, full
      execution path, info messages, errors and warnings
      -Set the Folder for RFC trace files property to the directory location where the RFC Traces
      are created

      2. Recreate the issue.

      3. Collect the RFC trace files generated.

      Note: The trace files are created in the directory where the adapter process has been started by default. The trace file has a .trc file extension and the file name will start with the letters rfc followed by a unique identifier. For example, rfc03912_02220.trc.

  5. General Broker information
    If the mqsidc tool was not run, then capture this information manually
    • Record the WebSphere Message Broker version, release, and maintenance level.
      This can be captured using the command 'mqsiservice -v'..
    • Record the operating system version, release, and maintenance level.
    • Record the version, release, and maintenance level of any related products and components for the problematic application.
    • Collect the local error log. On Windows, the local error log is the Windows Event viewer application log.
      See: Windows Event viewer application logs
    • Collect the console.txt

      WMB writes information to console.txt. This file is located under the Message Broker workpath.
      See: Standard System Logs



  • Tell us what errors you saw, where you saw them, and what time they happened
  • Let us know if you made any changes to WebSphere Message Broker or the system before the problem
  • Share any other observations which you think will help us to better understand the problem

Step 3: Submit Data to IBM





Please see the IBM Software Support Handbook for more information on working with IBM support.

Cross reference information
Segment Product Component Platform Version Edition
Business Integration WebSphere Message Broker Windows 8.0 All Editions

Product Alias/Synonym

WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI

Document information

More support for: IBM Integration Bus
Adapter

Software version: 9.0, 10.0

Operating system(s): Windows

Reference #: 1299300

Modified date: 07 October 2016