Building Your Event-Driven Architecture : Using Integration Server to Build a Client for JMS : Exactly-Once Processing for JMS Triggers : Document History Database for Use with JMS Triggers : Managing the Size of the Document History Database
Managing the Size of the Document History Database
To keep the size of the document history database manageable, Integration Server periodically removes expired rows from the database. The length of time the document history database maintains information about a UUID varies for each trigger (JMS trigger or webMethods messaging trigger) and depends on the value of the History time to live property for the trigger.
Integration Server provides a scheduled service, namely the Message History Sweeper, that removes expired entries from the database. By default, the Message History Sweeper task executes every 10 minutes. You can change the frequency with which the task executes. For information about editing scheduled services, see webMethods Integration Server Administrator’s Guide.
Note:  
The watt.server.idr.reaperInterval property determines the initial execution frequency for the Message History Sweeper task. After you define a JDBC connection pool for Integration Server to use to communicate with the document history database, change the execution interval by editing the scheduled service.
You can also use Integration Server Administrator to clear expired document history entries from the database immediately.
Copyright © 2016 - 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback