Limiting the Size of the Transaction Archive
Even as a zip archive, a transaction archive entry may consume a substantial amount of disk space. There are three mechanisms available to avoid filling the file system.
• Filter which transactions are stored in the archive by setting the com.arbortext.e3.transactionArchive.selector parameter.
◦ none saves no entries
◦ error saves error entries
◦ log (the default) saves error entries, as well as requests with log entries or intermediate files
◦ all saves all requests, including successful requests
• Control how long a transaction will remain in the archive by setting the com.arbortext.e3.transactionArchive.maxAge. Transactions older than the specified duration will be deleted.
• Specify the maximum amount of disk space that the archive can occupy by setting the com.arbortext.e3.transactionArchive.maxSize parameter. If the archive grows larger than the specified limit, oldest transactions are deleted to bring the spaced consumed within the maximum level.