Enables exactly-once processing for the JMS trigger and instructs the server to check a message’s redelivery count to determine whether the trigger has received the message before.

Specifies that exactly-once processing is provided for messages received by this trigger and instructs the server to check a document’s redelivery count to determine whether the trigger received the document previously.

The redelivery count indicates the number of times the routing resource has redelivered a document to the trigger.

Specifies that exactly-once processing is not provided for messages received by this trigger.

Indicates whether a document history database will be maintained and used to determine whether a message is a duplicate.

Indicates that Integration Server maintains a history of messages processed by the trigger. When the trigger receives a message, the Integration Server compares the message’s universally unique identifier (UUID) to the UUIDs of messages processed by the trigger. If there is a match, the Integration Server either determines the second message is a duplicate and discards it or, if the first message has not finished processing, marks the second message’s status as In Doubt.

Indicates Integration Server does not maintain a document history database. The Integration Server will not use document history to determine whether a message is a duplicate of one already processed by the trigger.

Specifies the length of time the document history database maintains an entry for a message processed by the JMS trigger. During this time period, the Integration Server discards any messages with the same universally unique identifier (UUID) as an existing document history entry for the trigger. When a document history entry expires, the Integration Server removes it from the document history database. If the trigger subsequently receives a message with same UUID as the expired and removed entry, the server considers the copy to be new because the entry for the previous message has been removed from the database.

The document resolver service must use the pub.publish:documentResolverSpec to define the service signature.