The following table summarizes the relationships of multiple-application clusters to users and scenario editor servers (SES). The architecture diagram in this chapter identifies the server types (A – H) in the table.
The abbreviation ISS represents individual scenario servers, and SES represents a scenario editor server (an instance of a process editor server).
For information on how to set up scenario editor servers, refer to the ATG Personalization Programming Guide. Note: The ATG Configuration and Installation Manager (CIM) cannot be used to configure scenario editor servers or global scenario servers.
Server Type | Cluster/ | External Users | External Scenario Server | Internal Users | Internal Scenario Server | Preview Users | Preview Scenario Server |
|---|---|---|---|---|---|---|---|
A | Customer Applications/ | Customer Users | Customer SES | NA | NA | NA | NA |
B | Agent Applications/ | Customers | ISS points to Customer SES | Agents and Service Administrators (in | Agent SES | NA | NA |
C | Management Applications/ | Customers | ISS points to Customer SES | Management Users | Starts up but not used | Preview Users | Preview SES |
E | ATG Search Engine | NA | NA | NA | NA | NA | NA |
F1 | ATG Data Warehouse Loader/ | Customers | NA | Dynamo Administration Users | NA | NA | NA |
F2 | ATG Outreach Data Warehouse Loader/ | Customers | NA | Dynamo Administration Users | NA | NA | NA |
G | ACI/ | NA | NA | Agents and/or Management Users | NA | NA | NA |
Methods on the ATG Data Warehouse load servers are invoked using a Dynamo Admin user interface or run on a schedule.
Note also that the scenario server on the asset management server does not run scenarios (the editOnlyMode property in the Scenario Manager is set to true). Users can create and edit scenarios through the ACC, but there is no attempt to run them, and the scenarios do not appear in the ATG Dynamo Server Admin. This behavior is required to avoid conflicts with external user profiles in the customer-facing database. If the Preview layer is enabled, however, the scenario manager does run scenarios so that users can preview their results. In this case, the database being referenced is the preview user profile database, where the conflicts do not occur.
Order of Server Startup for Correct Behavior of Scenarios
Important: As shown in the previous table, several ATG applications use a scenario editor server instance running on the customer-facing server. If your environment includes ATG Service as well as other applications that use the customer-facing scenario editor server, for example ATG Outreach, make sure you start the customer-facing server before the agent server. Otherwise, the agent server becomes the scenario editor server, which can cause errors to occur; for example, ATG Outreach campaigns fail to run.
