Show TOC

Defining Logical Path and File Names.Locate this document in the navigation structure

Use

To specify the platform-specific physical path and file name under which the archive files (which were created during archiving using this archiving object) are to be stored, you define logical path and file names assign them to the archiving object.

Note

By default, the system uses the logical file name ARCHIVE_DATA_FILE and the logical path name ARCHIVE GLOBAL PATH. 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 Service (includes ArchiveLink and the CMS interface) , you must ensure that this storage system has access to the archive files.

  • In the case of HSM systems, you must make sure that the archive files can be written to the file system of the HSM system.

Procedure

1. Defining logical path names

  1. Start transaction FILE.

    Alternatively, from the initial screen for Archive Administration (transaction SARA), choose Start of the navigation path Customizing Next navigation step Basis Customizing Next navigation step Cross-Client File Name/Paths End of the navigation path.

  2. To enter a new path name, select an existing path name, such as ARCHIVE_GLOBAL_PATH, or choose New Entries. This must be as descriptive as possible.

  3. In the Logical File Path Definition dialog structure, double-click on the Assignment of Physical Path and Logical Paths substructure.Double-click to select a syntax group or create a new syntax group.

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

    Caution

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

    Recommendation

    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 archiving object. This way you can avoid an internal copy process during the store phase.

    Recommendation

    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.

  1. Save your entry.

2. Defining Logical File Names

Note

Logical file names client-specific (transaction SF01) or cross-client-specific (transaction FILE). A client-specific definition always overrides a cross-client definition. Therefore, ensure 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. Start transaction FILE for cross-client file names.

    Alternatively, from the initial screen for Archive Administration, choose Start of the navigation path Customizing Next navigation step Basis Customizing Next navigation step Cross-Client File Name/Paths End of the navigation path.

    For client-specific definitions, from the initial screen for Archive Administration, choose Start of the navigation path Customizing Next navigation step Basis-Customizing Next navigation step Client-Specific File Names End of the navigation path.

  2. To enter a new file name, select an file path name, such as ARCHIVE_DATA_FILE, or choose New Entries. This must be as descriptive as possible.

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

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

  4. Maintain the Physical File and Logical Path fields.

    In the Physical File field, enter the physical file name you require.

    The following parameters are of particular interest here:

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

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

    • PARAM_3: At runtime, this parameter is filled with the name of the archiving object. In archive administration, this enables you to check the file contents or to store the archive files by archiving object.

      Recommendation

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

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

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

  5. Save your entry.

3. Assigning a Logical File Name to the Archiving Object

Once you have defined the logical path name and file name, you need to assign the logical file name to the archiving object. Proceed as follows:

  1. In the initial screen for Archive Administration, enter the name of an 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.