Skip to main content
Version: 2.75.x.x LTS

Events and persistent queue

The persistent queue is used by different nevisIDM modules such as batch jobs or the printing module. The persistent queue is stored on the database and, as a result, its entries survive crashes of nevisIDM or its server, and may also be processed in parallel if there is more than one nevisIDM application using the same nevisIDM database. Moreover, the processing of the queue entries is done asynchronously by separate worker threads so that the main application is not interrupted by them and can focus on user interactions.

With appropriate rights, it is possible to delete failed elements from the queue.

Database table TIDMA_PERSIST_QUEUE

DB attributeJava data type (max. size), defaultsDescription
client_idLong, nullableThe ID of the enqueuer's client. Foreign key that links to information in the table TIDMA_CLIENT.
data1CLOB, nullableGeneric data field
data2String(4000), nullableGeneric data field
data3String(4000), nullableGeneric data field
event_idString(2048), not NULL
item_idLong, not NULLPrimary key (uniquely identifies each individual DB entry)
job_nameString(2048), nullable
schedule_dateDate, nullableThe Date the event has to be scheduled for.
stateInteger, not NULL
target_client_idLong, nullableID of the target's client or null if the target does not belong to any specific client or belongs to more clients. Foreign key that links to information in the table TIDMA_CLIENT.
timestampLong, not NULL
typeInteger, not NULL
user_idString(2048), not NULLUser ID of enqueuer