Integration Guide › Integrating with CA User Activity Reporting › CA User Activity Reporting Integration Architecture

CA User Activity Reporting Integration Architecture

Integration with CA User Activity Reporting lets you send CA ControlMinder audit events from each of your endpoints for collection and reporting by CA User Activity Reporting.

You can configure CA ControlMinder to send audit events from the audit file on the local endpoint to a remote audit queue on the Distribution Server. You can then configure a CA User Activity Reporting connector to connect with the audit queue and pull events (messages) from it. CA User Activity Reporting processes these events and sends them to the CA User Activity Reporting server.

The CA ControlMinder installation supports CA User Activity Reporting integration.

The following diagram shows the architecture of CA User Activity Reporting integration components:

The preceding diagram illustrates the following:

• Each endpoint, containing a CA ControlMinder database (seosdb), has the Report Agent component installed.
• The Report Agent collects audit data from the endpoint and sends them to the Distribution Server.
• The Distribution Server accumulates the audit data in an audit queue.
• A CA User Activity Reporting agent collects events from the audit queue and sends it to the CA User Activity Reporting server for processing.

Note: CA User Activity Reporting integration relies on reporting service components. As such, your architecture includes other reporting service components and features that are not used for CA User Activity Reporting integration. These components and features are dimmed in the diagram.

Note: CA ControlMinder Enterprise Management installs the Distribution Server on the Enterprise Management Server by default. For high availability purposes, you can install the Distribution Server on a separate computer.

More information:

Reporting Service Architecture