44 / 166
What is Document History Database?
The document history database maintains a history of the guaranteed documents processed by triggers. The Integration Server adds an entry to the document history database when a trigger service begins executing and when it executes to completion(whether it ends in success or failure). The document history database contains document processing information only for triggers for which the Use history property is set to true.
The database saves the following information about each document:
* Trigger ID. Universally unique identifier for the trigger processing the document.
* Document UUID. Universally unique identifier for the document. The publisher is responsible for generating and assigning this number. (The Integration Server
automatically assigns a UUID to all the documents that it publishes.)
* Processing Status. Indicates whether the trigger service executed to completion or is still processing the document. An entry in the document history database has either a status of "processing" or a status of "completed." The Integration Server adds an entry with a "processing" status immediately before executing the trigger service. When the trigger service executes to completion, the Integration Server adds an entry with a
status of "completed" to the document history database.
* Time. The time the trigger service began executing. The document history database uses the same time for both entries it makes for a document. This allows the Integration Server to remove both entries for a specific document at the same time.
To determine whether a document is a duplicate of one already processed by the trigger, the Integration Server checks for the document’s UUID in the document history database. The existence or absence of the document’s UUID can indicate whether the document is new or a duplicate.
Asked In ::
The document history database maintains a history of the guaranteed documents processed by triggers. The Integration Server adds an entry to the document history database when a trigger service begins executing and when it executes to completion(whether it ends in success or failure). The document history database contains document processing information only for triggers for which the Use history property is set to true.
The database saves the following information about each document:
* Trigger ID. Universally unique identifier for the trigger processing the document.
* Document UUID. Universally unique identifier for the document. The publisher is responsible for generating and assigning this number. (The Integration Server
automatically assigns a UUID to all the documents that it publishes.)
* Processing Status. Indicates whether the trigger service executed to completion or is still processing the document. An entry in the document history database has either a status of "processing" or a status of "completed." The Integration Server adds an entry with a "processing" status immediately before executing the trigger service. When the trigger service executes to completion, the Integration Server adds an entry with a
status of "completed" to the document history database.
* Time. The time the trigger service began executing. The document history database uses the same time for both entries it makes for a document. This allows the Integration Server to remove both entries for a specific document at the same time.
To determine whether a document is a duplicate of one already processed by the trigger, the Integration Server checks for the document’s UUID in the document history database. The existence or absence of the document’s UUID can indicate whether the document is new or a duplicate.