Skip to main content
Version: Latest (4.54.0)

OpenText CS DB source connector

The OpenText CS database connector uses a direct connection to the database. It supports all OpenText Content Server versions running on a MSSQL or Oracle database.

note

LiveLink was renamed to Content Server when it was acquired in 2012 by OpenText. With some adjustments this connector will also work on those older LiveLink versions. Please scroll down to the bottom for the adjustments that were identified.

Features​

  • Exporting content structure
  • Exporting versions
  • Exporting categories
  • Exporting binaries
  • Exporting principals
  • Exporting record details (record management)
  • Exporting classifications
  • Exporting audit logs
  • Exporting holds
  • Exporting relationships
  • Other custom metadata than categories and record details

Settings​

mongoConnection​

The Mongo connection string including the database name to connect to.

OTCSDBConnectionString​

The connection string to the OpenText CS database.

Example: mssql://USERNAME:PASSWORD@otcs.yourcompany.com:1433/otcs

OTCSDBEngine​

The engine of the OpenText CS database. Currently, only MSSQL and Oracle are supported.

OTCSDBOwner​

The owner of the OpenText CS database schema. Only required for Oracle databases. Example: DMS.

providerDataMapping​

Specifies the mapping of the provider data. The provider data of an object contains the reference to the file on the file system. As the provider data itself only contains a relative path, the absolute path is constructed by combining the provider data with an UNC path based on the storage provider name and sub provider name.

A list of logical providers can be obtained by running the following query on the OpenText CS database:

SELECT * FROM <OTCSDBOwner>.KINI WHERE inisection = 'Livelink.LogicalProviders'

Example of provider data:

A<1,?,'providerInfo'='0000\\003\\3193.dat','storageProviderName'='ExtShared','subProviderName'='Default'>

Example of provider data mapping:

{
  "ExtShared" : {
    "Default" : "\\\\otcs\\data01"
  }
}

pageSize​

Specifies the page size number that is used when paginating.

Example: 250

enableRecordManagement​

Enables extracting the record details on containers and records. Can either be true or false.

enableAuditLogs​

Enables extracting the audit logs on containers and records. Can either be true or false.

enableHolds​

Enables extracting the applied holds on containers and records. Can either be true or false.

enableRelations​

Enables extracting the cross references on containers and records. Can either be true or false.

rootIds​

A list of comma-separated rootIds. The id of the Enterprise workspace is typically 2000.

Example: [1448,1461]

origin​

Specifies the origin of the document in the Content Store.

There are some minor differences in the database schema for the older LiveLink versions. As a result, some adjustments will have to be made in the DB Query components to make this connector work with those older versions. The following adjustments were identified:

  • When LiveLink is running on older versions of MSSQL (on or before 2008), adjust the DB Query components connection options:
{
  "options": {
    "trustServerCertificate": true,
    "tdsVersion": "7_1",
    "encrypt": false,
    "packetSize": 16368
  }
}
  • Database table DTREECORE is named DTREE in LiveLink,
  • Paginating by using ROW_NUMBER() does not work. Instead paginate by using a unique identifier for the table, e.g. column DATAID,
  • Database table DTREE does not have columns DELETED and MODIFIEDBY.