Process Data Archiving 
You can archive process and task instances with relevant data, such as process context, tasks, attachments, and business log. The archiving unit is the main process with its sub-processes, tasks, and the related context data. The process data is archived through the XML Data Archiving Service (XML DAS) and serialized and stored in XML format.
You define and schedule the archiving process that consists of a write and a delete job with the Java Archiving Cockpit, an application that is integrated into SAP NetWeaver Administrator.
Recommendation
We recommend that you archive entries of the business log that are older than two months. This archiving session is to be executed on a daily basis at a specified time.
The Administrator role is assigned to your user.
You have the rights to call the XML DAS Administration from within SAP NetWeaver Administrator.
Archive store for BPM process data is defined.
To be able to archive processes, you need to configure your Java system environment first. Follow the description and define an archive store with the name bpm_proc. If you need to synchronize the home path, enter /<SYSID>/bpm_proc/ in the Home Path field where <SYSID> is the ID of the system, for example, /P23/bpm_proc/, and choose the bpm_proc archiving set.
More information: Configure and Activate XML Data Archiving Service
Log on to the SAP NetWeaver Administrator application.
You can start an archiving session for BPM process data from the Manage Processes application (see Monitoring and Managing the Processes):
To open the Manage Processes application, choose .
Choose the Archive... pushbutton.
The Java Archive Cockpit opens.
You can also directly open the Java Archiving Cockpit in the SAP NetWeaver Administrator by choosing
On the Write tab, choose the bpm_proc archiving set.
Enter the appropriate selection criteria for the BPM process data that you want to archive.
Note
If you do not enter any selection criteria, all archivable data for the bpm_proc archiving set is archived.
The following table lists the BPM process specific selection criteria only:
Selection Criteria |
Description |
Completion_Time_Period |
Period of time the process instances have been in completed or canceled state. |
Error_Status |
Select the Error_Status checkbox to archive only process instances that are in error status. |
Process_IDs |
You can enter multiple process instance IDs for a single archiving session. You can separate the IDs with any of the following punctuation:
|
SystemLogOnly |
Set the SystemLogOnly checkbox to archive the business log only. All other settings will then be ignored. |
SkipOnError |
Set the SkipOnError checkbox to enable the archiving of the processes (process instances and the associated data) to continue by skipping erroneous process instances. As a result all successfully written objects are also deleted and the archiving process for this process data is completed. The erroneous process instances with the associated data remain in the database (the main persistency).
Use this option if a few corrupted process instances prevent the archiving of a large number of process instances and associated data. End of the recommendation. |
Schedule the archiving process and specify if the process data that has been archived successfully is to be deleted automatically.
Enter the technical settings.
Choose Start Write Session.
To schedule the delete job separately, choose the Delete tab in the Java Archiving Cockpit. There are no BPM-specific parameters.
More information: Java Archiving Cockpit