This section describes the Archive profile and the Archiving agents. The agents are forwarding agents for batch workflow configurations. 

With the Archiving agents, you have the possibility to archive data batches for a configurable period of time.

There are two agents:

• The Archiving agent, which stores the data on the platform machine.

• The Local Archiving agent, which stores the data locally on the Execution Context machine. Note that local data cannot be exported.

The Archiving agents can be configured to archive all received data batches. Each data batch is saved as a file in a user specified repository.

Depending on the selected profile, the Archive services are responsible for the naming and storing of each file, and the purging outdated files on a regular basis. Utilizing the Directory Templates and base directories specified in the Archive profile, directory structures are dynamically built when files are stored.

The system administrator defines what structure is suitable for each profile. For instance, setting the directory structure to be changed with respect to the collecting agent name on a daily basis. The Archive services automatically create all directories needed in the base directory or directories.

Configuration

You configure an archiving agent in three steps:

• Define an Archive profile.

• Configure the agent.

• Set MultiForwardingUDR input.

This section includes the following subsections:

• Archive Cleaner Task(4.1)
• Archive Profile (4.1)
• Archive Inspector (4.1)
• Archiving Agents Transaction Behavior, Input/Output Data and MIM(4.1)
• Archiving Agent Configuration(4.1)
• Archiving Agents Events(4.1)
• Archiving Agents MultiForwardingUDR Examples(4.1)
• Local Archiving(4.1)