Show TOC

Background documentationSecurity of Stored Data in SAP NetWeaver ILM

 

Security of Archived Data in the File System

When storing archived data in the file system, you have read and write access to the file system with the technical system user of the SAP system. The system temporarily moves the archive files to the file system and then deletes them after forwarding them to the ILM store. The archive files in the file system and the ILM store, are stored not in plain text but in binarily text in an SAP-specific, compressed format.

A logical path define the storage location of the archived data in the file system. You need to specify this path in Customizing for the archiving object.

For more information:

Data Archiving in the SAP NetWeaver Library

Security Guide for ADK-Based Data Archiving in the Security Guide of the SAP NetWeaver Library

Security of Data in the ILM Store

To guarantee the non-changeability of data and the protection from early deletion, the resources (archive files) and their higher level collections (hierarchy nodes of the store) are stored on an ILM-certified WebDAV server.

For more information: Providing WebDAV Server for ILM Store

Metadata Security in the Store Hierarchy

To manage the store hierarchies, the service that you use to manage ILM stores saves the metadata to the system database. Depending on which service you use, the storage location of the metadata is:

ILM Store Service

Metadata Storage Location

Storage and Retention Service (SRS)

Database of the AS ABAP on which the SRS runs

XML Data Archiving Service (XML DAS)

Database of the AS Java on which XML DAS runs

XML DAS uses the database pool alias SAP/BC_XMLA.

You can guarantee the security of the metadata with the standard function of the database you are using.

For more information: Database Access Protection, Security Aspects for Database Connections in the SAP NetWeaver Library.

Backup of Complete Data in the Retention Warehouse System

To ensure that the dataset you are managing in Retention Warehouse is still complete after the transfer from the legacy system, use the checksums function before and after the transfer and the ILM-compliant conversion of the data (archive files).

For more information:

Generating Checksums Prior to Archive File Conversion

Generating and Comparing Checksums After ILM Archive File Conversion