|
Problem |
Does the Node Agent have to be running for an Application
Server in the node to be started? |
|
Solution |
In a Network Deployment environment, an application server
cannot start unless the Node Agent is running. Upon application server
start-up, the server must register with the Node Agent in order to provide
the correct server status to the Deployment Manager and also allow
configuration and administrative changes to be performed on the server
through the Deployment Manager.
In the past, part of the requirement that the Node Agent had to be
started was because the Location Service Daemon (LSD) ran specifically on
the Node Agent and the application server needed the LSD to find resources
within a cell. This Location Service Daemon (LSD) was changed in WebSphere
Application Server V5.0.2 to not be a single point of failure and this is
no longer a reason the Node Agent must be started for an application
server to be started. The requirement now is strictly for registering the
server with the Node Agent and then the Deployment Manager for server
configuration and administration. It also allows the server to be
registered as active for a cluster which contains the server. While it is
not recommended to run a server with out the Node Agent running, it is
possible after the server has started to shut down the Node Agent and to
continue handling requests. The server will not be capable to be managed
or administered however. |
|
|