Data Archiving 

This section provides you with information on data archiving specific to a process integration environment.

More information: XML-based Archiving.

Integration Engine

The message store on the Integration Engine is the component for which data archiving is most critical. Depending on the integration processes that are running on the Integration Server, large numbers of messages with large message sizes may be persisted in the Integration Engine. Therefore, the archiving of (processed) messages must be carefully planned and monitored.

Standard archiving processes are available to be scheduled as needed, based on the Archive Development Kit and on the Archive Administration transaction (SARA). It is possible to run archiving jobs in parallel, which means that archiving is scalable.

Fast growing tables to be monitored are those holding message processing data. To prevent these tables from growing too much, several jobs are scheduled automatically. These either archive outgoing messages or execute single-record deletion (every time a message is processed, it is subsequently deleted from the related tables). In addition, the complete tables can be dropped by activating a drop-delete job.

Make sure you save any entries from the respective tables that are still required.

The fastest growing tables are those that contain the application payload in a compressed form.

●      SXMSCLUP

●      SXMSCLUR

More information: Defining Interfaces and Retention Periods for Archiving and Archiving and Deleting.

Business Process Engine

Work items are created when an integration process is executed by the Business Process Engine. This is similar to the execution of a business workflow. If you want to archive an integration process, you therefore must archive the corresponding work items.

More information: Archiving Work Items.

Archiving work items enables you to display the archived work items for a specific object. You can use this function, for example, if you want to display the archived integration process with which a specific message was processed.

Fast growing tables to be monitored are:

●      SWWLOGHIST

All information about one process step.

●      SWWWIHEAD

Header information for processes.

●      SWWCNTP0

Context information for processes, for example, references to messages.

Adapter Engine

The following table represents the persistence layer of the Adapter Engine, which means that it stores incoming and outgoing messages.

●      XI_AF_MSG

A full archiving solution is provided for this table.

More information: Background Processing.

Security Archiving

Messages with S/MIME security settings can be archived by using the Runtime Workbench or the SAP NetWeaver Administrator.

More information: Security Archiving.