Implementation Guide › Considerations for CA Audit Users › Sending CA Audit Events to CA Enterprise Log Manager › Configure iRecorder to Send Events to CA Enterprise Log Manager

Configure iRecorder to Send Events to CA Enterprise Log Manager

CA Enterprise Log Manager receives events from iRecorders through the iTech Event Plugin Listener. You must configure the listener before you change the iRecorder's configuration. If you do not do this, you may lose event data. After you configure the Listener, use this procedure to configure the iRecorder to send events to the CA Enterprise Log Manager server.

iRecorders that are installed on the same computer as a CA Audit client send events to the client directly. For those machines, you should use the SAPI collector or router adapters.

Important! A standalone iRecorder can only send its events to a single destination. If you reconfigure an iRecorder using the procedure that follows, events are stored only in the CA Enterprise Log Manager event log store. If you need to retain events in both the event log store, and the CA Audit Collector database, modify a rule action on an existing policy, or create a new policy for a CA Audit client.

To configure the iRecorder to send events to CA Enterprise Log Manager

1. Log into the server that hosts the iRecorder as a user with Administrator privileges.
2. Navigate to the directory for your operating system:
   • UNIX or Linux: /opt/CA/SharedComponents/iTechnology
   • Windows: \Program Files\CA\SharedComponents\iTechnology
3. Stop the iGateway daemon or service with the following command:
   • UNIX or Linux: ./S99igateway stop
   • Windows: net stop igateway
4. Edit the iControl.conf file.
5. Specify the following RouteEvent value:

   <RouteEvent>true</RouteEvent>
   

   This entry tells the iGateway to send its events, including all iRecorder events, to the host named in the RouteHost tag pair.

6. Specify the following RouteHost value:

   <RouteHost>CA_ELM_hostname</RouteHost>
   

   This entry tells the iGateway to send its events to the CA Enterprise Log Manager server using its DNS name.

7. Restart the iGateway daemon or service with the following command:
   • UNIX or Linux: ./S99igateway start
   • Windows: net start igateway

   This action forces the iRecorder to use the new settings and starts the flow of events from the iRecorder to the CA Enterprise Log Manager server.

More information:

About the SAPI Router and Collector

Configure the SAPI Collector Service

Configure the SAPI Router Service