Introduction
The Node Agent server and the Deployment Manager server both use a repository of XML files on their own nodes. The master repository data is stored on the Deployment Manager node. That data is then replicated to each node in the Administrative domain (or cell). The Deployment Manager server and the Node Agent servers keep these files synchronized. The default synchronization interval is one minute. The synchronization process is unidirectional from the Deployment Manager to the Node Agents to ensure repository integrity. That means that any changes made on the Node Agent level are only temporary and will be overwritten by the Deployment Manager during the next synchronization. Only changes to the master data through the Deployment Manager are permanent and replicated to each node.
Administrative and configuration actions as well as operational changes can be applied to either the Node Agent server, the appserver, or the Deployment Manager through wsadmin scripting. To communicate with these servers you can use either the SOAP or the RMI protocol. The Administrative Console (adminconsole.ear) is an application that is installed in the Deployment Manager server by default in a WebSphere Network Deployment environment.
The Node Agent server provides runtime support for the Location Service Daemon (LSD), file transferring and synchronization, JMX server, distributed logging, naming server, security server, and EJB workload management configuration.
The Deployment Manager provides runtime support for WLM services, file transferring and synchronization, configuration management, JMX server, distributed logging, naming server, security server, and for the master configuration.
Figure 10-1 WebSphere Deployment Manager and Node Agent for configuration administration and application bootstrapping
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.