The syncNode command forces a configuration synchronization to occur between the node and the dmgr 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, we 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, first stop the node agent.
The syncNode.log file is located in...$WP_PROFILE/logs
See about where to run this command, see the Use command tools article.
SyntaxThe 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.
The following options are available for the syncNode command:
- Tells the syncNode command to stop all servers on the node, including the node agent, before performing configuration synchronization with the cell.
- 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, first stop the node agent.
- Tells the syncNode command not to wait for successful initialization of the launched node agent process.
- Suppresses the progress information that the syncNode command prints in normal mode.
- -logfile <fileName>
- 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 we are synchronizing.
- Defines the profile of the appserver 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.
- Replaces the log file instead of appending to the current log.
- Generates trace information into a file for debugging purposes.
- -timeout <seconds>
- Waiting time before node agent initialization times out and returns an error.
- -username <name>
- User name for authentication if security is enabled. Acts the same as the -user option.
- -user <name>
- User name for authentication if security is enabled. Acts the same as the -username option.
- -password <password>
- Password for authentication if security is enabled.
- -conntype <type>
- Java Management Extensions (JMX) connector type to use for connecting to the dmgr. Valid types are SOAP or Remote Method Invocation (RMI). The default type is SOAP.
- Prints a usage statement.
- Prints a usage statement.
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 dmgr JMX port is 4444)
Remote file services
Synchronizing nodes with wsadmin