You 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 deployment manager. You can propagate changes explicitly by running commands that synchronize the configuration.
When the synchronization is complete, the files that are created in the config directory for the deployment manager now exist on the myNodeName node in the app_server_root/config directory.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) |