Basis Customizing (XML DAS Archiving)

Customizing of the Home Paths

You define here for which physical home path there should be a logical home path.

Note the following naming conventions:

• To avoid conflicts with other archiving objects, the home path should always begin with /<SYSID>/<CLIENT>/<OBJECT>/ , where OBJECT is replaced with the relevant XML archiving object.

• You can only use the key words in angled brackets, because only these are replaced by the system.

• The logical home path delivered is always DEFAULT_WITH_CLIENT.

Configuration of XML DAS

You specify here which XML DAS is used by making the following entries.

• RFC Destination

  You enter the HTTP connection here that you have created in Display and Maintain RFC Destinations ( transaction SM59).

• Active

  You define here which XML data archiving service the application communicates with.

• Check total

  You define here whether a check total should be evaluated or not when importing resources.

  If you set this indicator, a check is made when importing resources whether it is still the same resource that was originally archived, and that there have been no changes.

Synchronization of the Home Paths

You define here the home paths that are to be used by XML archiving objects. You can determine existing home paths, create new ones, or delete home paths created inadvertantly.

You can only archive data once you have created the home path relating to the XML archiving object.

• Determine

  The logical home paths are analyzed for all XML archiving objects, and the resulting home paths output. Any placeholders (such as <SYSID>) are expanded. No check is made whether the home paths can actually be created in XML DAS or already exist there.

• Create

  The home paths are transferred to the XML DAS that is identified using the HTTP connection determined for each client. All home paths not available are created. If a home path exists already, it is not changed.

• Store

  You can optionally specify a store. This store is then assigned to all of the newly created home paths. The prerequisite for this is that the store is known to the XML DAS (see below: administration function Define Archive Stores). The store specified can be changed provided no data for this home path has been archived (administration function Assign Archive Stores).

• Delete

  This action deletes the home paths entered in Customizing in the relevant XML DAS. If these home paths have already been used, nothing is deleted.

• For current client only

  If you select this checkbox, you restrict the selection of the home paths to those paths for which the entries exist in archiving object-specific Customizing.