Configuring the XML Data Archiving
Service
You set up the XML DAS in the following steps:
● Define an archive store.
● Create a home path for your archiving set.
● Assign an archive store.
Defining an archive store: A prerequisite for archiving (storing the resources) is either one or more WebDAV servers or one or more directories in an appropriately secure and large file system. For a quick minimum setup (file system), start with the second bullet.
● Choose an empty or create a new root collection in your WebDAV system.
The XML DAS authenticates against WebDAV servers using user and password specified in the HTTP destination created for that purpose and referenced in the definition of an archive store done in the XML DAS Administration.
● In case a file system is used, the directories chosen must be accessible (read/write/create dir) for the operating system user <sid>adm in case of a UNIX system, and SAPService<sid> in case of a Windows system.
Choose an empty or create a new directory or directories and make sure they are globally mounted to all servers belonging to the Application Server Java (AS Java) running the XML DAS.

You want to store your archived data on host “myfileserver”. Choose a name for your directory and create it on your host; for example “archive_directory”. Now you must make this new directory accessible to your AS Java.
● For a Windows server you might have: \\myfileserver\archive_directory
● For a Unix server you might have: /mountedfilesystem/archive_directory

To prevent unauthorized access or harmful alteration or deletion of resources or directories in the file system, give the appropriate access privileges only to SAPService<sid> or <sid>adm, respectively.
Do not manually create or delete directories or files once the archive store root directory is fixed.
If you are using a WebDAV system you have to create a destination in the AS Java on which the XML DAS is running. The destination points to the WebDAV server you want to use. You must do so before you can begin using the XML DAS Administration to define an archive store.
1.
Go to the
Destination
Service integrated in the SAP NetWeaver Administrator (NWA).
2. Select HTTP Destination and choose DASdefault:
3. In the Connection and Transport tab strip, enter or choose the following information:
○ Connection
URL: http://<Host of XML DAS>:<HTTP port>/DataArchivingService/DAS
○ SSL Server Certificates
Select Ignore Server Certificates
4. In the Logon Data tab strip, enter or choose the following information:
○ Authentication:
Select Basic (User ID and Password)
○ Basic Authentication
Username: <XML DAS communication user ID created according to Creating Users and Assigning Roles>
Password: <password of XML DAS communication user>
For a detailed
description of how to define archive stores see Define under
Archive Store
Management.

This step no
longer needs to be executed using XML DAS, because it is done automatically
after the creation of the destination and the first access to the
Java Archiving
Cockpit in the application system.
Prerequisite: To be able to assign collections to archive stores, the home paths need to have been created and synchronized and archive stores need to have been defined previously.

There are several
important considerations you must keep in mind before assigning collections to
archive stores. Do not proceed without reading these considerations first
under
Archive
Hierarchy and Store Assignment.
You can assign
collections to archive stores using the
Archive Hierarchy and
Store Assignment function of the XML DAS Administration.
1. Choose an appropriate collection in the archive path hierarchy.
The Archive Store Assignment window appears on the right side of the screen.
2. To assign an archive path (collection) to an archive store, use the drop down list of the field help to choose an appropriate archive store and then choose Assign.
To remove the assignment of an archive store from the collection, choose Unassign.