Skip to main content
Version: 4.48.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.

Features​

  • Exporting content structure
  • Exporting versions
  • Exporting categories
  • Exporting binaries
  • Exporting principals

Currently not supported:

  • Other custom metadata than categories
  • Relationships
  • ACLs

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

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.