Generally you make your basis Customizing settings when you implement the XML Data Archiving Service. This Customizing area differs considerably from Basis Customizing in ADK.
When making your entries, adhere to the following naming convention:
· To avoid conflicts with other archiving objects your home path should always begin with /<SYSID>/<CLIENT>/<OBJECT>/, whereby OBJECT will be substituted by an XML archiving object.
· You can only use the key words shown here, identified as such by < >, because only these are recognized and substituted by the system.
· The standard is always delivered with the logical home path DEFAULT_WITH_CLIENT.
The home path /<SYSID>/<CLIENT>/<OBJECT>/MY_HOME/ becomes /C11/000/BC_SBOOK_X/MY_HOME/ after synchronization with XML DAS from system C11, client 000, using archiving object BC_SBOOK_X.
Here you determine which XML DAS is to be used by entering information or making settings in the following three columns.
· RFC Destination
Here you enter the HTTP connection that you entered in Display and Maintain RFC Destinations (transaction SM59).
Here you determine with which XML Data Archiving Service the application system communicates.
You can list as many entries as you like under RFC Destination. However, only one HTTP connection may be activated. If more than one are activated you may encounter inconsistencies. For more information see the F1 Help for this column.
· Check Sum
Here you determine whether or not a check sum is to be verified when resources are read.
If this indicator is activated, a check is run during the reading of a resource to make sure that it has not been changed or modified in any way since it was archived, and that the resource is the resource that was originally archived.
SAP recommends that you always activate this indicator, because it does not have any significant effect on access performance. Setting the indicator ensures you that the resource was not modified.
Here you determine the home paths that are to be used by XML archiving objects. You can determine already existing home paths, create new ones or delete home paths that were created accidentally.
You cannot archive any data until you have created a home path for your XML archiving object.
The program analyzes the logical home paths for all XML archiving objects and then lists the corresponding home paths. Key words, such as <SYSID>, are substituted. The program does not check whether it is possible to create these home paths in XML DAS or whether they already exist in XML DAS.
The home paths are transferred to XML DAS, which is identified via the HTTP connection that was entered for each client. All home paths that do not yet exist are created. If a home path already exists, the program will not make any changes to it.
· Archive Store
You have the option to enter an archive store. This archive store is assigned to all newly created home paths. However, the archive store has to be known to XML DAS (see below: Administration Function Define Archive Stores.) You can change the archive store you entered, as long as no data has been archived yet for this particular home path (Administration Function Assign Archive Stores).
This action deletes the home paths entered in Customizing from their corresponding XML DAS. If these home paths have already been used, nothing is deleted.
· Only for Current Client
If you mark this check box you restrict the selection of the home paths to those paths for which entries have been made in archiving-object-specific Customizing under the current client.
This Customizing function is described in detail in the program documentation, which can be reached via . Also see the corresponding F1 Help for each area.