The servers that comprise an ATG Content Administration cluster can either run on the same host machine, or be distributed across different hosts.
If all servers run on the same host, you can set the location of file asset storage for all servers to a common location as follows:
Create a
publishingFiles.xml
file with a newpathPrefix
attribute that overrides the default.Put the file in your application’s configuration path.
For detailed information, see Changing File Asset Storage Location.
If the cluster servers are distributed across different host machines, you must coordinate file asset storage and access. You can do so in several ways:
Use a storage area network (SAN) and make the location of the
versionFileStore
exist on the SAN.Use
rsync
to synchronize all directories on each server.Use a network file system (NFS) and make the location of the
versionFileStore
exist on the SAN.If none of the aforementioned methods are available, synchronize file assets with the
FileSynchronizationDeployServer
component as described in the next section.
Synchronizing Distributed Files with FileSynchronizationDeployServer
If enabled, the FileSynchronizationDeployServer
component synchronizes distributed files whenever a given file is required by any server on the cluster. In order to use this component, you must set properties on it and on /atg/epub/Configuration
, as follows:
/atg/epub/file/synchronization/FileSynchronizationDeployServer
:
Property | Setting |
---|---|
|
|
| The desired listener port number, set by reference to |
/atg/epub/Configuration
:
For example:
remoteHosts=\ jupiter.acme-widgets.com,\ saturn.acme-widgets.com,\ uranus.acme-widgets.com remoteRMIPorts=\ 8860,\ 8860,\ 8860 remotePorts=\ 8815,\ 8815,\ 8815