Archiving Object-Specific Customizing (XML DAS Archiving)
These settings are valid only for the relevant XML archiving object.
Archiving object-specific Customizing for XML-DAS data archiving differs from archiving object-specific Customizing for ADK data archiving as follows:
Logical home path
Instead of a logical file name, XML DAS data archiving used the logical home path. The logical home path indicates the physical home path. The physical home path leads to the home collection under which applications store their own hierarchies for storing resources. It is defined in Basis Customizing.
Size of an archive file
This area is not applicable in Customizing for XML DAS data archiving, because a separate resource is created for each data object.
Settings for the Delete Program
This area contains the additional Package Size field for XML DAS data archiving. The value of this field determine how many resources the delete program requests at one time for processing together in one step.
This is valid only for delete program that work without partitions. If your delete program works with partitions, the package size entered here is not relevant.
Delete jobs
As in ADK data archiving, you use this area to determine when the delete program is to be started.
The difference is that with Start Automatically or starting automatically After an Event, exactly one delete job is scheduled per archiving session in XML archiving. This job processes all resources in sequence.
File Storage to Storage System
Not relevant for XML DAS data archiving