Synchronize nodes with the wsadmin tool

Synchronize nodes with the wsadmin tool

+
Search Tips | Advanced Search

Overview

You can propagate node changes using scripting and the wsadmin tool.
A node synchronization is necessary in order to propagate configuration changes to the affected node or nodes. By default, this situation occurs periodically, as long as the node can communicate with the deployment manager. You can propagate changes explicitly by performing the following steps:

Procedure
Set the variable for node synchronization.
Use Jacl:
set Sync1 [$AdminControl completeObjectName type=NodeSync,node=myNodeName,*]
Use Jython:
Sync1 = AdminControl.completeObjectName('type=NodeSync,node=myNodeName,*')
where:

set Jacl command
Sync1 variable name
$ Jacl operator for substituting a variable name with its value
AdminControl object that enables the manipulation of MBeans running in a WAS process
completeObjectName AdminControl command
type=NodeSync,node=myNodeName fragment of the object name. The complete name is returned by this command. This fragment is used to find the matching object name which is the SyncNode object for the myNodeName node, where myNodeName is the name of the node that you use to synchronize configuration changes. For example: type=Server, name=serv1. It can be any valid combination of domain and key properties. For example, type, name, cell, node, process, and so on.

Example output:
WebSphere:platform=common,cell=myNetwork,version=5.0,name=node
Sync,mbeanIdentifier=nodeSync,type=NodeSync,node=myBaseNode, process=nodeagent
Synchronize the node by issuing the following command:
Use Jacl:
$AdminControl invoke $Sync1 sync
Use Jython:
AdminControl.invoke(Sync1, 'sync')
where:

$ Jacl operator for substituting a variable name with its value
AdminControl object that enables the manipulation of MBeans that run in a WAS process
invoke AdminControl command
Sync1 evaluates the ID of the server that is specified in step number 1
sync attribute of modify command

Example output:
true
You receive an output value of true, if the synchronization completes.
Results

When the synchronization is complete, the files that are created in the c:/WebSphere/DeploymentManager/config directory now exists on the mynode node in the c:/WebSphere/AppServer/config directory.

Use the AdminConfig object for scripted administration
Manage nodes

Related Reference

Commands for the AdminConfig object

set	Jacl command
Sync1	variable name
$	Jacl operator for substituting a variable name with its value
AdminControl	object that enables the manipulation of MBeans running in a WAS process
completeObjectName	AdminControl command
type=NodeSync,node=myNodeName	fragment of the object name. The complete name is returned by this command. This fragment is used to find the matching object name which is the SyncNode object for the myNodeName node, where myNodeName is the name of the node that you use to synchronize configuration changes. For example: type=Server, name=serv1. It can be any valid combination of domain and key properties. For example, type, name, cell, node, process, and so on.