Implementation Guide › Considerations for CA Access Control Users › Integrating with CA Access Control

Integrating with CA Access Control

You can integrate CA User Activity Reporting Module with CA Access Control using one of several different release levels. The general approach is the following:

For CA Access Control releases that use a TIBCO message server for routing events, do the following:

• Install a CA User Activity Reporting Module agent
• Configure a connector that uses the AccessControl_R12SP1_TIBCO_Connector connector

For CA Access Control r12.5, see the CA Access Control r12.5 Implementation Guide and the CA User Activity Reporting Module CA Access Control Connector Guide.

For CA Access Control r12. SP1, see the CA Access Control r12 SP1 Implementation Guide, 3rd Edition, and the Connector Guide for CA Access Control.

Note: These implementations use components that are part of the CA Access Control Premium Editions.

For CA Access Control releases that use selogrd for routing events, do the following:

• Install a CA User Activity Reporting Module agent
• Configure a connector that uses the ACSelogrd integration

More information about configuring a connector to collect CA Access Control events is available in the CA Access Control r8 SP1 Connector Guide.

If you are currently sending CA Access Control events to CA Audit, use of the following methods to get events to CA User Activity Reporting Module:

• Modify an existing CA Audit policy to send events both to CA Audit and to CA User Activity Reporting Module, if you use a CA Audit iRecorder to collect events. You can also modify the policy to send events only to the CA User Activity Reporting Module server, if desired.
• Configure the control.conf file for an iRecorder to send events directly to CA User Activity Reporting Module.

The guidelines that follow use the r8 SP2-series for the Policy Manager user interface. The general procedures are the same when you are using earlier CA Audit releases, though the user interface is different.