ATG Content Administration uses the multi-threaded deployment features provided by the Dynamo Application Framework (DAF) to transfer data from the versioned source on the ATG Content Administration server to the target site. DAF deployment uses the JDBC driver to copy repository assets to the target, and a TCP connection to transfer file assets.

ATG Content Administration integrates with DAF deployment through the ATG Content Administration deployment API, whose starting point is the DeploymentServer. The DeploymentServer represents the core controller of all ATG Content Administration deployment operations and provides API access to the targets and agents where assets are deployed.

The deployment process can be outlined as follows:

Note: If the deployment process fails at any point, the DeploymentManager returns control to the ATG Content Administration deployment system. For more information on failure handling, see Deployment Recovery.

Enabling distributed deployments

By default, deployment events are sent locally and only to the server that initiated the deployment. If you want to use distributed deployment instead, so that deployment events are sent as JMS messages to any configured listener, set the DeploymentManager’s useDistributedDeployment property to true. For more information about distributed deployment, see Using DAF Deployment in the ATG Programming Guide.

Post-data transfer tasks

If the data transfer is successful, the ATG Content Administration deployment system performs these tasks:

DAF deployment architecture and its processes and phases are described in detail in the Using DAF Deployment chapter of the ATG Programming Guide.

 
loading table of contents...