Purge Old Transaction IDs batch process
Code |
|
Categories |
|
Implementation |
Batch process |
Stoppable |
No (single phase process) |
Schedule |
Not scheduled |
Class |
PurgeTransactionIds.gs |
The Purge Old Transaction IDs batch process deletes SOAP header transaction IDs generated by systems external to PolicyCenter. This process uses Gosu class PurgeTransactionIds to read the value of the TransactionIdPurgeDaysOld parameter in config.xml. The process then purges transaction IDs that have a creation date prior to the current date minus the value of the TransactionIdPurgeDaysOld parameter.
Guidewire does not schedule this batch process in the base configuration as the table that stores the transaction IDs takes very little space in the database. Unless there is a constant buildup of these transaction IDs, there is no real need to continually purge this data. In fact, if you do purge this data, it is then not possible to determine if a new transaction is a duplicate of a transaction sent by the external system at an earlier date. There are other alternatives to purging this data. For example, you can partition the table by date.
By default, Guidewire does not provide an entry for this process in file scheduler-config.xml in the base configuration. To schedule this process, add an entry for it to scheduler-config.xml.
See also
- For information on SOAP headers, see the Integration Guide.
- For information on how to check for duplicate transaction IDs, see Checking for duplicate external transaction IDsthe Integration Guide.
