IBM Support

WMB/IIB MustGather: problems with Security on Windows

Troubleshooting


Problem

You are experiencing a Security problem with WebSphere Message Broker (WMB) or IBM Integration Bus (IIB) and would like to know what documentation you must collect (MustGather) so that the WebSphere Message Broker Support team can diagnose your problem. 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 WMB / IIB 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:
    Resolving problems when developing message models
    Resolving problems when developing message flows
    WebSphere Message Broker support site
    Troubleshooting

  4. Additional Resources:
    Security overview
    Library and Information centers


Step 2: Collect Data


  1. mqsidc

    See: mqsidc usage instructions

    • When running the tool, select the option for 'Broker Collector', when prompted.

  2. WebSphere MQ Security documentation

  3. 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 Window systems, the local error log is the Windows Application Event Log.
      You can find the Event Viewer from the Windows Control Panel.
      See: Event viewer logs
    • Collect the Standard Output/Error logs.
      On Window systems, WMB writes information to a 'console.out' file.
      This file is located under the Message Broker workpath.
      See: Standard System Logs


ATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!
When sending data to IBM, be sure to update your PMR or send a note with the following information:

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



Back to top

[{"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Security","Platform":[{"code":"PF033","label":"Windows"}],"Version":"10.0;9.0","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":" ","Platform":[{"code":"PF033","label":"Windows"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Product Synonym

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

Document Information

Modified date:
23 March 2020

UID

swg21299471

Page Feedback