The Dynamo Application Framework includes a deployment system you can use to deploy repository and file-based assets from one server cluster to another, for example from a development environment to a cluster that represents a staging or production site. DAF deployments are designed to optimize performance and scalability by using multi-threading in a multi-server configuration. Error recovery is supported; you can resume a deployment after an error occurs, or after a deployment is halted manually, without having to restart the entire operation. If your deployment setup includes ATG Content Administration, you can also roll the target site back to a previous state.
DAF Deployment is designed to be used as a replacement for ATG Content Administration’s manifest-based deployment mechanism as it is especially suited for sites where content updates are frequent or involve very large numbers of assets. Non-ATG Content Administration environments can also use the DAF Deployment API to build asset distribution into custom code. (Note, however, that without ATG Content Administration, DAF Deployment can be used only as an API. No asset management or deployment UI is available in this case.)
Non-Versioned Deployment: DAF Deployment can be used to deploy content from one or more non-versioned GSA repositories. Multiple source repositories can be deployed, in which case each source repository must have a corresponding target repository. Similarly, the DAF Deployment system can be used to deploy file items from one or more non-versioned VirtualFileSystems to corresponding target VirtualFileSystems.
Versioned Repository Deployment: The DAF Deployment system can also be used to deploy versioned data created with ATG Content Administration. It can deploy versioned repository data to target non-versioned repositories or to target VirtualFileSystems. For more information on repository and file assets, VirtualFileSystems, and versioned data, refer to the ATG Content Administration Programming Guide.
Selective Deployment: The repository-to-repository architecture of DAF Deployment allows you to deploy different data to each target (a feature not available with ATG Content Administration’s manifest-based deployment, where all targets must receive the same data). For more information, see Using DAF Deployment to Deploy to Multiple Sites.
This chapter contains the following sections:
