The Experience Manager architecture consists of the following components:
Figure 1-3 Experience Manager Architecture
The Experience Manager adapter manages:
Connectivity with the Experience Manager Monitors
Configuration information for each subscribed Experience Manager Monitor
Hierarchy information used to display elements as they are aggregated from the Experience Manager Monitors (using the Managed Objects Definition Language [MODL])
Data persistence configuration information for all data aggregated from the monitors (including connectivity and purging information)
All test configuration information that is stored in the database
The Experience Manager database stores the usage information from Experience Manager Monitors and test configuration information. Supported databases include: Oracle, Microsoft SQL Server, PostgreSQL, Sybase, and DB2.
See the Operations Center 5.6 Getting Started Guide for supported database versions.
For instructions on configuring Experience Manager for the database, see Section 3.1, Configuring Windows Servers for Single Sign On (SSO) and Section 3.2, Creating a Experience Manager Adapter.
Experience Manager Monitors are responsible for communication between the Operations Center server and the targets used to collect performance metrics or run synthetic testing of HTTP, HTTPS, FTP, SMTP/POP3, LDAP, SQL, TRACEROUTE, ICMP, DHCP, and NSLOOKUP sessions, as well as third-party custom tests. Based on deployment and scalability requirements, install Experience Manager Monitors on a single machine or distribute them among multiple machines.