|
Problem(Abstract) |
MustGather for problems with the WebSphere® Application
Server discovery problems for all releases of V5. Gathering this
information before calling IBM® support helps familiarize you with the
troubleshooting process and saves you time. |
|
|
|
Resolving the
problem |
If you have not contacted support, click MustGather: Read First for WebSphere Application Server
for z/OS
Discovery-specific MustGather information:
Discovery is the process by which the Deployment Manager locates and
establishes contact with the various NodeAgents, as well as the way Node
Agents locate and contact the Application Servers. If the discovery
process completed successfully you see the following message in the
JOBLOGS:
ADMD0023I=ADMD0023I: Process discovered (name: {0}, type: {1}, pid: {2})
{0} is the name of the process, {1} is the type, and {2} is the process
id.
The Deployment Manager should issue the message ADMD0023I for every Node
Agent that is configured and running in the cell; similarly the Node Agent
issues one message for every Server, as well as for the Deployment
Manager.
If discovery does not occur, set the following trace in both the servers
that are trying to communicate. For example, if a NodeAgent and Deployment
Manager are not discovering each other, set the trace in both. Do the same
for Server and Node Agent. A startup trace is best, because discovery is
one of the first things a server does after coming up.
com.ibm.ws.management.discovery.*=all=enabled
For information on sending documentation to IBM click Submitting Diagnostic Information to IBM.
For a listing of all technotes, search the WebSphere Application Server for z/OS support
page. |
|
|
|