The syncNode script

The syncNode script allows you to manually synchronize the configuration between a single node and the deployment manager for the cell that the node belongs to. The master copy of the configuration documents for the node are copied from the deployment manager cell to the node. Before you run the syncNode script, the node agent and all servers for the node must be stopped. Use this script only if you cannot run the node agent because the node configuration does not match the cell configuration.

Product

The syncNode script is available with the WebSphere Application Server product only.

Authority

To run this script, your user profile must have *ALLOBJ authority.

Syntax

The syntax of the syncNode script is:

syncNode dmgr_host [ dmgr_port ] [ -instance instance ]
 [ -conntype type ] [ -stopservers ] [ -restart ] [ -quiet ] [ -nowait ]
 [ -logfile filename ] [ -replacelog ] [ -trace ] [ -username username ]
 [ -password password ] [ -help | -? ]

Parameters

The parameters of the syncNode script are:

• dmgr_host
  This is a required parameter. The value dmgr_host specifies the name of the machine that hosts the deployment manager for the cell that contains the node.

• dmgr_port
  Optional. The value dmgr_port specifies the SOAP or RMI port on which the deployment manager for the Network Deployment cell is listening. By default, the script reads the configuration file for the node to determine the port to use. If you specify a port other than the SOAP port for your deployment manager, specify the -conntype parameter. The deployment manager must be started and actively listening on the port specified for this parameter.

• -instance
  Optional. The value instance specifies the name of the instance associated with the node agent that you want to synchronize. The default value is default.

• -stopservers
  Optional. If you specify this parameter, the syncNode script stops all servers for the node and the node agent for the node before synchronizing the configuration. The default is to not stop the servers or node agent. If you are not sure that all servers and the node agent are stopped, it is recommended that you specify this parameter.

• -restart
  Optional. If you specify this parameter, the script starts the node agent process after the synchronization is complete. The default is to not start the node agent process.

• -nowait
  Optional. You can specify this parameter when you specify the -restart parameter. The -nowait parameter specifies that control should be returned immediately to the user after starting the node agent process. The default is to wait until the node agent process has successfully started before returning control to the caller.

• -quiet
  Optional. If you specify this parameter, the script does not display informational messages. The default is to display informational messages while the script runs.

• -logfile
  Optional. The value filename specifies the location and name of the log file for the script. The default value is /QIBM/UserData/WebAS5/Base/instance/logs/syncNode.log where instance is the name of the instance that contains the server that you want to stop.

• -replacelog
  Optional. If you specify this parameter, the script replaces the log file if it exists. By default the script appends to the log file if it exists.

• -trace
  Optional. If you specify this parameter, the script outputs additional trace information to the log file for the script. You should only specify this parameter if errors occur when you try to synchronize a node's configuration. The default is to not log additional trace information.

• -username
  Specifies the user name for authentication if security is enabled.

• -password
  Specifies the password for authentication if security is enabled.

• -conntype
  Specifies the Java Management Extensions (JMX) connector type to use for connecting to the deployment manager. Valid types are Simple Object Access Protocol (SOAP) or Remote Method Invocation (RMI).

• -help or -?
  This optional paramter prints the usage statement for the script.

Examples

These examples demonstrate correct syntax:

syncNode myiseries

This example synchronizes the configuration for the node associated with the default instance with the deployment manager for the cell to which the node belongs. In this example the deployment manager is running on the myiseries iSeries server in the default Network Deployment instance.

syncNode myiseries -instance mynode -restart

This example synchronizes the configuration for the node associated with instance mynode with the deployment manager running on the myiseries iSeries server in the default Network Deployment instance. The node agent process is automatically started after the synchronization is completed.

syncNode myiseries 11381 -restart -nowait

This example synchronizes the configuration for the node associated with the default instance with the deployment manager running on the myiseries iSeries server. In this example the deployment manager is running in a non-default Network Deployment instance and has a SOAP port of 11381. The node agent for the default instance is automatically started after the synchronization is completed, and control is returned immediately to the user.