Implementation Guide › Considerations for CA Audit Users › Understanding Differences in Architectures

Previous Topic: Considerations for CA Audit Users

Next Topic: CA Audit Architecture

Understanding Differences in Architectures

In planning how you to use CA Audit and CA Enterprise Log Manager together, you first should understand the differences in the architectures and the effects they have on your network structure.

CA Enterprise Log Manager uses an embedded event log store, and provides an Agent Explorer to configure and manage agents. New technology coupled with a common event grammar allows for faster event throughput to storage while supporting a higher number of event sources. The common event grammar allows CA Enterprise Log Manager to normalize events from many different event sources into a single database schema.

CA Enterprise Log Manager integrates at a certain level with CA Audit, but by design it is not completely interoperable. CA Enterprise Log Manager is a new and separate server infrastructure that can run in parallel with CA Audit, with the following event handling considerations:

CA Enterprise Log Manager does...

CA Enterprise Log Manager does not...

Receive event logs sent from CA Audit clients and iRecorders using configurable listeners.

Directly access event logs stored in the CA Audit collector database.

Provide a utility to import event log data stored in the CA Audit collector database (SEOSDATA table).

 

Use agents to send event logs only to the CA Enterprise Log Manager server infrastructure.

 

Permit CA Enterprise Log Manager agents and CA Audit clients with iRecorders to run on the same physical host.

Allow CA Enterprise Log Manager agents and CA Audit clients with iRecorders on the same host to access the same log sources simultaneously.

Use its built-in Agent Explorer to manage only CA Enterprise Log Manager agents. During side-by-side operation of the two systems, CA Audit uses its Policy Manager only to manage CA Audit clients

 

 

Migrate CA Audit data held in table collectors, report templates or custom reports, alert policies, collection/filtering policies, or role-based access control policies