Enterprise Administration Guide › Creating Reports › Reporting Service › How the Reporting Service Works › How Data for Reporting Is Collected from Each Endpoint

How Data for Reporting Is Collected from Each Endpoint

To generate reports, data from each endpoint has to be collected. The reporting service uses a Report Agent, installed on each CA Access Control and UNAB endpoint, to collect data from that endpoint at scheduled times or on-demand.

Note: The Report Agent is also responsible for collecting and routing audit data for integration with CA Enterprise Log Manager. This process describes only those actions that the Report Agent takes for reporting on the endpoint.

The Report Agent performs the following actions on each endpoint:

1. Performs a deviation calculation and sends the results to the Distribution Server.

   Important! If you have the Report Agent set to run regularly, and you do not need to have the DMS updated, you do not need to schedule a policy deviation calculation separately.

2. Creates a copy of the CA Access Control database (seosdb) and each Policy Model database (PMDB) on the CA Access Control endpoint, or creates a copy of the UNAB database on the UNAB endpoint.

   This is a temporary copy that the Report Agent takes so that it can process data without affecting CA Access Control performance.

3. Dumps the data from each database into an XML structure.

   This is a dump of all of the objects in the database, meaning that all data is captured, not just data that is visible through database interface utilities (such as selang).

4. Sends an XML version of the database to the Distribution Server.

   The Report Agent sends the data to the reporting queue on the Distribution Server.

Note: Data for reporting is not collected from PUPM endpoints.

More information:

How Configuration Settings Affect the Report Agent