Configuration (Store) - EMC CENTERA (1)
[COMMON SETTINGS]
In order to use EMC CENTERA without a database, please set in [COMMON SETTINGS] section the parameter StorageType = 1.
[EMC CENTERA]
Parameter | Value | Description | Defaults |
|---|---|---|---|
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 of available Centera-nodes. 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 "CenteraPoolAddress_xx" (xx = Repository-ID). | |
CompClip-DescA_n-xx-yyyy | Syntax: AttributeName,AttributValue | 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) 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 | |
DocClip-DescA_n-xx | Syntax: AttributeName,AttributValue Attribute names with special functionality (see EMC SDK) | Optional 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. Max. value: 102400 | 102400 |
Additional Information
For each SAP document one Centera file (CLIP) will be created with all administration data required by the document container.
Every "document clip" contains all references to the "component Clip's".
None of the Clips may have a tag with a BLOB (datafile). All ClipIDs of corresponding components may be stored in the attributes tags.
CLIP-Name = SAP-ArchiveLink-Document.
CFG File
Clip | SAP-ArchiveLink Document | ||
|---|---|---|---|
Attribute-Name | Attribute-Value | Mandatory | Description |
app-vendor | KGS Software GmbH | ||
app-name | SAP LINK EMC Centera | ||
app-version | 01.00 | ||
app-profileversion | 01.00 | X | |
Prop-type | Document | X | |
Prop-archivid | X | SAP ContentrepositoryID | |
Prop-docid | X | SAP DocumentID | |
Prop-alversion | X | ArchiveLink-Version 0031 / 0045 | |
Prop-protection | SAP Protection Flag | ||
Prop-createtime | X | SAP creating time | |
Prop-createdate | X | SAP creating date | |
Prop-changetime | X | SAP modification time | |
Prop-changedate | X | SAP modification date | |
Prop-barcode | SAP barcode (for future usage) | ||
Tag | CompclipID | ||
CompID | X | SAP Comp-ID | |
cid | X | CLIP ID Component |
CFG-Sample
<?xml version='1.0' encoding='UTF-8' standalone='no'?>
<ecml version="3.0">
<eclipdescription>
<meta name="type" value="Standard"/>
<meta name="name" value="SAPAL Document"/>
<meta name="creation.date" value="2005.03.23 12:38:10 GMT"/>
<meta name="modification.date" value="2005.03.23 12:39:00 GMT"/>
<meta name="creation.profile" value="anonymous"/>
<meta name="modification.profile" value="anonymous"/>
<meta name="numfiles" value="0"/>
<meta name="totalsize" value="0"/>
<meta name="refid" value="8B56JFU7VKDF1390BPB0S94CKL"/>
<meta name="prev.clip" value=""/>
<meta name="clip.naming.scheme" value="MD5"/>
<meta name="numtags" value="1"/>
<meta name="retention.period" value="0"/>
<custom-meta name="app-vendor" value="EMC (Powered by KGS)"/>
<custom-meta name="app-name" value="SAPALINK Centera"/>
<custom-meta name="app-version" value="01.00"/>
<custom-meta name="app-profileversion" value="01.00"/>
<custom-meta name="prop-type" value="document"/>
<custom-meta name="prop-archivid" value="T1"/>
<custom-meta name="prop-docid" value="27F31DBF78F34D4BB50C2816133EB434"/>
<custom-meta name="prop-alversion" value="0045"/>
<custom-meta name="prop-protection" value="rucd"/>
<custom-meta name="prop-createtime" value="133810"/>
<custom-meta name="prop-createdate" value="20050323"/>
<custom-meta name="prop-changetime" value="133810"/>
<custom-meta name="prop-changedate" value="20050323"/>
<meta name="sdk.version" value="2.3.327"/>
</eclipdescription>
<eclipcontents>
<compclipid cid="8BK1G3RHK69QBe1ES6EAS9PRGGB" compid="data"/>
</eclipcontents>
</ecml>Content handling
The data files are saved as BLOG in the tag compdata.
If the filesize is less than the specified size in the parameter EmbeddedDataThreshold no separare BLOG will be used for storing the data.
Instead of an external BLOB file the document data will be embedded in the CDF file. This is being handled by Centera internally.
CDF File
Clip | SAP-ArchiveLink-Component | ||
|---|---|---|---|
Attribute-Name | Attribute-Value | Mandatory | Description |
app-vendor | KGS Software GmbH | ||
app-name | SAP Link EMC Centera | ||
app-version | 01.00 | ||
app-profileversion | 01.00 | X | |
prop-type | component | X | |
prop-archivid | X | SAP ContentrepositoryID | |
prop-docid | X | SAP DocumentID | |
prop-compid | X | SAP ComponentID | |
prop-alversion | X | ArchiveLink Version 0031 / 0045 | |
prop-createtime | X | SAP creation time | |
prop-createdate | X | SAP creation date | |
prop-changetime | X | SAP modification time | |
prop-changedate | X | SAP modification date | |
prop-appversion | SAP Application Version | ||
prop-comptype | SAP Mimetype | ||
prop-charset | SAP Characterset | ||
Tag | Name = Component data | ||
Filename | X | SAP Filename |
CDF-Sample
<?xml version='1.0' encoding='UTF-8' standalone='no'?>
<ecml version="3.0">
<eclipdescription>
<meta name="type" value="Standard"/>
<meta name="name" value="SAPAL Component"/>
<meta name="creation.date" value="2005.03.23 12:38:10 GMT"/>
<meta name="modification.date" value="2005.03.23 12:38:10 GMT"/>
<meta name="creation.profile" value="anonymous"/>
<meta name="modification.profile" value="anonymous"/>
<meta name="numfiles" value="1"/>
<meta name="totalsize" value="7716"/>
<meta name="refid" value="7CSR4L4SJ97N6D9GJV26UE3EN0"/>
<meta name="prev.clip" value=""/>
<meta name="clip.naming.scheme" value="MD5"/>
<meta name="numtags" value="1"/>
<custom-meta name="app-vendor" value="EMC (Powered by KGS)"/>
<custom-meta name="app-name" value="SAPALINK Centera"/>
<custom-meta name="app-version" value="01.00"/>
<custom-meta name="app-profileversion" value="01.00"/>
<custom-meta name="prop-type" value="component"/>
<custom-meta name="prop-archivid" value="T1"/>
<custom-meta name="prop-docid" value="27F31DBF78F34D4BB50C2816133EB434"/>
<custom-meta name="prop-compid" value="data"/>
<custom-meta name="prop-alversion" value="0045"/>
<custom-meta name="prop-createtime" value="133810"/>
<custom-meta name="prop-createdate" value="20050323"/>
<custom-meta name="prop-changetime" value="133810"/>
<custom-meta name="prop-changedate" value="20050323"/>
<custom-meta name="prop-appversion" value="Application V1.00"/>
<custom-meta name="prop-comptype" value="image/tiff"/>
<custom-meta name="prop-charset" value="Charset001"/>
<meta name="sdk.version" value="2.3.327"/>
</eclipdescription>
<eclipcontents>
<compdata filename="C:\Dokumente und Einstellungen\Grau\Eigene Dateien\S0000001.TIF">
<eclipblob md5="2SKF8I7TV30MJx55EI6UT27E7D0" size="7716" offset="0"/>
</compdata>
</eclipcontents>
</ecml>Addon functionality: Requesting a Centera ClipID for a given Document
The KGS ConentServer provides an additional http-command in order to request a Centera ClipID of an ArchiveLink document.
The http-URL has the following syntax: http://<ipaddress:port>/prgname?docPropertyGet&docid=<DocumentID>&propId=<PropertyID>
→ Configuration (Store) - NetApp (2) | Configuration (Store) - StorageTypes - ArchiveLink