File synchronization service settings
To specify that a file set on one node matches that on the central dmgr node and to ensure consistent configuration data across a cell.
We can synchronize files on individual nodes or throughout the system.
If wer installation includes mixed release cells, a large numbers of nodes, and runs a large number of applications, we might want to use the Generic JVM Arguments field, on the Java™ Virtual Machine Settings page of the admin console, to enable the hot restart sync feature of the synchronization service. This feature indicates to the synchronization service that the installation is running in an environment where configuration updates are not made when the dmgr is not active. Therefore, the service does not have to perform a complete repository comparison when the dmgr or node agent servers restart.
Do not routinely disable the synchronization process as various portions of the appserver run time depend on synchronization. For example, the security run time depends on node synchronization to propagate updated certificates during automated replacement processes. Also, the security runtime also depends on it for LTPA key changes. However, the only exception is the configuration save operation. To avoid synchronizing the configuration when the configuration repository is being updated by a save operation, it might be beneficial to temporarily disable the synchronization process, save the configuration, and then re-enable the synchronization process. This process ensures that changes are fully committed to the configuration repository before node synchronization.
To view this admin console page, click System Administration > Node agents > node_agent_name > File synchronization service.
- Enable service at server startup
Whether the server attempts to start the file synchronization service. This setting does not cause a file synchronization operation to start. This setting is enabled by default.
Data type Boolean Default true
- Synchronization Interval
Number of minutes that elapse between synchronizations. Increase the time interval to synchronize files less often. Decrease the time interval to synchronize files more often.
Data type Integer Units Minutes Default 1
The minimum value that the appserver uses is 1. If we specify a value of 0, the appserver ignores the value and uses the default of 1.
- Automatic Synchronization
Whether to synchronize files automatically after a designated interval. When this setting is enabled, the node agent automatically contacts the deployment manager every synchronization interval to attempt to synchronize the node's configuration repository with the master repository owned by the dmgr.
If the Automatic synchronization setting is enabled, the node agent attempts file synchronization when it establishes contact with the dmgr. The node agent waits the synchronization interval before it attempts the next synchronization.
Disablement of automatic synchronization is recommended in a production environment or if we use the application rollout update capability.
Remove the check mark from the check box to control when files are sent to the node.
Data type Boolean Default true
- Startup Synchronization
Whether the node agent attempts to synchronize the node configuration with the latest configurations in the master repository prior to starting an appserver.
The default is to not 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 appserver.
Note that this setting has no effect on the startServer command. The startServer command launches a server directly and does not use the node agent.
Data type Boolean Default false
- Exclusions
Specifies files or patterns that should not be part of the synchronization of configuration data. Files in this list are not copied from the master configuration repository to the node, and are not deleted from the repository at the node.
The default is to have no files specified.
To specify a file, use a complete name or a name with a leading or trailing asterisk (*) for a wildcard. For example:
Excludes this specific file Excludes files named file name in any context Excludes the subtree under dirname
Press Enter at the end of each entry. Each file name appears on a separate line.
Since these strings represent logical document locations and not actual file paths, only forward slashes are needed no matter the platform.
Changes to the exclusion list are picked up when the node agent is restarted.
Data type String Units File names or patterns
Related concepts
Remote file services
Related tasks
Set remote file services
Related
Java virtual machine settings Custom property collection