Components and Deployment Scenarios 

Components for XML Archiving

The following components are the principal constituents of the XML archiving technology:

●      XML Data Archiving Service (XML DAS): A Java Enterprise Edition (Java EE) 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. (Not discussed in this guide).

●      XML Archive API for Java: An API for accessing the XML DAS from within the Application Server Java (AS Java). It is provided in the form of a Java EE Library.

●      GUIs:

○       The XML DAS Administration is available as a SAP NetWeaver Administrator (NWA) plug-in.

○       For the XML DAS Connector for ABAP, the local archiving administration is provided by transaction SARA.

○       For the administration of Java archiving sessions, another NWA plug-in is provided, called the Java Archiving Cockpit.

Deployment Scenarios

The XML-based archiving technology offers different deployment scenarios. Understanding these scenarios is essential for an appropriate configuration. The two most common ones are same system and distributed system deployments:

Same System Deployment

In this scenario both the archiving client (including the archiving Job Beans and the local archiving session management), and the XML DAS are running on the same host. The HTTP destination is used for local communication. Only one NWA is used, which includes the Java Archiving Cockpit and the XML DAS Administration. In this case users 2 and 3 can be identical. This deployment is most often used in local test or development environments.

Distributed Systems Deployment

In this scenario the XML DAS runs on a different host than the archiving client. The HTTP destination determines the remote communication. The scenario is probably most often used in production environments. It allows you to use a single XML DAS for several application systems.

Figure 1: Distributed Systems Deployment Scenarios in XML-Based Archiving

¹ User 1 is the technical user between application system and XML DAS, while Users 2 and 3 are NWA users. See Creating Users and Assigning Roles for more information. Note that User 1 is also used in a same system deployment scenario.

² SLD may, but does not have to be installed on a different host; it is used to register XML DAS and its archive stores.