Archiving

Automatically archive inbound messages that have been indexed. EngageOne Deliver batches content into collections with the required journal files to efficiently compress, index and store content.

The archiving feature relies primarily on three components:

• Repository Facade creates a subfolder where content is staged for archive. Can be instantiated after content is ready for archiving or when the load frequency time has lapsed since the last time Repository Facade was created.
• Batching Process continuously manages the batching of individual message content into larger ready files for efficiency and better compression based on the Load Frequency setting. Vault uses these settings to determine when to upload the ready files. When Load Frequency = 0, the Batching Process is called by EngageOne Deliver after the Archive Content Process has completed writing files into the Collection folder for a given batch of messages.
• Archive Content writes content into the Collection folder. The Archive Content Process performs the actual writing of content into the Collection folder. This is triggered after Repository Facade has successfully created the Collection folder. The Repository Facade and Batching Process settings determine when Archive Content can start or if the Repository Facade should create a new collection.

For the technical details of how the archiving process works, refer to the EngageOne Deliver Reference Guide.