Archiving Object-Specific Customizing 

Procedure

To maintain the archiving control parameters for an archiving object, proceed as follows:

Select the archiving object in the list on the initial screen of transaction AOBJ, and choose Customizing settings under Dialog Structure.

Variants must be maintained for each client. All other values are cross-client.

You can set the following parameters:

Logical file name

Logical name for the archive file used for platform-independent data storage.


You must have maintained the logical file name using transaction FILE (Logical File Path Definition).

Server selection

You use this to select the servers where the archiving programs are to run in the background.

Archive file size

If one of the following parameters is exceeded during writing of an archive file, the system automatically creates a new archive file.

The absolute maximum size of an archive file is 2 GB.

Settings for delete program
The archived data records in the database are usually deleted. Under certain circumstances, however, this deletion is only logical, that is, when the Delete indicator is set The physical deletion occurs later in a postprocessing program.

Commit counter
Number of data objects after which the delete program sends COMMIT to the database.

Test session variant
Specify the delete program variant for the test session.

Production session variant
Specify the delete program variant for the production system.

Use the Variant pushbutton to maintain variants for the delete program.

The program variants specified under Test session and Production session are client-dependent. They must be created in each client under the same name, with the same parameters.

The delete jobs are not automatically started.

The delete jobs are started automatically by the write program immediately after an archive file is finished. If files are to be stored in a storage system, you can specify whether the data is to be deleted from the database before or after the files are successfully stored.

The delete jobs are started by events. The name of the event must be entered in the Event field. If the event requires a parameter be set, enter the parameter in the Parameter field.

Controls whether the archived data objects are to be added to the index.

The Build index check box is only displayed if the indicator is set in transaction AOBJ (Definition of Archiving Objects).

Postprocessing program settings

If you have selected an archiving object that uses a postprocessing program, you can maintain the following parameters:

Use this to set a production variant of the postprocessing program.

Use the Variant pushbutton to maintain the production session variants.

Controls whether the postprocessing program is automatically called after the delete is finished.

The postprocessing program then only starts when the last delete program of the archiving session has completed and no archive file has the status Archiving completed, Archiving running, or Delete running.

Data storage in storage system

If a storage system is connected through the Content Management Service and you want to store files in a storage system, you can set the following:

Name of the Content Repository

Controls whether an archive file is automatically stored in the Content Repository.

The time point at which the files are moved to the Content Repository is determined by how the archive files are processed after they are created:

- Delete before storage

The files are moved to the Content Repository after the delete program has processed the file in production mode. If the delete program is running in test mode, the files are not automatically stored after the delete program has finished.

- Store before delete

The files are moved to the Content Repository after the write program has written the archive file and before the delete program starts. This means the delete program cannot process the files until they are successfully stored.

The Delete prog. reads from stor.system check box specifies whether the delete program reads the data to be deleted from the storage system or the file system.

If the delete program option Start automatic. is selected, the delete program is called after file storage is completed. In this case, it makes no difference whether the delete program is running in test mode or production mode. Similarly, if the After event option is selected, the delete jobs are scheduled and automatically started after the specified event occurs.

Save your entries, and return to the initial screen of transaction AOBJ.