|
This document applies only to the following language
version(s):
English |
|
Problem |
Collecting data for problems with the IBM® WebSphere®
Application Server monitoring policy by nodeagent component. Gathering
this MustGather information before calling IBM support will help you
understand the problem and save time analyzing the data. |
|
Solution |
If you already contacted support, continue to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
Nodeagent does not properly monitor the Application Servers Specific
Mustgather Information
- Describe the problem in detail and any possible work around found.
- Stop the NodeAgent and Application Server monitored.
For v5.0 users, enable
com.ibm.ws.management.*=all=enabled on the nodeagent and
application server(s) in the Administrative Console under Troubleshooting
> Logs and Trace > serverName > Diagnostic Trace Service.
For v6.0 users, enable com.ibm.ws.management.*=all on the
nodeagent and application server(s) in the Administrative Console under
Troubleshooting > Logs and Trace > serverName > Change Log Detail
Levels.
Start the NodeAgent and Application Server being monitored to recreate the
problem.
- Run the collector tool on all installs involved. See the Information
Center specific to the version of Application Server you are running
for additional information on running the collector tool.
- Follow instructions to send
diagnostic information to IBM support.
What to do next
Once you have collected the preceding information, you can submit
the diagnostic information to IBM support.
For a list of all technotes, downloads, and educational materials
specific to System Management, search the WebSphere
Application Server support site. |
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|
|