Versions Compared

Version Old Version 1 New Version Current
Changes made by

Armin Franke

Armin Franke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

At least one encryption key definition must be configured, see https://kgs-software.atlassian.net/wiki/spaces/SUPPORTDOCUEN/pages/35582777233645637333/DRAFT+-+Sharepoint+specific+configuration#Encryption-key-definition-parameter .

...

The SharePoint request to tia Connect contains these attributes meta properties path, pathPrefix, siteId, and libraryId. By true|false switches, each of these attribute can be included into the storage path. The sequence, however, is fixed.

For example:

  • When all attributes meta properties are included: archiveFolder/siteId/libraryId/pathPrefix/path

  • When only libraryId and path are included: archiveFolder/libraryId/path

Parent

Parameter

Description of request attribute

Required

Supported values

Default

tia.instances.<name>.sharepoint

archiveFolder

CMIS folder in which the data is to be archived

Example: /cmis/instance1

no

<path on tia Content Server>

/

tia.instances.<name>.sharepoint.includeInPath

path

The strange, anywhere configured, SharePoint path

no

true | false

true

tia.instances.<name>.sharepoint.includeInPath

pathPrefix

A prefix for the archive path

no

true | false

true

tia.instances.<name>.sharepoint.includeInPath

siteId

Sharepoint Site ID

no

true | false

true

tia.instances.<name>.sharepoint.includeInPath

libraryId

Sharepoint Library ID

no

true | false

false

...

Parent

Parameter

Description

Required

Supported values

Default

tia.instances.<name>.sharepoint.encryptionkeydefinitions[<n>]

id

Identifier for the definition

yes

<string>

-

tia.instances.<name>.sharepoint.encryptionkeydefinitions[<n>]

encryptionAlgorithm

The encryption algorithm

no

<encryption algorithm>

AES/CBC/PKCS5Padding

tia.instances.<name>.sharepoint.encryptionkeydefinitions[<n>]

encryptionKey

The password for encryption and decryption

yes

<user>

-

tia.instances.<name>.sharepoint.encryptionkeydefinitions[<n>]

secretKeyFactoryAlgorithm

The secret-key algorithm

no

<secret-key algorithm>

PBKDF2WithHmacSHA256

tia.instances.<name>.sharepoint.encryptionkeydefinitions[<n>]

iterationCount

The iteration count

no

<numeric>

65536

tia.instances.<name>.sharepoint.encryptionkeydefinitions[<n>]

keyLength

The to-be-derived key length

no

<numeric>

256

Mapping Metadata

With the setting metadata-mappings an incoming property can be mapped to a different property on the cmis-side. The mapping also applies when fetching the properties, the cmis-side property is mapped to the original value. The definition of the cmis-side must specify the full cmis-id of the target property.
ExamplesThe SharePoint request to tia Connect contains meta properties that are stored in the tia Content Server CMIS as CMIS properties.

When no metadata mapping or type mapping applies to an meta property name, the CMIS property name is prefixed by the customPrefix parameter and stored as property of CMIS type specified by customType parameter. Only when the meta property name starts with cmis:, the prefix is not applied building the CMIS property name.

The metadata mapping allows direct mapping of a meta property name to a CMIS property name, and overrides the building process. However, for the metadata mapping, the CMIS property mapped must be known to the tia Content Server.

Example:

Code Block
metadata-mappings:
  customvalueabstract: 'cmis:description'
  othervaluecontent: 'sapbo:basedocument:Document'

The first mapping maps the incoming value customvalue to the cmis property cmis:description, which is a default property. The second mapping maps the incoming value othervalue to the cmis property sapbo:basedocument:Document. The latter will fail, because the cmis property is a non-standard property. To be used, the type mapping parameter must be added.After the CMIS properties are mapped, the type mappings allow map CMIS types: When there is a type mapping for a CMIS property to be added, then the CMIS type is also added.

Example:

Code Block
type-mappings:
  "[sapbo:basedocument:Document]": 'sapbo:basedocument'
Info

Use always “[ … ]” (double-quotes with square brackets) on the left-hand-side of an association in YAML file. One the right-hand-side '

...

(single quotes) are sufficient.

Background is, that : is a separation character and may otherwise split the CMIS type name leading to unexpected results.

Assuming both example mappings are active for the same instance, then if the meta property content is present in the request, it will be mapped to sapbo:basedocument:Document CMIS property because of the meta mapping. Then because of the type mapping the CMIS type sapbo:basedocument is also added.

Metadata mappings

Parent

Parameter

Description

Required

Supported values

Default

tia.instances.<name>.sharepoint

customType

CMIS custom type for sharepoint metadatanot mapped meta data

no

<string>

tia:archiveProperties

tia.instances.<name>.sharepoint

customPrefix

Prefix for extension of the sharepoint metadatafor not mapped meta data

no

<string>

tia:archiveProperty:

tia.instances.<name>.sharepoint

metadataIgnoreFields

List of meta fields from Sharepoint property names that should be ignored.

Info

Specify this parameter to append to the list in default column. The listed values cannot be unset.

no

<List of Strings>

[
SharedWithUsers,
SharedWithUsers@odata.type,
SharedWithUsers#Claims,
SharedWithUsers#Claims@odata.type
]

tia.instances.<name>.sharepoint

metadata-mappings

Mapping of custom meta property name to CMIS property name.

no

<Map of configurations>

-

tia.instances.<name>.sharepoint

type-mappings

Mapping of custom meta property name to CMIS property name.

no

<Map of configurations>

-

...