The DAF Deployment architecture allows you to deploy from a single ATG server to multiple sites, including multiple sites on a single target. To do so, follow the steps in Setting Up DAF Deployment for a Single ATG Server, creating corresponding repositories on the target server or servers for each repository that you want to deploy from the ATG server. For data that you do not want to deploy to a particular site or target, do not set up a matching repository on the target. The data will not be deployed if no matching repository exists.
Note that any repositories that have data dependencies, for example items that have links to other assets, must be deployed together.
The diagram below shows two target sites, Production Site 1 and Production Site 2, that have different data supplied by a single ATG server instance. On Production Site 1, there is no matching repository for the Repository C that is configured on the source, so this target site does not receive Repository C data. Similarly, Repository A is not configured on Production Site 2, so this target does not receive data for Repository A.
Note that DAF Deployment does not support the deployment of different data from multiple ATG servers to a single target.
