The Admin Console in the ATG Business Control Center lets you set up the target sites, agents, and agent responsibilities that define an ATG Content Administration deployment topology:
Assemble a Web application that includes ATG Content Administration server according to the instructions in the ATG Installation and Configuration Guide. Deploy the application to the appropriate server.
Access the ATG Business Control Center.
Log in as a user with access rights to the Admin Console (see Accessing the Admin Console).
In the Home page, under Content Administration click Admin Console.
From the Deployment Administration page, click Configuration.
Adding a Site
From the Configuration page, you can add one or more sites as follows:
Click Add Site.
Configure the new site by supplying data for the following fields:
Site Name: Supply the target site’s name—for example, Staging or Production. See Identify Deployment Target Sites for more information.
Site Initialization Options: Choose one of the following options:
Flag Agents Only: Select if the data on the target site was imported for use as the starting data for the versioned database on the ATG Content Administration server. If this is the case, you do not need to do a full deployment when you initialize this target, because you are sending the same data back to the target site. Flag Agents Only initializes the target with only data that changed since the original data was imported.
Do a Full Deployment: Select if the data on the target site is not the same as the versioned data on the ATG Content Administration server. This option guarantees that data is the same in both places, but be aware that a full deployment can take some time to complete.
Caution: If any projects are currently checked in when you initialize the target, and you select the Flag Agents Only option, all those projects are deployed immediately on initialization, including any marked as Deploy Later. This behavior occurs because the Flag Agents Only option deploys all data from the main versioning branch. If you do have any projects scheduled for later deployment, therefore, and deploying those projects immediately is undesirable, perform a full deployment instead. The behavior does not occur with the full deployment option.
Site Description: Enter text you can use to identify this target. The description appears in the Deployment Administration Overview list for this target. You can edit the description later if required.
Source Repository and Destination Repository lists let you provide mappings between this target’s source and destination repositories:
Choose a versioned source repository whose assets you wish to deploy to this target.
This list is populated with all versioned repositories in the CONFIGPATH. If the items you need do not appear, make sure all appropriate modules are included in your application.
Choose the matching destination repository on the ATG Content Administration server. This is the repository that is configured to point to the target server’s database; for more information, see Configure Deployment Data Sources and Destination Repositories.
Click Add. The mapping is added to the Source Repository list. To remove a mapping from this list, click X.
Click Save Changes.
The Deployment Administration Configuration page displays the new site.
Configuring Site Deployment Agents
From the Deployment Administration Configuration page, you configure deployment agents for each target site as follows:
Click the new site’s name.
Display the Agents tab.
Click Add Agent to Site
Supply data for the following fields:
Name: Supply this agent’s name—for example, Repository Agent. See Identify Deployment Agents for more information
Transport Type: Specify the agent’s transport type.
Transport URL: Specify the agent’s transport URL
Include Destinations: Use this field to define the deployment agent’s responsibilities: all assets, repository assets, file assets, or no assets. You populate this list from by moving items from Available Destinations:
Available Destinations shows possible asset destinations (repository or VFS) that an agent can be responsible for updating.
Include Destinations shows the asset destinations that you want the agent to update.
See Plan Deployment Agent Responsibilities for more information.
Be sure to assign each asset type (repository or VFS) or asset destination (identified by its name in Nucleus) that resides in a shared data store to only one agent that uses the data store.
If an agent has deployment responsibilities, the agent is considered essential for deployments to the target (see Essential and Unessential Agents).
Click Save Changes.
To add more agents for the site, repeat steps 2-5.
