Parameter | Value | Description |
---|---|---|
ArchPath | Path for Filesystemindex for storing Center Clip-IDs (one Clip-ID for each SAP-document) | |
CenteraPoolAddress | List of Centera-IP-Addresses | 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 |
CompClip-DescA_n-xx-yyyy | 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) |
DocClip-DescA_n-xx | Syntax: AttributeName,AttributValue Attribute names with special functionality (see EMC SDK) | n= counter starting with 1 xx=SAP Repository ID |
EmbeddedDataThreshold | Integer | 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 |
Page Comparison
General
Content
Integrations