Deployments performed in switch mode require two databases, where repository assets are updated on the target site’s inactive database while its live database runs undisturbed. These databases should begin with identical content, which you can ensure in one of two ways:
Use the tools provided by your database vendor to make the second database identical to the first database.
After you configure the target for switch deployments, perform a full deployment to the target.
Definition files of the target site repositories must not contain operation tags such as <add-item>, <update-item>, and <remove-item>. These tags cause switch deployments to fail.
Perform the following steps on the target site ATG servers:
Configure data sources that connect to the two databases.
Configure a SwitchingDataSource to switch between the two underlying data sources.
Configure repository components to point to the SwitchingDataSource. Also, set each repository component’s
cacheSwitchHotproperty totrue.Add the SwitchingDataSource to the DeploymentAgent’s list of switchable data stores. To this, set the property
switchableDataStoresto the SwitchingDataSource’s fully qualified Nucleus path, in:<ATG9dir>/home/localconfig/atg/epub/DeploymentAgent.properties
Note: For detailed information on steps 1-3, see the ATG Installation and Configuration Guide.
Configuring a new ATG server for switch deployment
When adding an ATG server to an existing target, configure its repositories and SwitchingDataSource like those on the existing ATG target servers. Verify that:
It has the same underlying data sources.
Its initial data source is the same as their current data source, so the new server’s agent application starts up using the same data source.
