Skip to main content
Version: 4.48.0

OpenText CS source connector

The OpenText CS REST API is supported by all OpenText Content Server versions. Permissions are introduced in OpenText Content Server REST API v16.2 and higher. When exporting permissions (ACLs), make sure to use a version that meets the requirements.

Features​

  • Exporting content structure
  • Exporting versions
  • Exporting categories
  • Exporting binaries
  • Exporting permissions (ACLs)

Currently not supported:

  • Other custom metadata than categories
  • Relationships

Settings​

mongoConnection​

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

origin​

Specifies the origin of the document in the Content Store.

pageSize​

Specifies the page size number that is used when paginating.

Example: 100

enableDownloadFiles​

Enables downloading the binaries into the Content Store. Can either be true or false.

enableVersions​

Enables extracting the versions. Can either be true or false.

enableCategories​

Enables extracting the categories of nodes and their versions. Can either be true or false.

enableACLs​

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

openTextUrl​

The base URL to the OpenText Content Server and its APIs.

Example: http://otcs162.xillio.com/otcs/cs.exe

openTextUsername and openTextPassword​

The credentials of an OpenText CS user with at least read access to all the contents that need to be extracted. All the OpenText REST API requests will be done on behalf of this user.

rootIds​

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

Example: ["1448","1461"]

authTicketExpirationPeriod​

OpenText Content Server security settings configure the expiration period for issued authentication tickets, which, by default, is 30 minutes. Put this expiration period of your OT CS (as a number of minutes) to this value. The connector will then regularly refresh the ticket 3 minutes before its expiration. Setting this value to 3 minutes or lower will result in constantly refreshing the authentication ticket.

Example: 30