The following configuration steps are aimed at data archiving administrators who want to use XML archiving objects and run, test and monitor the XML Data Archiving Service and developers of XML archiving objects.
Before you begin you should be familiar with the concepts of XML-based archiving. For more information see:
To be able to follow these configuration steps you need to have an SAP J2EE Engine 7.00 installed. A standalone J2EE Engine is sufficient. An SAP NetWeaver AS add-in installation is possible as well.
The following components are the principal constituents of the XML data archiving technology:
· XML Data Archiving Service (XML DAS): A J2EE enterprise application, which processes the incoming archiving requests and manages the archives.
· XML Archive API for ABAP: An API for accessing the XML DAS from ABAP archiving objects.
· XML Archive API for Java: An API for accessing the XML DAS from within the SAP J2EE Engine. It is provided in the form of a J2EE Library (not discussed in this guide).
Ў The XML DAS Administration is available as a JSP-based browser application.
Ў For the XML DAS Connector for ABAP, the local archiving administration is provided by transaction SARA.
Ў For the administration of J2EE archiving applications a central WebDynpro-based user interface is currently being developed.
The following figure gives an overview of the configuration steps necessary for XML archiving for ABAP applications and which areas of XML data archiving these steps affect or where exactly they are carried out.
This is only an example of a data archiving landscape. It is also possible to have the J2EE Engine running as an add-in of the same SAP Web AS installation, for example, or to have a separate file or WebDAV system, or other configurations.
The figure shows the following procedure steps needed to configure the XML data archiving environment for ABAP applications: