| Collect troubleshooting data for problems with IBM WebSphere Adapter and WebSphere Business Integration Adapters. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time. |
The term "MustGather" represents the diagnostic data (system information, symptoms, log files, traces, and so on) that is required to resolve a problem. By collecting MustGather data early, even before you open a PMR, you help IBM Support quickly determine the following:
- Whether symptoms match known problems (rediscovery)
- If you have a non-defect problem that can be identified and resolved
- If there is a defect that identifies a workaround to reduce severity
- If locating the root cause can speed development of a code fix
Select the runtime product from the following list:
Use the following information for WebSphere Business Integration Adapters:
Note: WebSphere Application Server only supports:
Collect the following information about your environment:
- Adapter version (including the fix pack level)
- WebSphere Application Server version (including the fix pack level)
- Rational Application Developer version (including fix pack level)
For Development or Build time issues, collect the EMD Meta data discovery logs.
For Runtime traces:
- Enable the adapter tracing from the WebSphere Process Server administrative console.
- Navigate to Troubleshooting > Logs and traces > server > Change Log level details.
- Set the following tracing either in the Configuration tab or the Runtime tab:
| com.ibm.j2ca.*=all |
|
| Note: Changing the traces in Configuration tab would require server restart to take into effect. |
|
- Recreate the issue.
- Collect the system out, trace, and ffdc logs.
Note: WebSphere Enterprise Service Bus only supports:
Collect the following information about your environment:
- Adapter version (including the fix pack level). To determine the version of the adapter, choose one of these approaches:
- Extract the Adapter.jar file within the Adapter.rar file to find the Manifest.mf file which contains the adapter version.
- In WebSphere Integration Developer, navigate to File > New > ESD to open the ESD wizard which displays the adapter version.
- WebSphere Enterprise Service Bus version (including fix pack level)
- WebSphere Integration Developer version (including fix pack level)
For Development or Build time issues, collect the EMD Meta data discovery logs.
For Runtime traces:
- Enable the adapter tracing from the administrative console.
- Navigate to Troubleshooting > Logs and traces > server > Change Log level details.
- Set the following tracing either in the Configuration tab or the Runtime tab:
| com.ibm.j2ca.*=all |
|
| Note: Changing the traces in Configuration tab would require server restart to take into effect. |
|
- Recreate the issue.
- Collect the system out, trace and ffdc logs.
Note: WebSphere Message Broker only supports:
Collect the following information about your environment:
Note: WebSphere Process Server only supports:
Collect the following information about your environment:
- Adapter version (including the fix pack level). To determine the version of the adapter, choose one of these approaches:
- Extract the Adapter.jar file within the Adapter.rar file to find the Manifest.mf file which contains the adapter version.
- In WebSphere Integration Developer, navigate to File > New > ESD to open the ESD wizard which displays the adapter version.
- WebSphere Process Server version (including fix pack level)
- WebSphere Integration Developer version (including fix pack level)
For Development or Build time issues, collect the EMD Meta data discovery logs.
For Runtime traces:
- Enable the adapter tracing from the WebSphere Process Server administrative console.
- Navigate to Troubleshooting > Logs and traces > server > Change Log level details.
- Set the tracing either in the Configuration tab or the Runtime tab.
| com.ibm.j2ca.*=all |
|
| Note: Changing the traces in Configuration tab would require server restart to take into effect. |
|
- Recreate the issue.
- Collect the system out, trace and ffdc logs.
Note: WebSphere Transformation Extender only supports:
Collect the following information about your environment:
- Adapter version including the fix pack level and interim fix level
- WebSphere Transformation Extender version and fix pack level
- Adapter runtime log file. Configure and run the adapter to generate the trace file. This can be done by setting the following option on the adapter execution command line:
| TV <file location relative to the map or absolute path> |
|
All the adapter's runtime tracing information will go to this trace file.
- If the issue involves the WebSphere Transformation Extender Importer wizard and configuring adapter, provide these log files:
- Log files located in Eclipse workspace .metadata directory. (In other words, Eclipse <workspace>\.metadata\.log)
- WebSphere Transformation Extender Launcher logs. If inbound scenario, set the following options in the dtx.ini file:
- LogTrace=1
- LogDebug=1
- LogInfo=1
- LogWarning=1
- LogError=1
- LogFatal=1
For the inbound scenarios, when running the WebSphere Transformation Extender Launcher, provide the logs for the Launcher. The logs could be enabled in the
dtx.ini file.
Collect the following information about your environment:
- The Adapter type and version, including Fix Pack, if any.
- Version of broker used. (for example: WebSphere InterChange Server, including Fix Pack and/or LAIF level, if any or other broker)
- Adapter Framework version, including fix packs or LAIFs, if any.
- Operating System, including maintenance level or Service Pack level, if any.
- If applicable, database version, including fix pack level, if any.
- If applicable, MQ version, including CSD level, if any.
Take these steps to gather logs and the following detailed information:
- Collect the Adapter log and trace files, with trace level set at level 5, if possible.
- Collect the adapter configuration file, following these steps:
- Collect the configuration file supplied at startup through the command line.
- If you do not use a cfg file, do the following:
- Import the adapter into your System Manager.
- Open the adapter in the Connector Configurator.
- Click File > Save as > to File.
- Specify a path and file name.
- If possible, describe the steps to recreate the problem.
- Provide the repository that contains all of the objects needed to recreate the issue.
- Describe recent changes to the system, if any.
- If you encountered any MQ error messages, collect the following 2 MQ error logs:
\MQ_INSTALL_HOME\errors\AMQERRxx.log
\MQ_INSTALL_HOME\Qmgr name\errors\AMQERRxx.log |
|
To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:
- IBM Support Assistant (ISA)
- Service Request (SR)
- FTP to the Enhanced Customer Data Repository (ECuRep)
For information about using each of these services, see
Exchanging information with IBM Technical Support.
