WMB/IIB Mustgather: problems with FTE for Windows

Technote (troubleshooting)


Problem(Abstract)

You are experiencing a problem with the MQ FTE (File Transfer Edition) Nodes with 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 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. 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.

  4. 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

    • Output the FTEAgent properties stored in WMB mqsireportproperties <broker name> -e <EG name> -o FTEAgent -r
    • Screen shot of Transfer log in MQ Explorer captured as follows:
      a. Expand the coordination qmgr in MQ Explorer
      b. Click on Transfer Log and expand (click on + sign) the failed transactions in the Transfer Log
      c. Capture a screen shot and send it to support
    • A directory listing of your <workpath>/common/FTE


  • 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 IBM Integration Bus 9.0 All Editions

Product Alias/Synonym

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

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Message Broker
Built-in nodes

Software version:

7.0, 8.0

Operating system(s):

Windows

Reference #:

1625855

Modified date:

2014-03-19

Translate my page

Machine Translation

Content navigation