WMB/IIB Mustgather: problems with Web Services (HTTP, HTTPS) problems on UNIX and Linux

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:
   Dynamic guide to help troubleshooting Message Broker

   IIB and Web services

   
   Implementing WebService security in WMB
   Run the WebServices samples
   WebSphere Message Broker support site
   

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
   
   • You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.
     See: Exporting files from the Workbench


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 service level trace is intended to be provided to IBM Support to assist in the diagnosis of your issue.
   • SSL trace for HTTPS problems only
   • SOAP debug trace when using SOAP nodes with http (not https)


4. General Broker information
   If the mqsidc tool was not run, then capture this information manually
   • Record the IBM Integration Bus or 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 UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.
     See: Configuring the syslog daemon
   • Collect the Standard Output/Error logs.
     WMB writes information to both STDOUT and STDERR. These files are located under the Message Broker workpath.
     See: Standard System Logs
   • Additional information
   • Output of command: mqsilist -r -d2
   • Is IIB/WMB acting as service provider or service consumer?

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

• Use IBM Service Request to open or view a problem record with IBM.
• Send your data to IBM for further analysis.