If you are not familiar with synchronization, check out our Getting Started article.
With a partial synchronization, only files that the deployment manager thinks have changed will be synchronized. A partial synchronization takes less time than a full synchronization.
After selecting Synchronize, message "successfully initiated synchronization" should be displayed.
The managed node can also be synchronized using the syncNode.sh (Linux) or syncNode.bat (Windows) command. You will run this command from the server that contains the node that you want to sync with the deployment manager. Before issuing the syncNode.sh / syncNode.bat command, you will need to issue the stopNode.sh / stopNode.bat command.
Once the node has been stopped, you can then issue the syncNode.sh command. In this example, "example.com" is the hostname of the deployment manager, and 8879 is the SOAP port of the deployment manager. 8879 is the default SOAP port. To be absolutely certain that you have the correct port, check the was_home/profiles/your_profile/properties/portdef.props file on the dmgr.
~]# was_home/AppServer/profiles/your_profile/bin/syncNode.sh example.com 8879
After the node has been sycned, start the node.
The managed node can also be synchronized using the wsadmin command. In this example, a variable named myNode which is associated with Node01, and then the node is synchronized.
# Jacl set myNode [$AdminControl completeObjectName type=NodeSync,process=nodeagent,node=Node01,*] $AdminControl invoke $myNode sync # Jython myNode = AdminControl.completeObjectName('type=NodeSync,process=nodeagent,node=Node01,*') AdminControl.invoke(myNode, 'sync')