A DAF Deployment configuration requires you to add a destination repository on the ATG Content Administration server for every target repository that receives deployed data. A destination repository is a GSARepository instance that is configured to point to the database of the matching target site repository. Only repository asset deployment requires a destination repository. File assets are deployed directly from the ATG Content Administration server to the target sites over a TCP connection.
The following graphic shows an ATG Content Administration environment that is configured with one versioned source repository, and two target sites, staging and production. A destination repository is configured on the ATG Content Administration server to match each target repository. In this case, two destination repositories are configured, one for staging and another for production. The destination repositories are not versioned.
This example shows a deployment environment that is configured for switch deployments. For each repository on the content development server—staging and production—the environment includes a SwitchingDataSource that corresponds to each SwitchingDataSource on the destination server. See Configure Switch Deployment for more information.
As part of the deployment setup process for ATG Content Administration, you need to create and configure destination repositories (see Configure Deployment Data Sources and Destination Repositories). Later, when you set up deployment topology, you specify mappings between the source and destination repositories.
