Page Comparison

0 = output standardout - off

1 = output standardout - on

Available filing modes

0 = Native filesystem

1 = Centera

2 = NetApp

3 = Native filesystem with Database

4 = Centera with Database

5 = ICAS

6 = ICAS Filesystem

7 = ORACLE UCM

8 = SharePoint

9 = DELL DX

10 = DELL DX with Database

For more detailed information please see Section

0 = [StorageFS]

1 = [EMC Center]

2 = [NetApp]

3 = [StorageFSDB]

4 = [EMC Centera DB]

5 = [ICAS]

6 = [ICASFS]

7 = [OracleUCM]

8 = [SHAREPOINT]

9 = [DELL]

10 = [DELLDB]

1 = log errors

2 = log warnings

4 = log debug information.

8 = log performance information

Defines which kind of information shall be loged.

A combination of these values is possible.

Examples:

Errors + Warnings → Log-Mode = 3

Errors + Warnings + Performance information → Log-Mode = 11

true / false

Permitting offset/length access to Component

Recommendation > true

Permit deleting components

0 = disabled

1 = Create missing doc.info-files

Defines the path, where documents will be stored.

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

Example: ArchPath_H8 = /opt/storage

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

Example:  ArchPath#1_T1 = /opt/storage

                ArchPath#2_T1 = /home/temp/storage_T1

Defines the minimal amount of space in megabyte that should be kept free.

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

Example: FreeDiscSpaceArchPath_H8 = 1024

Multiple space configurations are possible by adding a "#<number>" between FreeDiscSpaceArchPath and potential trailing repository specifications.

Example:  FreeDiscSpaceArchPath#1_T1 = 1024

                FreeDiscSpaceArchPath#2_T2 = 512

List of ContentRepository name/-s, separated by comma

Defines a list of one or many ContentRepositories which shall be handled as read only.

If set to true, all write requests will be rejected.

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.

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

Example: RetentionPeriod_MX=36|application /x-alf=1000|application/x- reo=5|image/tiff=6

Repository ID in document filing structure on/off

Recommendation TRUE

Defines the hashing algorithm used for the hashkey.

Empfy means that the hashmode is off.

This parameter can be set per ContentRepository.

Example:

HashAlg = HashAlg_T1 = MD5

Enables or disables the hashkey check during document checkout (get).

This parameter can be set per ContentRepository.

Example:

HashCheck = false

HashCheck_T1 = true

0 = No data encoding

1 = KGS encoding

This parameter can be set per ContentRepository.

Example:

DataEncoding = 0

DataEncoding_T1 = 1

Defines the path for storing dulicates of the data (mirroring).

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

Example: DuplicatePath_H8 = /opt/storage

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

Example:  DuplicatePath#1_T1 = /opt/storage

                DuplicatePath#2_T1 = /home/temp/storage_T1

Defines the minimal amount of space in megabyte that should be kept free.

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

Example: FreeDiscSpaceDuplicatePath_H8 = 1024

Multiple space configurations are possible by adding a "#<number>" between FreeDiscSpaceArchPath and potential trailing repository specifications.

Example:  FreeDiscSpaceDuplicatePath#1_T1 = 1024

                FreeDiscSpaceDuplicatePath#2_T2 = 512

Defines a limitation for the maximal length of the filename.

When this limit is exceeded the part of the ComponentID in the filenmae is being replaced by a fingerprint of the ComponentID and the original ComponentID is being stored in the info-file.

Use this parameter only if your file system has a limitation that does not fit to the documents you want to archive.

Default: 0 = no limitation

The pool addresses can be a comma-separated string of IP-addresses or DNS names ov available Centera-nodes.

Hiermit sind vermutlich ausschließlich IPv4-Adressen gemeint oder? Falls ja sollte man das auch so erwähnen.

This example specifies a connection string with multiple IP-addresses which is a best practice that protects against the unavailability of one or more nodes within the cluster.

10.1.1.1,21.17.3.12,16.123.121.90

This example opens a pool using the specified PEA-file.

10.62.153?C:\EMC\RWE.pea

