Skip to main content
Version: Latest (4.58.2)

OpenText CS DB source connector

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

note

LiveLink was renamed to Content Server when it was acquired in 2012 by OpenText.

note

To use this connector with an Oracle database, you will need to install some additional Oracle drivers. Please refer to the DB Query Component documentation for more information.

Supported Features​

  • Exporting content structure
  • Exporting versions
  • Exporting categories
  • Exporting binaries
  • Exporting permissions (ACLs)
  • Exporting principals
  • Exporting record details (record management, N/A in LiveLink)
  • Exporting classifications (N/A in LiveLink)
  • Exporting audit logs
  • Exporting holds (N/A in LiveLink)
  • Relationships (linked objects, N/A in LiveLink)
  • Other custom metadata than categories and record details

Features Currently Not Supported​

  • Renditions
  • Access control lists
  • Workflows

Settings​

mongoConnection​

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

OTCSDBConnectionString​

The connection string to the OpenText CS or LiveLink database.

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

OTCSDBConnectionOptions​

The connection options to connect to the OpenText CS or LiveLink database. Only required for MSSQL databases.

Example:

{
  "options": {
    "trustServerCertificate": true,
    "tdsVersion": "7_1",
    "encrypt": false,
    "packetSize": 16368
  }
}

OTCSDBEngine​

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

OTCSDBOwner​

The owner of the OpenText CS or LiveLink 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 or LiveLink 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"
  }
}

Specifies if the source system is an older version of LiveLink. In this case, the database tables are a little bit different and some of the OpenText CS features are not present. Can either be true or false.

pageSize​

Specifies the page size number that is used when paginating.

Example: 250

retrieveACLs​

Enables extracting the permissions of nodes (groups and users). Can either be true or false.

retrieveAuditLogs​

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

retrieveHolds​

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

note

Not available when isLiveLink is set to true.

retrieveRecordManagement​

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

note

Not available when isLiveLink is set to true.

retrieveRelations​

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

note

Not available when isLiveLink is set to true.

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.