Show TOC

 XML DAS AdministrationLocate this document in the navigation structure


The XML Data Archiving Service (XML DAS) is part of a standard Application Server Java (AS Java) installation and can be used for archiving data both from Java and ABAP application systems.

The XML DAS comes with an administration tool called the XML DAS Administration.

Implementation Considerations

An AS Java installatin contains the following for XML DAS:

  • The applications and in the Web Container

    The servlet /archtech/xmldasinitservice is responsible for creating User Management Engine (UME) roles and for initialising the MBeans.

  • The database pool alias SAP/BC_XMLA for

Before you can begin XML DAS archiving you must set up the different components involved and configure your systems.

More information: Archiving using XML Data Archiving Service (XML DAS)


XML-based data archiving involves two systems that are logically, and usually also physically, separate.

  • Application system, that needs to archive its data
  • Archiving system - the AS Java containing the XML DAS

During XML-based archiving the meta data and the property indexes used for value-based searches of archived data are stored in the database of the AS Java. The actual data that has been archived is stored in a storage system, which is connected to the AS Java. To configure your file or WebDAV system for XML DAS archiving, you use the XML DAS Administration, shown in the figure below.

You can reach the XML DAS Administration via the address http://<Host of J2EE Engine>:<HTTP port>/DataArchivingService/DAS


For example: http://localhost:50000/DataArchivingService/DAS


After you have set up your systems and made the archive stores available, you must use the XML DAS Administration to perform the following tasks:

  1. Define and test the archive stores:

    The concept of an archive store is used to refer to a location (WebDAV collection or file system directory) within a storage system. Using the XML DAS Administration, you must first define archive stores to be able to test their availability. In case of WebDAV servers accessed via proxies, register the proxy for each archive store.

    More information: Archive Store Management

  2. Synchrinize the home paths between application systems and XML DAS.

    The XML DAS Connector of an application system provides a function to propagate new home paths to the XML DAS. Make sure that this function is executed so that XML DAS synchronizes the "known" home paths with new ones required by the applications.


    SAP recommends that, if possible, you perform this necessary step from within the application system. This is because only here application-specific customizing can be taken into account.

    • In case of an ABAP application, use the Basis Customizing of XML Archiving in transaction SARA instead of the XML DAS Administration. This function determines and synchronizes home paths for all existing XML archiving objects, using reserved key words.
    • In case of a Java application, the home paths are synchronized automatically, when the Java Archiving Cockpit is started.

    More information: Home Path Synchronization

  3. Assign home paths to archive stores.

    Using the XML DAS Administration, you must assign an archive store to every home collection or application collection you want to use for archving.

    More information: Archive Hierarchy and Store Assignment

In addition the XML DAS Administration offers the following features for packing and unpacking resources:

More information: Packing

You can view the archive hierarchy, including details about the collections and resources in the hierarchy. You can also view all metadata managed by the data archiving service (XML DAS).

More information: ILM Store Browser