SyncNode command

The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.

The node agent server runs a configuration synchronization service that keeps the node configuration synchronized with the master cell configuration. If the node agent is unable to run because of a problem in the node configuration, you can use the syncNode command to perform a synchronization when the node agent is not running in order to force the node configuration back in sync with the cell configuration. If the node agent is running and you want to run the syncNode command, you must first stop the node agent.

The syncNode.log file is located in the profile_root/logs directory.

For more information about where to run this command, see the Using command tools topic.

Syntax

The command syntax is as follows:

syncNode <deploymgr host> <deploymgr port> [options]

• The <deploymgr host> argument is required.
• The <deploymgr port> is the Java Management Extensions (JMX) port number that corresponds to the connector type on the -conntype parameter.

Parameters

The following options are available for the syncNode command:

-stopservers

Tells the syncNode command to stop all servers on the node, including the node agent, before performing configuration synchronization with the cell.

-restart

Tells the syncNode command to launch the node agent process after configuration synchronization completes. If the node agent is running and you want to run the syncNode command, you must first stop the node agent.

-nowait

Tells the syncNode command not to wait for successful initialization of the launched node agent process.

-quiet

Suppresses the progress information that the syncNode command prints in normal mode.

-logfile <fileName>

Specifies the location of the log file to which trace information is written. By default, the log file is named syncNode.log and is created in the logs directory of the profile for the node that you are synchronizing.

-profileName  

Defines the profile of the Application Server process in a multi-profile installation. The -profileName option is not required for running in a single profile environment. The default for this option is the default profile.

-replacelog

Replaces the log file instead of appending to the current log.

-trace

Generates trace information into a file for debugging purposes.

-timeout <seconds>

Specifies the waiting time before node agent initialization times out and returns an error.

-username <name>

Specifies the user name for authentication if security is enabled. Acts the same as the -user option.

-user <name>

Specifies the user name for authentication if security is enabled. Acts the same as the -username option.

-password <password>

Specifies the password for authentication if security is enabled.

-conntype <type>

Specifies the Java Management Extensions (JMX) connector type to use for connecting to the deployment manager. Valid types are SOAP or Remote Method Invocation (RMI). The default type is SOAP.

-help

Prints a usage statement.

-?

Prints a usage statement.

Usage scenario

The following examples demonstrate correct syntax:

 

syncNode testhost 8879

syncNode deploymgr 8879 -trace (produces the syncNode.log file)

syncNode host25 4444 -stopservers -restart

(assumes that the deployment manager JMX port is 4444)

syncNode.sh testhost 8879

syncNode.sh deploymgr 8879 -trace (produces the syncNode.log file)

Case:

Note: Before running syncNode command

1. Ensure that the Deployment Manager is running on the specified host and port

2. The syncNode command may only be run when the node agent is stopped

Case 1: when dmgr, app server, nodeagent in stop status —->

<appsrv-home>/bin> syncNode.bat  <dmgr-host> <dmgr_soap_port> -username xxx  -password xxxxx

O/P:

ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv60\logs\syncNode.log
ADMU0128I: Starting tool with the AppSrv60 profile
ADMU0113E: Program exiting with error:
com.ibm.websphere.management.exception.ConnectorException:
ADMC0016E: The system cannot create a SOAP connector to connect to
host localhost at port 8879., resulting from:
java.lang.reflect.InvocationTargetException
ADMU4123E: Ensure that the Deployment Manager is running on the specified host and port.
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU0211I: Error details may be seen in the file: C:\Program
Files\IBM\WebSphere\AppServer/profiles/AppSrv60\logs\syncNode.log

————————————————

Case 2: dmgr , nodeagent start state —>

syncNode.bat dmgr-host 8879

O/P:

ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv60\logs\syncNode.log
ADMU0128I: Starting tool with the AppSrv60 profile
ADMU0401I: Begin syncNode operation for node anode60 with Deployment Manager
localhost: 8879
ADMU0403E: The syncNode command may only be run when the node agent is stopped.
Either stop the node agent or use the normal synchronization
facility in the node agent.

—————————————————

Case 3: To do sync—> dmgr,server1 is start and nodeagent in stop—> running syncNode

O/P:

ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv60\logs\syncNode.log
ADMU0128I: Starting tool with the AppSrv60 profile
ADMU0401I: Begin syncNode operation for node anode60 with Deployment Manager
localhost: 8879
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node anode60 has been synchronized with
Deployment Manager localhost: 8879