A deployment topology requires you to determine which agents in a target are responsible for managing target assets. Only one agent should manage a shared data store. For each agent, determine which repository or type of asset that agent will manage. The two 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 Admin Console deployment UI.
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 and Web servers use shared and local data stores
This target includes two ATG servers that share a data store that stores repository assets, and a Web server where static content files are deployed from the asset management 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.
The various deployment agents have the following deployment responsibilities:
Publishing agents P1 and P2 manage their own local ConfigFileSystem VFSs.
Web publishing agent P3 manages its own local WWWFileSystem. In the Admin Console deployment UI, specify
/atg/epub/file/ConfigFileSystemas the included destination for deployment agents P1 and P2. Because both VFSs are local, no work is duplicated. For agent P3, specify/atg/epub/file/WWWFileSystemas the included destination.
