In this edition we will be covering up with basic Data and Database activities which comes under Operation tab. But before that let us have some idea for XML DAS for this we need a role SAP_ARCH_XMLDAS_VIEW . XML DAS can be used for archiving data for both ABAP and Java application.
This service can be execute on XML DAS can run on a Java application system or on a separate AS Java.
XML-based data archiving involves two systems that are logically, and physically separate.
● Application –system, that needs to archive its data.
● Archiving– system – AS Java containing the XML DAS.
During XML-based archiving the metadata 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.
ILM Store Browser – To make an ILM archive store
available for use by XML DAS, you need to register the storage location and its definition data in XML DAS Administration.
Here we punch in and assign the home paths under which applications store archived resources.
During data archiving with XML DAS, a resource in the form of an XML file is created for each data object. The system uses a predefined home path to write
resources to the hierarchically organized archive store in one step. Each resource has its own URI (Uniform Resource Identifier).
Define Archiving Sets (in the Java application system) or XML Archiving Objects (in the ABAP application system) that bundle data into complete business objects during XML DAS data archiving. Define which archiving programs are to be executed.
This is where you register stores and assign the home directory under which applications store archived resources.
Defining Archive Stores – We will be punch in the details Archive Store Management tab
- Archive Store: details new archive store
- Description: a relevant short description of file server ,
- Default: points to an archive store as a default archive store.
- Store Type: we can select option as File System and WebDAV System from drop down . These entries are applicable if we go for proxy server.
- Proxy Host/Port
HOME PATH SYNCHRONIZATION
In the Synchronize Home Path screen we mark the details for creating a new home collection, or delete an existing one.
You must fill in the following information:
- Home Path: Ensure the path should begins and ends with / (slash), here we can punch in the Directory path (New )If it is not existing.
- Action: Choose Insert a New Home Collection, or Delete Existing.
Home Collection, according to the action you wish to perform.
- Context: Optional
- Archive Store: Select the choices from the dropdown box.
Archive Hierarchy and Store Assignment –
Here we can view the entire existing Archive path and there archive store with detail info like archive path properties.
In Archive path Properties (Sub Window on RHS)
- Archive Path– Info related to the path of the collection displayed in the hierarchy.
- Collection Type– Info for the collection is an application, system, or home collection.
- Creation Time– time details when the collection was created.
- Creation User– User log in detail’s who was responsible for collection.
- Archive Store– shows to which archive store the collection has been assigned. If there is no details , the collection has not been
assigned to any archive store yet.
- Assigning Collections– With this function you assign or un assign collections to archive stores.
Packing– We will be using this option for compressing or decompressing the resources after archiving. The XML DAS Administration offers three functions that have to do with the packing of resources: Pack Resources, Unpack Resources, Display (Un)Pack Progress. Ensure the Archive Path for the resources you want to pack or unpack. Make sure it ends with a /.
JAVA ARCHIVING COCKPIT- To browising the Java Archiving cockpit option ,
For accessing this option we need role SAP_ARCH_SUPERADMIN. The Java Archiving Cockpit is the central user interface
for the administration of XML DAS archiving sessions created by an application running in an Application System Java (AS Java).
The Java Archiving Cockpit offers functions for manually starting, or scheduling, the write and delete phases, and for configuring the properties of XML archiving sets. It also contains an archiving monitor for checking the progress and state of archiving sessions.
Archiving Monitor-Here we can manage and monitor the refresh, remove and cancel archiving Session.
Hierarchy – we can see the hierarchy view for all systems in which archiving sets for, even if we have not archived any data so far.
Here we can add or delete collection manually as well as branch directly.
Write -This is where you schedule the write run for each archiving set.