+

Search Tips   |   Advanced Search

Manage node agents

Node agents manage and monitor application servers on that node. Node agents route administrative requests to application servers.

To manage a node agent, install WebSphere Application Server, Network Deployment.

To change the system clock, stop all the application servers, the node agent servers, the deployment manager server, the administrative agent server, and the job manager server first. After stopping the servers, change the system clock, and then restart the servers. If we change the system clock on one system, ensure the clocks on all systems that communicate with each other and have WAS installed are synchronized. Otherwise, we might experience errors, such as security tokens no longer being valid.

A node agent is a server created automatically when a node is added to a cell. A node agent runs on every host computer system that participates in the WAS ND product. We can view information about a node agent, stop and start the processing of a node agent, stop and restart application servers on the node managed by the node agent, and so on.

A node agent is purely an administrative agent and is not involved in application serving functions. A node agent also hosts other important administrative functions, such as file transfer services, configuration synchronization, and performance monitoring.

We can manage nodes through the wsadmin scripting tool, through the Java APIs, or through the administrative console. Perform the following tasks to manage nodes on an application server through the administrative console.


Tasks


Subtopics

  • Manage profiles for nonroot users
  • Security considerations when in a multi-node WAS WAS ND environment
  • IP version considerations for cells