Versions Compared

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

The SharePoint request to tia Connect contains meta properties that are stored in the tia Content Server CMIS. Attributes can hav

When no metadata-mapping or type-mapping applies to an attribute name, it is stored in the CMIS type that is set by customType parameter, and the attribute name is prefixed by the string in customPrefix parameter.

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.
Examples

...

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.

This setting defines, that whenever the property sapbo:basedocument:Document is filled, the type sapbo:basedocument must also be added. In combination with the above metadata-mappings, this means whenever the property othervalue is filled in an incoming metadata request, either on create or on patch, the type will be added.

...