The server runs ABTest.management and usually ABTest.reporting, as well as the customer facing applications.
The ATG Campaign Optimizer (CO) application has two different sets of users: those that log into the ABTest management user interface, and those that log into the customer facing site. These users are stored in separate database tables in production.
The architecture diagram and the table in Relationships between Clusters, Users, and Scenario Servers illustrate that, in general, the primary users for internal servers are internal users and the primary users for external servers are external users. ATG Campaign Optimizer differs from the other servers in this aspect. The table lists external users as its primary users, yet it appears in the architecture drawing as an internal application. ATG Campaign Optimizer is shown in the drawing as an internal application, because the link to the management user interface is not made available to the same set of users who visit the external Web site.
Internal users with the appropriate roles can manage application users via the ATG Control Center (ACC) that connects to the cluster’s RMI port.
You create scenarios on the Campaign Optimizer management server (on which there must be an external scenario editor server), and then use a manual process to copy them to the customer facing server for running. The customer facing server must have an external scenario editor server to preview tests.
For details about setting up your system to run ATG Campaign Optimizer, see the ATG Campaign Optimizer.
