ATG Content Administration Programming Guide

A deployment topology requires you to determine which agents in a target are responsible for managing target assets. This is necessary because only one agent using a shared data store should manage the data store. For each agent, determine which repository or type of asset that agent will manage. The three examples that follow demonstrate the deployment responsibilities to assign to agents in various target configurations:

ATG Servers Share a Single Data Store

The following target includes two ATG servers that share a single data store.

While both deployment agents share the data store, only one is given responsibility for managing all data store assets, by selecting all available destinations in the UI or through the <principalasset>ALL</principalasset> tag in the topology XML file.

You can also assign deployment responsibilities by giving agent P2 responsibility for managing all repository assets. This is permissible because there are no VFS assets in the target.

If you expand this sample target to include a second cluster of ATG servers that uses a second data store, the responsibility for managing the second store must be given to an agent that uses it.

ATG Servers Use Shared and Local Data Stores

This target includes two ATG servers that share a data store that stores repository assets. Each server has its own local VFS that stores ATG Scenario Personalization file assets. This local VFS is located in Nucleus at /atg/epub/file/ConfigFileSystem and is installed with the Publishing agent.

Because both deployment agents have a local VFS, each agent needs to be assigned responsibility for managing its own VFS. Furthermore, one agent needs to be assigned responsibility for managing the shared data store. To satisfy these requirements, the deployment responsibilities for the target are assigned as follows:

Because both VFSs are local, no work is duplicated.

ATG Servers and Web Servers Use Shared and Local Data Stores

This example builds on the previous one, where ATG Servers Use Shared and Local Data Stores, by adding a Web server where static content files are deployed from the ATG Content Administration server. The Web server has its own local VFS that stores file assets. This local VFS is located in Nucleus at /atg/epub/file/WWWFileSystem and is installed with the Publishing Web agent.

Deployment agents P1 and P2 are responsible for managing their own local ConfigFileSystem VFSs; agent P2 is responsible for managing the shared data store that stores repository assets.

To complete deployment assignments for this target configuration:

This is accomplished through the use of the Available Destinations and Include Destinations fields or the <includeassetdestination> and <excludeassetdestination> tags as shown in the diagram. If you specify these tags in the deploymentTopology.xml file, you must specify an asset destination by its absolute component name in Nucleus.