CentraSite Documentation : Runtime Governance with CentraSite : Run-Time Governance Reference : Run-Time Events and Key Performance Indicator (KPI) Metrics : Configuring CentraSite to Receive Run-Time Events and Metrics : Configuring the Event Receiver : Setting the Properties for FileSystem or InMemory
Setting the Properties for FileSystem or InMemory
When the eventsQueueImpl property is set to either FileSystem or InMemory, you should also set the following properties:
Property for FileSystem or InMemory and Description
com.softwareag.centrasite.soalink.events.enableBatchInsertion
Enable or disable batch insertion of events into the database. Supported values are true and false. If true, events will be batched as per the "batching rules" properties below and the batch will be stored to the database. If false, events will be stored to the database one by one.
com.softwareag.centrasite.soalink.events.maxNumOfEventsPerBatch
Maximum number of events in a batch. Should be an integer value. A value <= 0 disables this rule. This rule is evaluated only on arrival of a new Trap.
com.softwareag.centrasite.soalink.events.maxSizeOfBatch
Maximum size (in bytes) of a batch. Default value is 512KB. Should be an integer value. A value <= 0 disables this rule. This rule is evaluated only on arrival of a new Trap.
com.softwareag.centrasite.soalink.events.maxTimeIntervalBetweenBatches
Maximum time interval (in milliseconds) between two subsequent batch storages. Should be an integer value. A value <= 0 disables this rule. Unlike the other two rules, this rule is evaluated periodically. Hence this rule prevents any trap stuck in the batch for ever if inflow of traps stops; in short this acts as a batch-timeout. A very low value for this rule reduces batch efficiency and introduces unnecessary looping.
com.softwareag.centrasite.soalink.events.fileSystemQueueDir
(Only applies when the eventsQueueImpl property is set to FileSystem.) The directory that should be used as FileSystem Queue. Incoming traps will be stored in this directory temporarily and hence should have write permission. The path can be absolute or relative. It is advisable to provide the absolute path. Relative paths will be considered relative to one of the following, based on availability in the same order:
1. SOALinkSNMPEventsListener/WEB-INF directory for exploded deployments.
2. javax.servlet.context.tempdir for zipped deployments.
3. java.io.tmpdir if none of the above are available.
Copyright © 2005-2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback