The ATG distribution provides two VFSs that you might need to configure for switch deployments:

ConfigFileSystem

The ATG distribution provides ConfigFileSystem with the Publishing agent. As installed, ConfigFileSystem is configured for online deployments. In order to deploy personalization and scenario assets to the target, you must configure ConfigFileSystem on each ATG server for switch deployments.

To configure each ConfigFileSystem VFS for switch deployments, perform these steps on each target ATG server:

  1. Configure an instance of SwitchableLocalFileSystem by modifying ConfigFileSystem.properties as in the following example:

    $class=atg.vfs.switchable.SwitchableLocalFileSystem

    liveDirectory=
    {atg.dynamo.server.home}/PublishingAgent/deploymentconfig/live/
    config

    stagingDirectory=
    {atg.dynamo.server.home}/PublishingAgent/deploymentconfig/staging/
    config

    dataDirectory=
      {atg.dynamo.server.home}/PublishingAgent/deploymentconfig/data/
    config

    journaling=true
    updateListeners+=
      /atg/epub/monitor/PersonalizationConfigurationMonitor

    name1=firstDataStore
    name2=secondDataStore

    For detailed information on these properties, see SwitchableLocalFileSystem in Appendix B, Virtual File Systems.

    The following constraints apply:

    • If you specify a different live directory, make sure the directory is located within the application’s configuration path.

    • Do not set liveDirectory and stagingDirectory to directories that are on different UNIX partitions.

  2. Place the new ConfigFileSystem.properties file in:

    <ATG9dir>/home/localconfig/atg/epub/file/

  3. Add the ConfigFileSystem to the DeploymentAgent’s list of switchable data stores by setting the property switchableDataStores in:

    <ATG9dir>/home/localconfig/atg/epub/DeploymentAgent.properties

    Specify the ConfigFileSystem by its fully qualified Nucleus path:

    /atg/epub/file/ConfigFileSystem

WWWFileSystem

The ATG distribution provides WWWFileSystem with the Publishing Web agent. As installed, it is configured for online deployments. If you install the Publishing Web agent on the target Web servers for deployment of deploy static text and binary files, you can configure the WWWFileSystem on each Web server for switch deployments.

To configure each WWWFileSystem VFS for switch deployments, perform these steps on each target Web server:

  1. Configure an instance of SwitchableLocalFileSystem by modifying WWWFileSystem.properties as in the following example:

    $class=atg.vfs.switchable.SwitchableLocalFileSystem

    liveDirectory=
    {atg.dynamo.home}/docstagingDirectory={atg.dynamo.server.home}/PublishingWebAgent/deploymentdocroot/staging

    dataDirectory=
    {atg.dynamo.server.home}/PublishingWebAgent/deploymentdocroot/data

    name1=firstDataStore
    name2=secondDataStore

    For detailed information on these properties, see SwitchableLocalFileSystem in Appendix B, Virtual File Systems.

    The following constraints apply:

    • If you set the liveDirectory property to a different directory, make sure the directory is located in the Web server’s document root directory or one of its subdirectories.

    • The directory must not store files used by other services; it should contain only files deployed from the asset management server’s WWWFileSystem.

    • Do not set liveDirectory and stagingDirectory to directories that are on different UNIX partitions.

  2. Place the new WWWFileSystem.properties file in:

    <ATG9dir>/home/localconfig/atg/epub/file/

  3. Add the WWWFileSystem to the DeploymentAgent’s list of switchable data stores by setting the agent’s property switchableDataStores in:

    <ATG9dir>/home/localconfig/atg/epub/DeploymentAgent.properties

    Be sure to specify the ConfigFileSystem by its fully qualified Nucleus path:

    /atg/epub/file/ConfigFileSystem

Configure VFSs on a new ATG server for switch deployment

When adding an ATG server or Web server to an existing target, configure its switchable VFSs like those on the existing ATG target servers. Verify that:

 
loading table of contents...