Configuration (Store) - STORAGEFSDB (3)

Defines the path, where documents will be stored.

Can be specified per ContentRepository by adding a trailing "_<ContentRepository>"

Example: ArchPath_T1 = /opt/storage/T1

Multiple path configurations are possible by adding a "#<number>" between ArchPath and potential trailing repository specification.

Example:

ArchPath#1_T1 = /opt/storage1/T1

ArchPath#2_T1 = /opt/storage2/T1

0 = Containermode disabled

Can be specified per ContentRepository by adding “_<ContRep>”.

Example: ContainerMaxFiles_T1=500

Maximum time in seconds after a container will be closed when no new archiving request arrives.

Repository ID in document filing structure

Move files instead of copying to ArchPath.

If this option is being enabled it increases the performance if the working directory of the ContentServer and the defined ArchPath are on the same hard disk.

If file delete is not enabled, the dataset in the database will be deleted by a delete request, but the corresponding component file remains in the filesystem.

Datafilenames with fileextention (depending on MIMEType)

Defines the amount of time (in months) from date of filing until which deletion should be prevented.. Retention periods can be set per ContRep and per document mime time.

Example:

RetentionPeriod_T1=36|application /x-alf=1000|application/x- reo=5|image/tiff=6

For more information: STORAGEFSDB - Additional Information

Defines the maximal possible number of entries per Node.

<yyyyMMdd> = Dateprefix in folderstructure.

Example:\ArchPath\T1\20110825\0000\0000\document.pdf

Connection URL for the database.

Sample for Oracle: jdbc:oracle:thin:@169.254.25.100:1521:KGSSTORE

Database user password

The password will be encrypted after the first start.

Prefix for database tables.

True = document reference in database is relative to parameter ArchPath.

Otherwise, the full path to the document will be stored.

List of comma-separated Repository-ID’s.

Repositories for which database tables may be created automatically.

Sample: FI, T1

List of comma-separated RepositoryID’s.

For this repository the key CSREPID will be ignored for database accesses, so the DocumentID will be the unique key to the document.

Repository ID’s to change, comma-separated. This parameter works only in combination with parameter IgnoreContRepID.

If a document is archived with one of these ID’s, the first access to this document with a different ContentRepID will over-write the repository information in the document info file.