The customer-facing cluster (A) is also referred to as the production cluster. The modules that make up your customer-facing Web applications run here.
The users associated with applications running on this cluster are external users.
All instances in the cluster run the same modules (including ABTest.runtime and Outreach.runtime, as well as the modules for outward facing applications).
If ATG Self Service is running on this cluster, it receives deployments from the asset management cluster and from the agent-facing cluster.
The customer-facing cluster requires an external scenario editor server. You must designate one instance in the cluster as the scenario editor server; it will be a global scenario editor server. (Multiple instances can be global scenario servers.) The instance you designate as the scenario editor server is usually dedicated to that task; the load manager does not send it Web traffic in production.
Another instance in the cluster is usually dedicated to running lock managers, and the load manager does not send it Web requests.
For details about setting up and running applications, refer to the documentation for each application.
