Defining Logical Path and File Names

Use

Archive files are stored in the file system under a physical path and file name that is derived from a user-definable logical path or file name. The definition can be divided into the following steps:

...

       1.      Definition of the logical path name

       2.      Definition of the logical file name

       3.      Assignment of the logical fine name for the archiving object

By default, the system uses the logical file name ARCHIVE_DATA_FILE and the logical path name ARCHIVE GLOBAL PATH as defaults. Consequently, the names only need to be changed if they have to be adjusted to meet special requirements.

Prerequisites

·        If you intend to transfer the archive files to a storage system using the Content Management Infrastructure (which contains the ArchiveLink/CMS interface), you must ensure that this storage system has access to the archive files.

·        In the case of hierarchical storage management systems (HSM), you must ensure that the archive files can be written to the file system of the HSM system.

Defining Logical Path Names

...

       1.      Call transaction FILE.

Alternatively, from the initial screen for Archive Administration (transaction SARA), choose: Customizing ® Basis-Customizing® Cross-Client File Name/Paths .

       2.      Mark an existing file name, for example, ARCHIVE_GLOBAL_PATH, or choose New entries to enter a path name. The name should reflect its function.

       3.      Double click the dialog structure Logical File Path Definition in the substructure Assignment of Physical Paths to Logical Path. Double click to select a syntax group or create a new syntax group.

       4.      Assign a physical path name to the logical path name.

When assigning path names, the symbol <FILENAME> must appear at the end. This symbol is replaced at runtime by the physical file (or path) name. No part of the physical file name in the path name must be defined.

If you want to store your archive files, enter the placeholder <F=ARCHIVELINK> in the logical path. With <F=ARCHIVELINK><FILENAME> the files are created directly in the basis path of the content repository that has been assigned to the corresponding archiving object. This way you can avoid an internal copy process during the store phase.

You have created the subdirectory "data_archiving" for archive files in the global directory. You then specify a path name:

·         <P=DIR_GLOBAL>/data_archiving/<FILENAME> (Syntax group UNIX)

·         <P=DIR_GLOBAL>\data_archiving\<FILENAME> (Syntax group WINDOWS NT)

In a heterogeneous system landscape (such as UNIX and Windows NT servers) all system-specific syntax groups must be maintained. Ensure that the definitions for the various syntax groups point to the same directory.

       5.      Save your entries

Defining Logical File Names

Logical file names can be defined as client-specific (transaction SF01) or cross-client (transaction FILE). A client-specific definition always overrides a cross-client definition. Ensure, therefore, that in every client any unnecessary client-specific definitions are deleted.

The following describes the procedure for creating a cross-client definition using the transaction FILE. You create the client-specific definition in the same way using transaction SF01.

...

       1.      Call transaction FILE for cross-client file names.

Alternatively, from the initial screen for Archive Administration (transaction SARA), choose: Customizing ® Basis-Customizing® Cross-Client File Name/Paths.  

For client-specific definitions, from the initial screen for Archive Administration, choose: Customizing ® Basis-Customizing® Client-Specific File Names.

       2.      Mark an existing file name, for example ARCHIVE_DATA_FILE, or choose New entries to enter a new file name. The file name should reflect its function.

       3.      Double click the dialog structure Logical File Name Definition, Cross-Client.

You access the screen Change View "Logical File Name Definition, Cross-Client": Overview

       4.      Maintain the fields Physical File and Logical Path.

In the Physical File field, enter the required physical file name.

The following parameters are of particular interest here:

Ў        PARAM_1: Two-character application abbreviation (for example, HR, CO, MM) for the classification of the archive files in the system. The value of the definition is determined from the relevant archiving object at runtime.

Ў        PARAM_2: Single-character alphanumerical code (0-9, A-Z). If, when creating a new archive file, an existing file with an identical physical name would result in a conflict, the ADK increases this value by 1. This value must, therefore, always be a part of the physical name.

Ў        PARAM_3: This parameter is filled at runtime with the name of the archiving object. In archive management, this enables you to check the file contents or to store the archive files by archiving objects.

To enable maximum space in the name range for the archive file, the following entry is recommended:

<PARAM_1>_<DATE>_<TIME>_<PARAM_2>.ARCHIVE

In the Logical Path field, you assign the previously defined logical path name to the current logical file names. You can assign a logical path name to several file names.

       5.      Save your entries

Assigning a Logical File Name to the Archiving Object

Once the logical path name and file name have been defined, the logical file name must be assigned to the archiving object. Proceed as follows:

...

       1.      In the Archive Administration initial screen (transaction SARA), enter the name of the archiving object and choose Customizing. Under Archiving Object-Specific Customizing, choose Technical Settings.

       2.      In the Logical File Name field, enter the required logical file name.

       3.      Save your entries

Result

You have defined a logical path and logical file name and have assigned them to an archiving object. By doing this, you have specified the platform-specific physical path and name under which the archive files (which were created during archiving using this archiving object) were stored.