The following diagram illustrates the basic configuration of a production environment where ATG Content Administration-managed assets are deployed:
The preceding diagram illustrates several important concepts about the production environment:
The production environment does not use a versioned schema. When you deploy a specific version of an asset to your production environment, its version metadata is excluded.
The DeploymentManager moves assets from the content development environment to the production environment. However, each target site server runs an agent that handles deployment-related tasks on that server.
Two types of agents run on target sites:
Publishing agents run on the ATG servers. These agents are configured to manage deployment-related tasks for repository and file assets on the target site.
Publishing Web agents run on the Web servers. These agents are configured to manage deployment-related tasks for file assets on the target Web server.
The preceding diagram shows a production environment with a single ATG cluster, where multiple ATG instances point to the same data stores. However, a target site can include multiple ATG clusters. For simplification, it also indicates a configuration for Online Deployment; however, a production environment should always be configured to use Switch Deployment.
