Customizing (Steps 4-8)


Creating an HTTP Destination for XML DAS (Step 4)

       1.      Call transaction SM59.

       2.      Choose Create.

       3.      Enter the necessary information:

                            a.      RFC destination: <new name> (for example XML_ARCHIVE_FOR_Q2W)

                            b.      Connection type: G  (HTTP Connection to external server)

                            c.      Description: <anything you like> (such as XML Data Archiving Service)

                            d.      Choose Save.

                            e.      Technical settings:

Target host: <address of J2EE Engine host> (for example

Service No.: <http port> (for example 58400)

PathPrefix: /DataArchivingService/DAS

                              f.      Logon/Security:

Security Options: Basic Authentication, SSL inactive

Logon: User: <one of the communication users from Step 2>

Password: <corresponding password for communication user from Step 2>

                            g.      Special Options:

HTTP Setting: HTTP Version – HTTP 1.1

HTTP Cookies: Accept Cookies – Yes (All)

       4.      Choose Save.

       5.      Choose Test Connection.

Activating the HTTP Destination You Created for Different Clients (Step 5)

This step and the following step (Activating the HTTP Destination and Checking the Existence of or Creating Home Paths) are client-specific. This means that they have to be carried out in every client from which archiving is intended.


       1.      In transaction SARA enter an XML archiving object (such as BC_SBOOK_X) and choose Customizing ® Basis Customizing ® Configuration of XML DAS

       2.      Choose Maintain ® New Entries

       3.      Enter the necessary information:

                            a.      RFC Destination: <name entered under Creating an HTTP Destination> (such as XML_ARCHIVE_FOR_Q2W)

                            b.      DAS Active: X

                            c.      Check Sum: X (or space, if integrity checks are to be disabled)

       4.      Choose Save.

Checking the Existence of Home Paths (Step 6)

Logical home path for every XML archiving object

In transaction SARA enter the XML archiving object you are interested in (for example BC_SBOOK_X) and choose Customizing ® Archiving Object-Specific Customizing ® Technical Settings

Under Logical Home Path you should see DEFAULT_WITH_CLIENT or an application-specific logical home path.

Assigning a home path to the logical home path

In transaction SARA enter your XML archiving object (for example BC_SBOOK_X)  and choose Customizing ® Basis Customizing ® Customizing of Home Paths

Here you should see that the home path /<SYSID>/<CLIENT>/<OBJECT>/ is assigned to logical home path DEFAULT_WITH_CLIENT. An application-specific home path may have a different home path assigned to it.

Do not change any of the settings or entries without good reason.

Before you continue, you must establish a connection to a running XML DAS (test using SM59, see Creating an HTTP Destination)

Synchronization of Home Paths (Step 7)


       1.      In transaction SARA enter your XML archiving object (for example BC_SBOOK_X) and choose Customizing ® Basis Customizing ® Synchronization of Home Paths

       2.      Choose Production Mode and Execute.

The home paths you defined above are now pushed to the XML DAS.

Usually, this action only needs to be performed once during initial setup. (However, if you have created a new XML archiving object, you have to synchronize the home paths again). For more details see the program documentation available under .

Assigning an Archive Store to Your Home Path (Step 8)

·        In the XML DAS Administration, choose Assign Archive Stores.

·        For each home path you are interested in (the ones you synchronized in Step 7) select the desired archive store from the drop down menu and choose Save in the same row.

Testing the connection to XML DAS: It is possible to test the connection to XML DAS from within Archive Management in transaction SARA, by using the available  button. However, this is only possible if at least one XML archiving session is listed in archive management. In other words, an XML archiving object has to already exist and data has to have been archived with that archiving object. The function returns technical information and shows whether or not a connection exists to XML DAS.