Manage node agents

Node agents are administrative agents that represent a node to the system and manage the servers on that node. Node agents monitor application servers on a host system and route administrative requests to servers.

Before we can manage a node agent, install the WAS Network Deployment product.

If we plan 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 you stop the servers, change the system clock, and then restart the servers. If we change the system clock on one system, you must ensure the clocks on all systems that communicate with each other and have WAS installed are synchronized. Otherwise, you might experience errors, such as security tokens no longer being valid.

(zos) If we plan to change the system clock, stop all the application servers, the node agent servers, the deployment manager server, the administrative agent server, the job manager server, and the location service daemon first. After you stop the servers and location service daemon, change the system clock, and then restart the servers and location service daemon. If we change the system clock on one system, you must ensure the clocks on all systems that communicate with each other and have WAS installed are synchronized. Otherwise, you 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 Network Deployment 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 that is 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.

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


Results

Depending on the steps that you completed, you have viewed information about a node agent, stopped and started the processing of a node agent, and stopped and restarted application servers on the node that is managed by the node agent.


What to do next

We can administer other aspects of the WAS Network Deployment environment, such as the deployment manager, nodes, and cells.


Subtopics


Related concepts

(zos) Switching between 64 and 31 bit modes


Related tasks

Manage profiles for nonroot users

  • Security considerations when in a multi-node WebSphere Application Server WebSphere Application Server Network Deployment environment

    IP version considerations for cells