Configure Switch Deployment on the ATG Content Administration Server

Follow these steps to set up switch deployment on the ATG Content Administration server.

  1. Set up the appropriate Nucleus components for a SwitchingDataSource. SwitchingDataSources must be configured on the ATG Content Administration server for each destination repository and must point to the target databases. See the diagram in Destination Repositories, which shows a switch deployment configuration.

  2. In the Nucleus component that configures atg.service.jdbc.SwitchingDataSource, configure the dataSources property so it uses the same data source names configured on the agents in the appropriate target.

  3. Set the SwitchingDataSource.initialDataSourceName property to the data source that is not the one specified in the initialDataSourceName on the target servers. This behavior ensures that you are deploying to the inactive database on the target server.

For example, the properties file /atg/dynamo/service/jdbc/SwitchingDataSource.properties for the ATG Content Administration server might look like this:

$class=atg.service.jdbc.SwitchingDataSource
dataSources=\
FirstDataSource=/atg/dynamo/service/jdbc/FirstDataSource,\
SecondDataSource=/atg/dynamo/service/jdbc/SecondDataSource
initialDataSourceName=SecondDataSource
Configuring a multi-server cluster

In order to enable Switch Deployment from a multi-server cluster, each server must be configured with contact data about the other servers in the cluster. For more information, see Configure a Cluster for Switch Deployment.

 
loading table of contents...