|
Problem(Abstract) |
Description of Synchronization for V5 releases. |
|
|
|
Cause |
Clarification |
|
|
Resolving the
problem |
The synchronization status reflected on the Administrative Console is
based on the following settings:
- Startup Synchronization
If this option is enabled, the node agent attempts to synchronize the node
configuration with the latest configurations in the master repository
prior to starting an application server. The default is not to synchronize
files prior to starting an Application Server. Enabling the setting
ensures that the node agent has the latest configuration, but increases
the amount of time it takes to start the Application Server.
This setting has no effect on the startServer command. The startServer
command launches a server directly and does not use the node
agent.
- Automatic Synchronization
If this option is enabled, synchronization occurs automatically after the
node agent starts and subsequently at the interval designated by the
Synchronization Interval option. The status of synchronization is reported
on the console. When automatic synchronization is disabled, the status of
the node is always Not Synchronized on a node restart. The value is
changed to synchronized only after the first synchronization of the node
agent.
This option can affect server behavior. Depending on what has changed with
applications, servers or their applications might be restarted across the
cell in an uncoordinated fashion based on the sync interval for each
node.
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. Use this command only when you cannot run the node
agent because the node configuration is damaged. You must run this command
from the $WAS_ROOT/bin directory of the WebSphere Application Server
installation.
Since the syncNode command runs as a command line utility and not in the
node agent, it does not affect the synchronization status for the node
that is displayed in the console. The synchronization status in the
console is not updated until the node agent performs a
synchronization. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|