Administration Guide › Services and CA Adapters › CA Adapters Configuration Tasks › SAPI Service Considerations

SAPI Service Considerations

CA Enterprise Log Manager uses two instances of a CA Audit Submit Application Programming Interface (SAPI) service, one installed as the SAPI Collector, the other as the SAPI Router. The SAPI services are generally used to receive events from existing CA Audit clients and integrated products. You can configure the SAPI adapters using the following settings:

• Enable Listener

  Activates the selected service. This setting is enabled by default.

• SAPI Port

  Sets a specific port number for the selected service, if it is not registered with the portmapper. The default value, 0, allows the service to use a randomly-determined port, if the Register check box is selected.

  Note: The port number must be different for the SAPI Collector and Router. If the same ports are set for both services, the second one set will not function/.

• Register

  Controls whether the service registers with the system portmapper. If you select Register and enter 0 in the SAPI Port field, a random port is selected each time the service starts. This is the default setting for both fields. If Register is not selected, you must specify a SAPI port.

• Encryption Key

  Defines the encryption key, if you use a non-standard encryption key in your CA Audit environment, which the SAPI adapter uses to read incoming SAPI events.

• Event Ordering

  Ensures that events are sent to the event log store in the same order in which they are received. If event ordering is disabled, the order may be changed if some events are parsed and sent onward more quickly than others. Enabling event ordering may affect performance by increasing the size of the event queue.

• Event Throttling

  Defines the maximum number of events in the event processing queue, allowing control of processing resources. Entering 0 in this field means that no throttling occurs. Events that exceed this threshold will be delayed at the source.

• Thread Count Per Queue

  Defines the number of processing threads for each protocol. Using many processing threads will speed up processing if event ordering is disabled. If event ordering is enabled, the thread count will have no effect. Using many threads may have performance implications.

• Cipher and Data Mapping
  • The Cipher shuttle control determines which of the available ciphers the service uses to decrypt incoming messages.
  • The Data Mapping file shuttle control determines which of the available DM files the service uses for event mapping.

Logging settings control how individual CA Enterprise Log Manager modules record internal messages. They are only available as local settings. Logging settings are usually used for troubleshooting purposes. It is not normally necessary to change these settings, and you should have a good understanding of log files and logging before doing so.

• Log Level

  Defines the type and level of detail recorded in the logging file. The drop-down list is arranged in order of detail, with the first choice providing least detail, and the last providing most detail.

• Apply to all loggers

  Controls whether the Log Level setting overrides all log settings from the log's properties file. This setting only applies when the Log Level setting is lower (showing more detail) than the default setting.