JMS Audit Event Handler Properties

Note that the JMS audit handler config in audit.json includes the ForgeRock audit event topics and JMS audit topics.

To use the JMS resources provided by your web application container, leave the JNDI Context Properties settings empty. Values for topicName and connectionFactoryName will then depend on the configuration of your web application container.

UI Label / Textaudit.json File LabelDescription
Delivery ModedeliveryModeRequired property, for messages from a JMS provider; may be PERSISTENT or NON_PERSISTENT
Session ModesessionModeAcknowledgement mode, in sessions without transactions. May be AUTO, CLIENT, or DUPS_OK.
Batch Configuration SettingsbatchOptions for batch messaging
Write IntervalwriteIntervalInterval at which buffered events are written to JMS (units of 'ms' or 's' are recommended). Default is 10 ms.
CapacitycapacityMaximum event count in the batch queue; additional events are dropped
Maximum Batched EventsmaxBatchedEventsMaximum number of events per batch
JNDI ConfigurationjndiConfigurationJava Naming and Directory Interface (JNDI) Configuration Settings
JNDI Context PropertiescontextPropertiesSettings to populate the JNDI initial context with
JNDI Context Factoryjava.naming.factory.initialInitial JNDI context factory, such as com.tibco.tibjms.naming.TibjmsInitialContextFactory
JNDI Provider URLjava.naming.provider.urlDepends on provider; options include tcp://localhost:61616 and tibjmsnaming://
JNDI Topictopic.forgerock.idm.auditRelevant JNDI topic; default=forgerock.idm.audit
JNDI Topic NametopicNameJNDI lookup name for the JMS topic
Connection FactoryconnectionFactoryNameJNDI lookup name for the JMS connection factory
Read a different version of :