Configure A2A Client Event Polling

If you disable external listening for the A2A Client, you must configure the Client to poll
PAM
for event messages. Event information includes messages, such as get script hash or get fingerprint. 
capam32
If you disable external listening for the A2A Client, you must configure the Client to poll
PAM
for event messages. Event information includes messages, such as 
get script hash
 or 
get fingerprint
When you enable event polling, the A2A Client contacts the appliance at a regular polling interval and it queries the appliance for event data. The appliance places the events in a queue, and they remain in the queue until the A2A Client sends a request to retrieve event data. 
Enabling event polling increases network traffic between the appliance and A2A Client. If too many A2A Clients run event polling, it impacts performance at the appliance.
Enable Event Polling
To enable polling, modify the A2A Client configuration file.
Follow these steps:
  1. Open the A2A Client configuration file in a text edit. The file is in the directory:
    $CSPM_CLIENT_HOME/cspmclient/config/cspm_client_config.xml
    where
    $CSPM_CLIENT_HOME
    is the installation directory, for example
    /opt/cloakware
    .
  2. Set the external listening port (
    daemonserver2_port
    ) to 1, as shown:
    <daemonserver2_port>1</daemonserver2_port>
  3. Optionally, change the default polling interval of 120 seconds. For example, change it to 180 seconds:
    <eventpolling_interval>180</eventpolling_interval>
  4. Save your changes.