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 / Text | audit.json File Label | Description |
---|---|---|
Delivery Mode | deliveryMode | Required property, for messages from a JMS provider; may be PERSISTENT or NON_PERSISTENT |
Session Mode | sessionMode | Acknowledgement mode, in sessions without transactions. May be AUTO , CLIENT , or DUPS_OK . |
Batch Configuration Settings | batch | Options for batch messaging |
Write Interval | writeInterval | Interval at which buffered events are written to JMS (units of 'ms' or 's' are recommended). Default is 10 ms. |
Capacity | capacity | Maximum event count in the batch queue; additional events are dropped |
Maximum Batched Events | maxBatchedEvents | Maximum number of events per batch |
JNDI Configuration | jndiConfiguration | Java Naming and Directory Interface (JNDI) Configuration Settings |
JNDI Context Properties | contextProperties | Settings to populate the JNDI initial context with |
JNDI Context Factory | java.naming.factory.initial | Initial JNDI context factory, such as com.tibco.tibjms.naming.TibjmsInitialContextFactory |
JNDI Provider URL | java.naming.provider.url | Depends on provider; options include tcp://localhost:61616 and tibjmsnaming://192.168.1.133:7222 |
JNDI Topic | topic.forgerock.idm.audit | Relevant JNDI topic; default=forgerock.idm.audit |
JNDI Topic Name | topicName | JNDI lookup name for the JMS topic |
Connection Factory | connectionFactoryName | JNDI lookup name for the JMS connection factory |