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 Oracle Commerce Platform instance on each machine as the master instance. Other instances are considered slave targets and use the
ConfigFileSystemon the master instance.From the class
atg.vfs.switchable.SwitchableLocalFileSystem, configure a masterConfigFileSystem.propertiesfile:../localconfig/atg/epub/file/ConfigFileSystem.propertiesFrom the class
atg.vfs.switchable.SlaveLocalFileSystemService, configure identical slaveConfigFileSystem.propertiesfiles:../localconfig/atg/epub/file/ConfigFileSystem.propertiesConfigure the master
ConfigFileSystemas a switchable data store:On the master instance:
../localconfig/atg/epub/DeploymentAgent.propertiesSet the property
switchableDataStores:switchableDataStores+=/atg/epub/file/ConfigFileSystem
Create the following, depending on your type of operating system:
Windows - Create a shortcut from the master’s PublishingAgent
deploymentconfigLinux/UNIX - Create a symbolic link master’s PublishingAgent
deploymentconfigdirectory to each slave’s PublishingAgent directory (Ensure that you do not including the trailing slash):ln -s [PATH_TO_MASTER_DEPLOYMENTCONFIG_DIR]
[PATH_TO_SLAVE_DEPLOYMENTCONFIG_DIR]
Perform a full deployment to synchronize the new data directories with the asset management server.
To allow deployments to occur when non-essential agents are not running, you set the /atg/epub/DeploymentServer.allowMissingNonEssentialAgents to true using the BCC. By default, this property is set to false.
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
journalDirectory={serverHomeDirResource?resourceURI=PublishingAgent/deployment
config/data/config}
$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\\atg11.2\\home\\servers\\target- primary\\PublishingAgent\\deploymentconfig\\live\\config journalDirectory=c:\\atg\\atg11.2\\home\\servers\\target-primary\\ PublishingAgent\\deploymentconfig\\data\\config\\journal statusFile=c:\\atg\\atg11.2\\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 in 2 minutes
