|
|
In WebSphere V5 and higher, each individual node is "added" to the Deployment Manager cell. The Deployment Manager holds the cell's master configuration repository in the form of XML files. A subset of the master repository (related to a node's configuration) is then replicated to all the nodes in the cell. The Deployment Manager keeps all copies of the configuration files synchronized across all nodes. During normal operation, the Deployment Manager consistently synchronizes the repository data on each node with the master repository. The Deployment Manager also synchronizes application binaries to all appservers in a cluster (through the Node Agent).
You can turn synchronization on or off and change configuration parameters to tune synchronization using the Administrative Console (System Administration | Node Agents | Node_Agent_Name | File synchronization service).
WebSphere V6 also provides the option to synchronize copies of the repository and application binaries manually by using the syncNode command:
syncNode deploymgr_host deploymgr_port [options]
You can also use the Administrative Console (System administration | Nodes) as shown in Figure 3-1.
Figure 3-1 Node synchronization in the Administrative Console
If the Deployment Manager is not available, the repository cannot be synchronized. However, use wsadmin commands to change the configuration at the node level directly. Be aware that repository files across all nodes in the domain might become inconsistent or stale when doing so. When the Deployment Manager comes online again, all changes made locally to Node Agents or appservers are lost and are overwritten with the master repository.
