For deployment, the ATG Content Administration server must have a data source configured to point to each target server’s database. This section describes how to configure the data source and create destination repositories, which are repositories on the ATG Content Administration server that point to target site databases. For more about the relationship between data source and the destination repositories, see Destination Repositories.

Before you start this configuration, determine the number of repositories on each deployment target. The example that follows assumes two targets: staging and production. Each target has two repositories, productCatalog and priceLists, which correspond to two versioned repositories on the ATG Content Administration server. Thus configured, the environment requires ten repositories, as shown in the following table.

Repository name

Type

Server

productCatalog

versioned

ATG Content Administration

priceLists

versioned

ATG Content Administration

productCatalog_staging

destination

ATG Content Administration

priceLists_staging

destination

ATG Content Administration

productCatalog_production

destination

ATG Content Administration

priceLists_production

destination

ATG Content Administration

productCatalog

target

staging

priceLists

target

staging

productCatalog

target

production

priceLists

target

production

Given this configuration, complete the following steps:

 
loading table of contents...