Extended Reporting system architecture for BMC Real End User Experience Monitoring

The BMC Real End User Experience Monitoring Extended Reporting component enables extended performance reporting and analysis. The following figure illustrates the components required to implement BMC Real End User Experience Monitoring Extended Reporting. These components are in addition to the BMC Real End User Experience Monitoring basic system components already implemented.

Extended Reporting components and interface

Implementation of the Extended Reporting component requires installation of the following BMC Real End User Experience Monitoring components:

• Real User Analyzer—An Analyzer (or Real User Monitor) instance serves as the data provider.
• Aggregation Server—The Aggregation Server extracts data from the Analyzer's raw data export functionality via HTTP (or HTTPS). The Aggregation Server transforms the data into multidimensional data models (performance cubes), and loads the data into the data warehouse through the network-attached storage (NAS). Performance cubes control the selection of the application, infrastructure, or user performance data from an Analyzer. For more information about performance cubes, see Setting up performance cubes for Extended Reporting.
• BMC Real End User Experience Monitoring - Aggregation Server for Extended Reporting user interface—Like other BMC Real End User Experience Monitoring components, the Aggregation Server has its own user interface accessed by using browser software. The Aggregation Server for Extended Reporting user interface enables the administrator to configure the component and to manage and control data aggregation. Within a performance cube, the administrator can filter or limit the Analyzer data collected to produce the extended performance and availability reports.

Additional components required for Extended Reporting

The following components complete the Extended Reporting implementation.

• Network Attached Storage (NAS)—After transforming the data into performance cubes, .csv files are stored on the NAS device so that the data warehouse can access them. A NAS device is used to temporarily make the .csv file accessible to both the Aggregation Server and the data warehouse. Once the file is loaded into the data warehouse, it is removed from the NAS device. The NAS device uses the Server Message Block/Common Internet File System (SMB/CIFS) file sharing protocol.
• Oracle database instance (data warehouse)—You must install an Oracle database and client, and create a database instance to serve as the data warehouse for SAP BusinessObjects and the Aggregation Server. The Oracle database is external to the Aggregation Server. The Aggregation Server and SAP BusinessObjects require access to the Oracle database listener port (default: TCP 1521).
• SAP BusinessObjects Business Intelligence Platform 4.0—Generates report by gathering data from the data warehouse.
  • SAP BusinessObjects BI launch pad—Reports are viewable in the SAP BusinessObjects BI launch pad, which is accessible through a web browser.
  • The SAP BusinessObjects Central Management Server—The Central Management Server is part of the SAP Business Enterprise application and is deployed on an Apache Tomcat application web server.
  • BusinessObjects Universe—The universe contains the objects necessary for reporting on performance and availability.

Related topics

Downloading-the-installation-files

System-requirements