Configure a Shared ConfigFileSystem for Multiple Targets

Optionally, you can configure an ATG Content Administration environment distributed across multiple VMs so it deploys to a single ConfigFileSystem. To do so, you create a target SwitchableLocalFileSystem in one VM and SlaveLocalFileSystemServices in other VMs, so only one VM per machine is responsible for file deployments. This configuration can significantly increase performance because it requires the deployment data, which can become very large, to be sent to only one target rather than to all targets.

Note: A shared ConfigFileSystem is supported for switch mode deployments only.

To set up a shared ConfigFileSystem deployment model:

  1. Designate one ATG instance on each machine as the master target. Other ATG instances are considered slave targets and use the file system on the master instance.

  2. Using the ConfigFileSystem.properties files (see below) as starting points, configure a master SwitchableLocalFileSystem in the localconfig of the master instance. Then configure identical SlaveLocalFileSystemServices in the localconfig in each of the other instances, or in /home/localconfig.

  3. In the master localconfig only, configure the SwitchableLocalFileSystem as a switchable data store. Create an /atg/epub/DeploymentAgent.properties file with the following line:

    switchableDataStores+=/atg/epub/file/ConfigFileSystem

  4. Perform a full deployment to synchronize the new data directories with the asset management server.

ConfigFileSystem.properties

Note: These sample property files have machine-specific paths in them that you will need to change. In all cases, however, the component’s Nucleus name must be: /atg/epub/file/ConfigFileSystem.

The following sample shows a ConfigFileSystem.properties file for the master instance:

#$class=atg.vfs.journal.JournalingFileSystemService
#virtualFileSystem=ConfigFileSystemLocal
#journalDirectory={serverHomeDirResource?resourceURI=PublishingAgent/
   deploymentconfig/data/config}
#clearJournalOnUpdate=true
#updateListeners+=/atg/epub/monitor/PersonalizationConfigurationMonitor

################################
#Use this configuration for a switch deployment

$class=atg.vfs.switchable.SwitchableLocalFileSystem
#
liveDirectory={serverHomeDirResource?resourceURI=PublishingAgent/
   deploymentconfig/live/config}
stagingDirectory={serverHomeDirResource?resourceURI=PublishingAgent/
   deploymentconfig/staging/config}
dataDirectory={serverHomeDirResource?resourceURI=PublishingAgent/
   deploymentconfig/data/config}
journaling=true
clearJournalOnUpdate=true
backupJournal=true
name1=VFSName1
name2=VFSName2

The following sample shows a ConfigFileSystem.properties file for slave instances:

$class=atg.vfs.switchable.SlaveLocalFileSystemService

# references to SwitchableLocalFileSystem
rootDirectory=c:\\atg\\atg9.3\\home\\servers\\
  target-primary\\PublishingAgent\\deploymentconfig\\live\\config
journalDirectory=c:\\atg\\atg9.3\\home\\servers\\
  target-primary\\PublishingAgent\\deploymentconfig\\data\\config\\
  journalBackup
statusFile=c:\\atg\\atg9.3\\home\\servers\\target-primary\\
  PublishingAgent\\deploymentconfig\\data\\config\\status.dat

# schedule for checking switch status to see if an update event is required
scheduler=/atg/dynamo/service/Scheduler
schedule=every 20 seconds
 
loading table of contents...