You can synchronize servers and application components from EAServer Manager or by using the jagtool sync command.
Synchronizing a cluster
from EAServer Manager
Use EAServer Manager to connect to the source (primary) server.
Depending on the level of the sync operation, highlight a cluster, server, package, servlet, or component.
Synchronization is enabled for servers, packages, and
components for any EAServer edition. Cluster synchronization is
enabled only for the Enterprise Edition. The cluster options display
in the Synchronize dialog for any object, but are disabled if the
Enterprise Edition is not licensed.
Select File | Synchronize.
Supply the synchronization information in the Synchronization dialog and click Start Sync. Table 6-1 describes the synchronization properties.
A server is in Admin mode if it is running and accepting connections from EAServer Manager, but not accepting ordinary client connections. A server in Admin mode can be the target of synchronization, since this is often the appropriate way to get it out of Admin mode. EAServer Manager warns you if you connect to a server that is running in Admin mode. You can force a server into Ready mode as described in “Switching to Ready mode”, but you should understand why the server is in Admin mode before you use this option.
Property |
Description |
Comments |
|---|---|---|
Username |
The user name used to log in to the remote servers. |
The user must belong to the Admin Role to use the synchronize option. |
Password |
The password for the user name on the remote servers. |
When synchronizing to multiple remote servers, including cluster members, all remote servers must use the same password to allow connection to those servers. |
Cluster |
Click the Cluster check box and select a cluster from the drop-down list to synchronize the entire cluster. |
If you are synchronizing a server, package, component, or servlets, you can specify that the changes be replicated to all servers in a cluster. Use this option only when connected to the cluster's primary server, or when connected to a nonprimary server that becomes the primary after synchronization. |
Servers |
Click the Servers check box and supply a list of one or more URLs to be targets of synchronization if you want to synchronize a subset of the cluster. |
The URLs must be separated
by a comma, and of the form |
All Web App Files |
When this option is selected, all Web application files are distributed to the remote servers. |
See “Web application synchronization” for more information. |
Synchronize Java Classes |
Applies to Web application synchronization only. Specifies whether to synchronize Java classes listed in the Web application’s custom class list specified on the Java Classes tab in the EAServer Manager Web Application Properties dialog box. |
|
All Package Files |
When this option is selected, all of the package files are distributed to the remote servers. Package files refers to all user-defined IDL files, property files, and implementation files (Java .class, .dll, .so, .pbd) based on component definitions. |
Selecting this option may result in the synchronization taking a long time, depending on the number of files being transferred to the remote server(s). Consider using component-level synchronization if only a few components have been changed. See “Component synchronization” and “Package synchronization” for more information. |
All Servlet Files |
When this option is selected, all servlet files are distributed to the remote servers. |
See “Servlet synchronization” for more information. |
All App Files |
When this option is selected, all application files are distributed to the remote servers. |
See “Application synchronization” for more information. |
All Connector Files |
When this option is selected, all connector files are distributed to the remote servers. |
|
All Files Matching the Wildcard Pattern |
When this option is selected, all files that match the wildcard pattern you enter in the adjacent field are distributed to the remote servers. |
|
Verbose |
Run in verbose mode. |
|
Refresh |
If you select this option, the servers you are synchronizing refresh when synchronization completes. |
|
Restart |
If you select this option, the servers you are synchronizing restart when synchronization completes. |
A timeout is used so that if a remote server does not restart, the synchronization moves to the next server. |
Then Wait |
This is the amount of time that the primary waits for a server to restart if you have selected the Restart option. |
Overriding synchronization operations
You may want to manually configure properties on individual servers in a cluster to override properties from the logical server definition. For example, you may want to:
Increase the size of a connection cache on a machine that has more memory than other machines.
Establish a process for making manual updates after each EAServer Manager synchronization.
