Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin) > Use the wsadmin scripting AdminControl object for scripted administration
Synchronize nodes using wsadmin.sh
We can propagate node changes using scripting and the wsadmin tool.
There are two ways to complete this task. This topic uses the AdminControl object to synchronize nodes. Alternatively, you can use the node administration scripts in the AdminNodeManagement script library to synchronize a specific node, or to synchronize all active nodes.
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 dmgr. We can propagate changes explicitly by running commands that synchronize the configuration.
### Jacl set Sync1 [$AdminControl completeObjectName type=NodeSync,node=myNodeName,*] $AdminControl invoke $Sync1 sync ### Jython Sync1 = AdminControl.completeObjectName('type=NodeSync,node=myNodeName,*') AdminControl.invoke(Sync1, 'sync')You receive an output value of true, if the synchronization completes.
Results
When the synchronization is complete, the files that are created in the config directory for the dmgr now exist on the myNodeName node in...
WAS_HOME/config
Use the wsadmin scripting AdminConfig object for scripted administration
Manage nodes
Related
Node administration scripts
Commands for the AdminConfig object using wsadmin.sh