Implementation Guide › Considerations for CA Access Control Users › How to Configure a CA Access Control iRecorder to Send Events to CA Enterprise Log Manager › Configure a Standalone CA Access Control iRecorder

Configure a Standalone CA Access Control iRecorder

Use this procedure to configure your iRecorder to send CA Access Control events to CA Enterprise Log Manager.

Important! A standalone iRecorder can only send its events to a single destination. If you configure an iRecorder using the procedure that follows, all of the iRecorders installed on this system will send their events only to the named CA Enterprise Log Manager event log store.

iRecorders that are installed on the same computer as a CA Audit client send events to the client directly. For those servers, you should modify an existing CA Audit policy to add rule actions and after configuring the CA Enterprise Log Manager SAPI collector or router adapters.

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 or root 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.

   The following is a sample iControl file with the sections you need to change in boldface type:

   <?xml version='1.0' encoding='UTF-8' standalone='no'?>
   <iSponsor>
   	<Name>iControl</Name>
   	<ImageName>iControl</ImageName>
   	<Version>4.5.0.2</Version>
   	<DispatchEP>iDispatch</DispatchEP>
   	<ISType>DSP</ISType>
   	<Gated>false</Gated>
   	<PreLoad>true</PreLoad>
   	<RouteEvent>false</RouteEvent>
   	<RouteEventHost>localhost</RouteEventHost>
   	<EventsToCache>100</EventsToCache>
   	<EventUseHttps>true</EventUseHttps>
   	<EventUsePersistentConnections>true</EventUsePersistentConnections>
   	<EventUsePipeline>false</EventUsePipeline>
   	<StoreEventHost max="10000">localhost</StoreEventHost>
   	<RetrieveEventHost interval="60">localhost</RetrieveEventHost>
   	<UID>ef1f44ef-r8sp1cr3596a1052-abcd28-2</UID>
   	<PublicKey>Public_Key_Value</PublicKey>
   	<PrivateKey>Private_Key_Value</PrivateKey>
   	<EventsToQueue>10</EventsToQueue>
   </iSponsor>
   

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 RouteEventHost tag pair.

6. Specify the following RouteEventHost value:

   <RouteEventHost>Your_CA_Enterprise_Log_Manager_hostname</RouteEventHost>
   

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

7. Save and close the file.
8. 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.