Use this procedure to enable a CA Audit client to send events to both CA Enterprise Log Manager and the CA Audit collector database. By adding a new target to the Route or Collector actions on an existing rule, you can send collected events to both systems. As an alternative, you can also modify specific policies or rules to send events only to the CA Enterprise Log Manager server.
CA Enterprise Log Manager collects events from CA Audit clients using the CA Audit SAPI Router and CA Audit SAPI Collector listeners. Collected events are stored in the CA Enterprise Log Manager event log store only after you push the policy to the clients and it becomes active.
Important: You must configure the CA Enterprise Log Manager listeners to receive events before you modify and activate the policy. If you do not do this configuration first, you may have incorrectly mapped events if events arrive between the time that the policy becomes active and the listeners can correctly map the events.
To modify an existing policy rule's action to send events to CA Enterprise Log Manager
You can also use the Route action to create a rule to send events to a CA Enterprise Log Manager server.
For a CA Enterprise Log Manager implementations with two or more servers, you can enter a different CA Enterprise Log Manager host name or IP address in the Alternate Host Name field to take advantage of <Aus>'s automatic failover feature. If the first CA Enterprise Log Manager server is not available, CA Audit automatically sends events to the server named in the Alternate Host Name field.
Make any needed modifications to the rule and ensure that it compiles correctly before you activate it.
Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |