About Archiver applications

Separate tasks for separate document types

For each Archiver application, you can configure one or several archiving tasks. If you have several document types, you can configure a separate task for each document type. For example, you can configure one task for pick lists which should be available at a warehouse as soon as possible, and another task for invoices which should be available only twice a month.

Batch contra continuous archiving

In the task configuration, you schedule how often the Archiver application should poll the output queue in the runtime repository for documents ready for archiving. When the Archiver application finds such documents, the documents and the related metadata are archived in one of the following ways:

•

Batch archiving – At the specified polling interval, the Archiver application checks the number of documents in the output queue. If the number of documents equals or exceeds a certain value (the Task trigger (documents) setting in the Configuration dialog box), the Archiver application archives the batch of documents. By using batch archiving and directing the archiving to off peak hours, the load on the Collector archive can be decreased.

•	Continuous archiving – The Archiver application archives any documents marked for archiving based on the specified poll interval. By using continuous archiving, documents are quickly available to the StreamStudio or Content Server user.

You can configure several archiving tasks for the same Archiver application and combine batch and continuous tasks.

Documents moved per transfer

To reduce the load on a single Archiver application and decrease the impact of an archiving failure, documents are locked and transferred in smaller segments (the Documents moved per transfer setting in the Configuration dialog box). If you add several Archiver applications to an application domain, different segments can be archived by different applications. The workload is thereby spread among the Archiver applications, and the applications act as failover for each other.

Example 3

Triggered archiving events

In this example, the following is configured for an Archiver application:

•	Type – Batch

•	Task trigger (documents) – 40 documents

•	Documents moved per transfer – 100 documents

Depending on number of documents ready for archiving in the output queue, different archiving events are triggered.

Number of documents in the output queue	Archiving events by the Archiver application
39	No archiving is triggered
40	The archiving is triggered, and 40 documents are locked and transferred in one segment (with 40 documents in the segment).
201	The archiving is triggered and 201 documents are locked and transferred in three segments (with 100, 100, and 1 documents in the segments).
100 000	The archiving is triggered and 100 000 documents are locked and transferred in 1 000 segments (with 100 documents in each segment).