Before you create the archive project, you configure the source

and target

connections to the

archive locations that you want to use

. You set up access roles and assign security groups to the source

and target archive

locations to determine which users can run archive jobs in Data Archive.

Based on the archiving method that you use, you perform additional tasks to prepare Data Archive for the archive process.

When you create the archive project, you define project parameters to control which events and documents to

archive

. The archive project contains required and optional parameters. Required parameters apply to the entire event hierarchy. Optional parameters apply to the root event in the event hierarchy.

For required parameters that apply to the entire event hierarchy, the archive job

archives

only event hierarchies in which all events match the parameter. For example, if you select to

archive

events older than 10 days, the archive job

archives

event hierarchies in which all events are older than 10 days.

For optional parameters that apply to the root event in the hierarchy, child events of the hierarchy do not need to match the parameter. For example, if you select to

archive

events with a related

partner

, the archive job

archives

event hierarchies in which only the root event has a related

partner

. The child events in the event hierarchy can have different related

partners or no partners

.

After you create the archive project, you schedule and run an archive job. The archive job contains the archive project that you created and any additional operations that Data Archive needs to perform to successfully complete the event

archiving

.

For long-term archive jobs, the Load External Attachments archive job reports an error if the

B2B Data Exchange

document store does not contain any documents.