(Please confirm Centera documentation for details)

You can define one pool address per Repository ID by using Key "CenteraPollAddress_xx" (xx = Repository-ID) finde ich widersprüchlich.

Ist das jetzt so gemeint: 10.1.1.1_H8 oder CenteraPoolAddress_H8 = 10.1.1.1

The maximum data size in bytes for data to be embedded in the CDF instead of being stored as separate blobs.

Default: 102400

Max. value: 102400

Syntax: AttributeName,AttributValue

Attribute namens with special functionality (see EMC SDK): RetentionPeriod -> in Month (will be converted to seconds for EMC Centera) must be set with this parameter. e.g. CompClip-DescA_1-O1 = RetentionPeriod,10

n= counter starting with 1 xx=SAP Repository ID yyyy= SAP Component-ID

(If yyyy isn't specified, the attributes are valid for all Components)

Syntax: AttributeName,AttributValue

Attribute names with special functionality (see EMC SDK)

Connection URL for database.

This parameter is optional.

Sample for Oracle:

jdbc:oracle:thin:@169.254.25.100:1521:KGSSTORE

JDBC driver name.

(If DB-URL is not being set.)

IP address / DNS name of the database server.

(If DB-URL is not being set.)

Port database listener.

(If DB-URL is not being set.)

Database system ID.

(If DB-URL is not being set.)

Password of the database user.

The password will be encrypted after the first start.

The pool addresses can be a comma-separated string of IP-addresses or DNS names ov available Centera-nodes.

Hiermit sind vermutlich ausschließlich IPv4-Adressen gemeint oder? Falls ja sollte man das auch so erwähnen.

This example specifies a connection string with multiple IP-addresses which is a best practice that protects against the unavailability of one or more nodes within the cluster.

10.1.1.1,21.17.3.12,16.123.121.90

This example opens a pool using the specified PEA-file.

10.62.153?C:\EMC\RWE.pea

(Please confirm Centera documentation for details)

You can define one pool address per Repository ID by using Key "CenteraPollAddress_xx" (xx = Repository-ID) finde ich widersprüchlich.

Ist das jetzt so gemeint: 10.1.1.1_H8 oder CenteraPoolAddress_H8 = 10.1.1.1

The maximum data size in bytes for data to be embedded in the CDF instead of being stored as separate blobs.

Default: 102400

Max. value: 102400

Syntax: AttributeName,AttributValue

Attribute namens with special functionality (see EMC SDK): RetentionPeriod -> in Month (will be converted to seconds for EMC Centera) must be set with this parameter. e.g. CompClip-DescA_1-O1 = RetentionPeriod,10

n= counter starting with 1 xx=SAP Repository ID yyyy= SAP Component-ID

(If yyyy isn't specified, the attributes are valid for all Components)

Defines a list of Repositories for which KGS Store may automatically created tables on the database.

Example: Repositories = T1,FB,H8,C2

List of comma-separated ContentRepository/-ies that should be handled as read only.

If set to true, all write requests will be rejected.

List of comma-separated ContentReposity/-ies that should be handled as read only.

If set to true, all write requests will be rejected.

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.

Default: false

Repository ID in document filing structure on/off

Recommendation TRUE

Default: true

Defines the path, where documents will be stored.

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

Example: ArchPath_H8 = /opt/storage

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

Example:  ArchPath#1_T1 = /opt/storage

                ArchPath#2_T1 = /home/temp/storage_T1

Defines the minimal amount of space in megabyte that should be kept free.

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

Example: FreeDiscSpaceArchPath_H8 = 1024

Multiple space configurations are possible by adding a "#<number>" between FreeDiscSpaceArchPath and potential trailing repository specifications.

Example:  FreeDiscSpaceArchPath#1_T1 = 1024

                FreeDiscSpaceArchPath#2_T2 = 512

If set to true, component file and corresponding info file will be set read only on the filer. A delete date will be calculated and added to the properties file of the component. (Locking is done by a combination of the OS commands “touch –a –t” and “chmod 440”)

Default: false