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 master ConfigFileSystem on one VM and slave ConfigFileSystems on the others, so only one VM on a given machine is responsible for file deployments. This configuration can significantly increase performance because deployment data, which can be very large, is sent to one agent rather than all agents.
Note: A shared ConfigFileSystem is supported for switch mode deployments only.
To set up a shared ConfigFileSystem deployment model:
Designate one ATG instance on each machine as the master instance. Other ATG instances are considered slave targets and use the ConfigFileSystem on the master instance.
From the class
atg.vfs.switchable.SwitchableLocalFileSystem, configure a master ConfigFileSystem.properties file:../localconfig/atg/epub/file/ConfigFileSystem.propertiesFrom the class
atg.vfs.switchable.SlaveLocalFileSystemService, configure identical slave ConfigFileSystem.properties files:../localconfig/atg/epub/file/ConfigFileSystem.propertiesConfigure the master ConfigFileSystem as a switchable data store:
On the master instance:
../localconfig/atg/epub/DeploymentAgent.propertiesSet the property
switchableDataStores:switchableDataStores+=/atg/epub/file/ConfigFileSystem
Perform a full deployment to synchronize the new data directories with the asset management server.
Master ConfigFileSystem.properties
The following sample shows a ConfigFileSystem.properties file on the master instance:
Note: Paths are machine-specific.
#$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=VFSName2Slave ConfigFileSystem.properties
The following sample shows a ConfigFileSystem.properties file for slave instances:
Note: Paths are machine-specific.
$class=atg.vfs.switchable.SlaveLocalFileSystemService # references to SwitchableLocalFileSystem rootDirectory=c:\\atg\\atg10.1.1\\home\\servers\\target- primary\\PublishingAgent\\deploymentconfig\\live\\config journalDirectory=c:\\atg\\atg10.1.1\\home\\servers\\target- primary\\PublishingAgent\\deploymentconfig\\data\\config\\journalBackup statusFile=c:\\atg\\atg10.1.1\\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
