📄️ Alfresco source connector
The Alfresco connector consists of two flows which are described below.
📄️ Box.com source connector
The Box.com connector uses the Box.com API. It consists of multiple flows, which are described below.
📄️ Documentum source connector
The Documentum REST API is supported by Documentum 7 and higher.
📄️ File source connector
The file connector allows the scraping of a file system. It will return the most basic file system meta data for folders and files.
📄️ FileNet Hybrid source connector
The FileNet Hybrid connector uses a FileNet proxy to connect to the FileNet web services, as well as a direct connection to the database. Currently, only Db2 is supported. However with relatively little effort, other databases can be supported as well. This hybrid approach is used to gain the best balance between performance and functionality.
📄️ LiveLink DB source connector
The LiveLink database connector supports LiveLink running on a MS SQL Database. Note that in 2012 OpenText acquired LiveLink and renamed it to Content Server. This connector is not compatible with the OpenText Content Server REST API. For that connector see OpenText CS source connector.
📄️ OpenText CS source connector
The OpenText CS REST API is supported by all OpenText Content Server versions.
📄️ 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.
📄️ OpenText eDOCS DB source connector
The OpenText eDOCS database connector uses a direct connection to the database. This connector has only been tested with eDOCS version 16.3 and currently only MSSQL and Oracle databases are supported.
📄️ SharePoint On-Premise (2013, 2016, 2019) source connector
The SharePoint On-Premise source connector enables you to export content from a SharePoint On-Premise environment. The connector uses the SharePoint REST API to export the content.
📄️ SharePoint Online source connector
The SharePoint Online source connector consists of multiple flows, which are described below. These flows use the MS Graph API v1 and the SharePoint Online REST API.