Show TOC Start of Content Area

Background documentation Archiving Data and Monitoring Archiving Activities  Locate the document in its SAP Library structure

The following archiving objects are available for archiving in SAP Web Application Server:

Objects in SAP Web AS

Archiving Objects

User Master Change Documents: User Authorizations

US_USER

User Master Change Documents: Authorizations

US_AUTH

User Master Change Documents: Authorization Profiles

US_PROF

Workitems

WORKITEMS

IDocs

IDOC

Customizing Table Changes

BC_DBLOGS

ArchiveLink Entries

ARCHIVELNK

Archive Management Data

BC_ARCHIVE

SAP Product

PRODUCT_MD

For more information on how to use these archiving objects see Data Archiving in SAP Web AS.

Note

SAP Business Information Warehouse (SAP BW) also provides an archiving solution, which differs from archiving in SAP Web AS. For more information see Data Archiving.

System Settings for Data Archiving

As part of data archiving you must make different system settings for controlling the archiving process. The settings are made in archiving Customizing, which you can reach from Archive Administration by choosing Customizing. Customizing is divided into the following areas:

·        Basis Customizing

Here you can determine the file names and paths under which the archive files are to be created within the context of ADK-based archiving. File names and paths can be created for specific clients (transaction FILE) or cross-client (transaction SF01). For XML-based archiving you must also configure the appropriate home paths and the XML Data Archiving Service.

·        Cross-Archiving-Object Customizing

The settings you make here apply to all archiving objects. This includes for example settings for interrupting the write phase or entering server groups for background processing.

·        Archiving-Object-Specific Customizing

These settings apply to individual archiving objects and include, for example, determining the size of an archive file, indicating whether the delete program should run in the test or production mode, and specifying that the storage phase should occur before or after the delete phase (ADK-based archiving only). The Archive Routing function is used to establish rules and conditions for routing data to specific content repositories during the store phase of data archiving.

For more information on Customizing for Data Archiving, see Customizing.

Scheduling, Controlling and Monitoring Archiving Jobs

The following tools are available for scheduling, controlling and monitoring archiving jobs:

·        Archive Administration

Archiving jobs (write, delete, etc.) are scheduled using Archive Administration (transaction SARA). This transaction is also the central entry point for most other user activities in Data Archiving, such as data storage and retrieval, or 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) is used to analyze information relevant for data archiving. It offers an overview of all archiving objects that were used for archiving data, detailed information about the archiving sessions, and a progress indicator on the processing of archive files. In order for you to be able to view updated information you must switch on the Data Archiving Monitor in cross-archiving-object Customizing (see above).

The Data Archiving Monitor is part of the CCMS Monitor Group (transaction RZ20) and is available under SAP CCMS Monitor Templates Database Data Archiving.

For more information see Data Archiving Monitor.

·        Logs

This function can be accessed from within Archive Administration by choosing Logs. It offers central access to the most important logs generated during data archiving, such as job overview, job log, spool list and the application log. These logs provide information about the progress of the archiving sessions and the processing of the different objects during archiving.

For more information see Logs.

 

 

 

End of Content Area