This article only applies to network deployment installations. A node synchronization is necessary in order to propagate configuration changes to the affected node or nodes. By default this occurs periodically, as long as the node can communicate with the deployment manager. It is possible to cause this to happen explicitly by performing the following steps:
set Sync1 [$AdminControl completeObjectName type=NodeSync,node=myNodeName,*]
Sync1 = AdminControl.completeObjectName('type=NodeSync,node=myNodeName,*')
where:
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 server process |
completeObjectName | is an AdminControl command |
type=NodeSync,node=myNodeName | is a fragment of the object name whose complete name is returned by this command. It is used to find the matching object name which is, in this case, the SyncNode object for the node myNodeName, 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, etc. |
WebSphere:platform=common,cell=myNetwork,version=5.0,name=node Sync,mbeanIdentifier=nodeSync,type=NodeSync,node=myBaseNode, process=nodeagent
$AdminControl invoke $Sync1 sync
AdminControl.invoke(Sync1, 'sync')
where:
$ | 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 server process |
invoke | is an AdminControl command |
Sync1 | evaluates to the ID of the server specified in step number 7 |
sync | is an attribute of modify objects |
trueYou will receive an output value of true if the synchronization completes.
When the synchronization is complete, the files that are created in the Deployment Manager's config directory and are associated with myNodeName now exist in the config directory of myNode's node.
Related reference
AdminConfig object for scripted administration
Commands for the AdminConfig object