Operating Systems: i5/OS
             Personalize the table of contents and search results

 

Synchronizing nodes with the wsadmin tool

 

You can propagate node changes using scripting and the wsadmin tool.

 

Overview

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:

 

Procedure

  1. Set the variable for node synchronization.

    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 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.

    Example output:

    WebSphere:platform=common,cell=myNetwork,version=5.0,name=node
    Sync,mbeanIdentifier=nodeSync,type=NodeSync,node=myBaseNode,
    process=nodeagent
    

  2. Synchronize the node by issuing the following command:

    where:

    $ 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

    Example output:

    true
    You receive an output value of true, if the synchronization completes.

 

Results




}
Using the AdminConfig object for scripted administration
Managing nodes

 

Related Reference


Commands for the AdminConfig object