Executing and Monitoring 
The following archive objects are available for archiving in SAP Web Application Server:
Objects in SAP Web AS |
Archiving Object |
|---|---|
User changes |
US_USER |
Authorization changes |
US_AUTH |
Profile changes |
US_PROF |
Work items |
WORKITEMS |
IDocs |
IDOC |
Table changes |
BC_DBLOGS |
Link entries ArchiveLink |
ARCHIVELNK |
Archive administration data |
BC_ARCHIVE |
SAP product |
PRODUCT_MD |
For more information about using these archiving objects, see Data Archiving in SAP Web AS.
Note
SAP Business Information Warehouse (SAP BW) also has an archiving solution, but this is different to archiving in SAP Web AS. For more information about BW archiving, see Data Archiving.
You must make various system settings during data archiving to control the archiving process. You make these settings in archiving customizing, which you access from archive administration by choosing Customizing. There are three areas:
Basis Customizing
You can specify the file names and paths for the archive files for ADK-based archiving. You can define file names and paths as client-specific (transaction FILE) or cross-client (transaction SF01). For XML-based archiving, you must also configure the home paths and the XML data archiving service used.
Cross-Archiving-Object Customizing
The settings you make here apply to all archiving objects. This includes, for example, the settings for interrupting the archiving session or the definition of a server group for background processing.
Archiving-Object-Specific Customizing
You can define customizing for individual archiving objects, for example the maximum size of an archive file, whether the delete program is to run in the test or productive mode, or whether storage (ADK-based archiving) is to take place before or after deletion. You can use the Archive Routing funtion to define rules and conditions for saving the archive files in particular content repositories.
For more information about archiving customizing, see Customizing.
The following tools are available to help you schedule, control, and monitor archiving jobs:
Archive Administration
To schedule archiving jobs (writing, deleting, and so on), you use archive administration (transaction SARA). This transaction also gives you access to most other user activities in data archiving, for example storing and finding archive files and archiving customizing.
For more information, see Archive Administration (ADK-based archiving) and Archive Administration: XML Archiving.
Data Archiving Monitor
The data archiving monitor (transaction SAR_SHOW_MONITOR) allows you to analyze information relevant to archiving. For example, it provides an overview of all archiving objects that have run, detailed information about the individual archiving sessions, and a progress display for the processing of archive files. To ensure that the relevant information is updated, you must activate the data archiving monitor in cross-archiving-object customizing (see above).
The data archiving monitor is part of the CCMS monitor set (transaction RZ20) and can be found under .
For more information, see Data Archiving Monitor.
Logs
You can call this function by choosing Logs. It provides a central point of access to the most important logs generated by data archiving, for example the job overview, the job log, the spool list, and the application log. These logs provide information about the progress of the archiving and the processing of objects to be archived.
For more information, see Logs.