|
Problem(Abstract) |
Collecting data for problems with the IBM® WebSphere®
Application Server V5.0 System Management/Repository component. Gathering
this MustGather information before calling IBM support will help you
understand the problem and save time analyzing the data. |
|
Resolving the
problem |
If you already contacted support, continue to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
- Backup and purge the logs in the install_root/logs/nodeagent directory
and in the install_root/logs/FFDC directory.
- Enable tracing on the nodeagent:
- Make a backup copy of server.xml file for the nodeagent
- Edit the server.xml file for the nodeagent located in
WAS_BASE/config/cells/I/nodes/I/servers/nodeagent directory.
- Find the TraceService xml tag section.
- Modify the startupTraceSpecification entry to look like the following:
com.ibm.*=all=enabled
- Make sure enable is set to true.
- Startnode with -trace option.
example: ./startNode.sh -trace
example: startNode.bat -trace
- Run the collector tool on the base node - See the Information
Center for additional information on running the collector tool.
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the System Management/Repository component, search the WebSphere
Application Server support site. |
|
|