Execute APPEND in compatibility mode

APPEND_COMPATIBILITY_MODE

X

Enumeration

<empty> - disabled

X - enabled

If storage does not support append to already created binary files, then the append command is simulated.

Default retention implementation

DEFAULT_RETENETION_IMPL

Enumeration

<empty> - disabled

X - enabled

The cockpit will show you the default retention implementation option instead of the DataFrigde implementation option. This setting will only affect if DataFridge is present on the service system. In other cases default implementation option is shown as default.

License expiration reminder (days)

LICENSE_REMINDER_DAYS

30

Repair multipart in request

REPAIR_REQ_MULTIPART

Enumeration

<empty> - disabled

X - enabled

Repair functionality for the repair of HTTP requests containing multipart that cannot be read by standard SAP functionality.

Write data size to logs

WRITE_DATA_SIZE_TO_LOG

Enumeration

<empty> - disabled

X - enabled

Write data size to logs. As a possible performance loss, we have this on the switch. If we perform read or write on a document, its content size will be written to a log. This should ease up the fixing process and speed up problem analysis.

Write performance statistics

WRITE_PERFORMANCE_STATS

Enumeration

<empty> - disabled

X - enabled

Write performance statistics. Chosen Actions and Parameters will be written to a table for further analysis. Main table /DVD/CRP_STAT, Actions are stored in /DVD/CRP_STATA and parameters in /DVD/CRP_STATP.

Write statistics to logs

WRITE_STATS_TO_LOG

Enumeration

<empty> - disabled

X - enabled

Write runtime statistics to service logs. This is mainly aimed at runtime analysis and troubleshooting.

Raise error when storing empty data

RAISE_EMPTY_DATA_EXCEPTION

X

Enumeration

<empty> - disabled

X - enabled

Test report RSCMST expecting different behavior on different SAP releases for storing documents with empty data. You can choose whether you want to raise an exception (service return code 500) or you want to pass such a request (return code 0).

Delay for registration job (seconds)

REG_JOB_DELAY_SEC

20

Minimum 0

Maximum 2147483647

Registration job DVD_RM_REG_DOCUMENT is scheduled after the successful creation of the file in storage. To be able to identify archiving sessions for a given Document ID, we need to delay the registration job at least to the moment when the Document ID is updated in the ADMI_FILES table. Delay comes in handy also when you plan to get retention date and legal entity from infrastructure which is built after successful creation of the file.

Retention registration enabled

REG_RET_ENABLED

Enumeration

<empty> - disabled

X - enabled

Automatic registration of the files for retention management can be switched ON or OFF by this setting. When settings are ON, mentioned job DVD_RM_REG_DOCUMENT is scheduled after each successful creation of the file.

Auto <Source ID>_LAST_TS

<Source ID>_LAST_TS

0

Timestamp value in the format

YYYYMMDDhhmmss

When you use the report /DVD/CRP_RM_REGISTER_DOCUMENT or use transaction /DVD/CRP and choose Manual registration of documents. You can register all documents for a specific Source ID from the last execution of the report. This parameter is holding the last execution of the report for Source ID.

Add file extension to name

ADD_FILE_EXTENSION_TO_NAME

Enumeration

<empty> - disabled

X - enabled

Enables adding file extension to name. File extension is recognized from the mime type of the file and is stored in the external ID of the documents. Not all storages support this feature.

Unsupported Storages:

BLOB - BLOB Storage (Primary Database)
BLOB_ORA - ORACLE BLOB storage

Max size of the container (kB)

CONT_SIZE_THRESHOLD_KB

100000000

Minimum 0

Maximum 2147483647

For each Source ID, you can specify a prefix for containers that will be created on specified storage (more details in the section Source to storage mapping). Containers are then created with the following names <container prefix><sequence number>. During the first creation of the file, a container is automatically created with sequence number 0. This parameter is limiting how much data can be stored in one container in kB. When this size threshold is overreached, a container with the next sequence number is created.

Check container size threshold period (secs)

CONT_SIZE_CHECK_SECS

1440

Minimum 0

Maximum 2147483647

Parameter CONT_SIZE_THRESHOLD_KB defines the max size of the container. Due to performance reasons, it's not a good idea to check the size of the container each time when a new file is created. Using this parameter, you can set the period of how often the size of this container should be checked.

Delete empty container

DELETE_EMPTY_CONTAINER

X

Enumeration

<empty> - disabled

X - enabled

Container for source ID is created during the first attempt of data insertion to it and eventually, it will be deleted by deletion of last of its file. For some storage, there can be the issue to re-create containers with the same name and therefore this option was added. You can switch off the deletion of a container by this setting. The container will not be deleted and if there is another attempt to insert data into the source container doesn’t need to be re-created again because it is already available.

Number of allowed lock attempts

LOCK_WAIT_ATTEMPTS

10

Minimum 1

Maximum 2147483647

When a new file is being created, we need to check to which container it should be written. This information is stored in the table /DVD/CRP_SMC_LUC. To make sure this table will not be updated with another concurrent execution, we need to lock access to this table. This parameter restricts how many times the program can try to get this log.

If several attempts are overreached, an exception is raised with the following error message:

Creation of package is locked for storage ID '<Storage ID>'

Auto AUTO_CONT_SIZE_CHECK_<Source ID>

AUTO_CONT_SIZE_CHECK<Source ID>

0

Timestamp value in the format

YYYYMMDDhhmmss

Parameter CONT_SIZE_CHECK_SECS is limiting how often the size of the container will be checked, this dynamical parameter holds the last timestamp when container size was checked.

Virtualization of indexes enabled

VIRTUAL_INDEX_ENABLED

Enumeration

<empty> - disabled

X - enabled

Parameter disables/enables virtual index functionality in general.

Infostructure access mode

INFOSTRUC_ACC_MODE

T

Enumeration

T - use Infostructure management table

A - enable for all infostructures

The parameter specifies for which infostructures virtual indexes can be used. Either you use the table with a list of info structures to enable or disable a particular infostructure or you can allow it for all infostructures. We recommend using the method with the table as you know the exact list for which info structures is a virtual index used. You can edit the table by using transaction /DVD/CRP_AIND_IE

Transparentization runs

TRANSPARENT_RUNS

List of Run ids in CSV format

<empty> - search in all runids

<runid1>;<runid2>; …;<runidN>

To identify which storage and which table for which archiving object should be read, you can define allowed transparentization runids that will be used to get this metadata information. Runids need to be added in CSV format. Possible runid can be found in transaction /DVD/SARA using F4 help.

Transp. job delay

JOB_DELAY

20

Minimum 0

Maximum 2147483647

Transparentization execution job /DVD/CRP_TSP_EXECUTE is scheduled after the successful registration of components in the repository. To be able to identify archiving sessions for a given Document ID we need to delay the registration job at least to the moment when the Document ID is updated in the ADMI_FILES table.

Enable auto transparentization

ENABLE_AUTO_TRANSP

Enumeration

<empty> - disabled

X - enabled

Parameter disables/enables automatic transparentization functionality in general.