This process describes the basic procedures of XML-based data archiving. They differ from the Archiving Procedures of ADK-based archiving in several ways. In the following steps we describe the difference between the two.
The XML-based archiving procedure differs from the ADK procedure in that it comprises two steps:
Step 1: Creating resources
· In the XML archiving procedure one XML file is written per data object, while in ADK-based archiving several data objects are written to one archive file. The XML file that is created is called resource. Later it is possible for the administrator to pack the resources (optional).
· With XML archiving storing the resources is part of the first step. In other words, the second step of ADK-based archiving is not necessary here. The resources are written to archive stores via home paths. For this to take place the administrator must first assign archive stores to the existing home paths.
Step 2: Running Delete Programs
There are two ways you can start the delete programs in XML-based data archiving:
· Automatically after the write phase: To automatically start the delete programs, make the appropriate settings in Customizing. In this case the delete program processes the resources sequentially (one after the other).
During the automatic start of the delete program, the system schedules exactly one delete job per write job, no matter how many resources have been archived.
· Manually using transaction SARA: Here you start the delete program manually by choosing Delete in transaction SARA. You can enter how many delete jobs are to be scheduled for each archiving session. You can start several delete jobs in parallel.
The number of delete jobs you enter in the Delete function of transaction SARA refers to the individual archiving sessions you select under Archive Selection. It means number of delete jobs per archiving session.
It is not possible to select individual resources for deletion.