Persistent Events and Notifications

Selected user events, termed persistent user events, are audited by the primary database to enable the events to be replayed on the secondary database.

On a primary or non-SDS system, subscribers are notified of non-immediate events at the time the transaction commits (or never, if the transaction aborts). When a persistent user event is replayed on a secondary system, subscribers to the event are notified when the transaction containing the persistent event commits on the secondary system.

Persistent user events can be achieved in two ways, as follows.

Globally, by setting the AuditCauseEvents parameter in the [SyncDbService] section of the JADE initialization file to true. This parameter is observed only on an SDS primary server and it results in all non-immediate user events caused on persistent objects being converted into persistent user events; that is, they are audited for replay on secondary systems.
Selectively, by leaving the AuditCauseEvents parameter disabled (that is, false) and using the Object class sdeCauseEvent or sdsCauseEvent method to explicitly cause persistent user events for secondary replay.

The userInfo parameter can be used to associate additional information with the event. This information is passed in the userInfo parameter of the sdeCauseEvent or sdsCauseEvent method to be received by event subscribers in the corresponding userInfo parameter of the userNotification or userNotify callback method.