Why and when to perform this task
This article applies to network deployment installations only. 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:Steps for this task
Using Jacl:
set Sync1 [$AdminControl completeObjectName type=NodeSync,node=myNodeName,*]
Sync1 = AdminControl.completeObjectName('type=NodeSync,node=myNodeName,*')
set | is a Jacl command |
Sync1 | is a variable name |
$ | is a Jacl operator for substituting a variable name with its value |
AdminControl | is an object that enables the manipulation of MBeans running in a WebSphere Application Server process |
completeObjectName | is an AdminControl command |
type=NodeSync,node=myNodeName | is a 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. |
WebSphere:platform=common,cell=myNetwork,version=5.0,name=node Sync,mbeanIdentifier=nodeSync,type=NodeSync,node=myBaseNode, process=nodeagent
Using Jacl:
$AdminControl invoke $Sync1 sync
AdminControl.invoke(Sync1, 'sync')
$ | is a Jacl operator for substituting a variable name with its value |
AdminControl | is an object that enables the manipulation of MBeans that run in a WebSphere Application Server process |
invoke | is an AdminControl command |
Sync1 | evaluates the ID of the server that is specified in step number 1 |
sync | is an attribute of modify command |
trueYou receive an output value of true, if the synchronization completes.
Result
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.