Understanding the ATG Campaign Optimizer architecture can help you decide how to organize your hardware and software resources.
The following diagram shows how the databases and repositories interact while running the different modules. The numbers in the diagram describe interactions that are described in detail by the corresponding numbered list following the diagram.
Note: An identical architecture exists in support of ATG Campaign Optimizer for Commerce with ATG instances DCS-ABTEST.runtime, DCS-ABTEST.management, and DCS-ABTest.reporting.
The following list describes the actions in the above diagram. Each number in the list corresponds to a number in the diagram.
1. Write log records as test participants interact with the site
2. Read and write profile markers to track test group membership
3. Read and write test tracking records as tests start and end
4. Reads test tracking records to display test status and restrict editing
5. Reads and writes test definitions
6. Reads and writes preview tracking records as previews start and end
7. Reads and writes profile markers as business users start and end previews
8. Reads and writes asset registry entries
9. Reads report records to display test results
10. Reads and writes report records containing test results
11. Reads log records to compute reports
