Configuration Reference
Connectors are the conduit between Fusion and your external data sources. Connectors retrieve your data and import it into Fusion.
Installation instructions:
Fusion includes all available connectors in Indexing > Datasources. Some connectors come pre-installed, but you must install others manually. See the following resources for your version of Fusion:
Check the connector reference page linked in the table for Fusion compatibility information. |
Database connectors |
||||
Name |
Description |
Source Compatibility |
Platform Version |
Security Trimming |
The Couchbase V2 connector uses the Couchbase Java client to retrieve data stored in Couchbase. |
Couchbase Server 6.0.3 Enterprise Edition (V2) |
V2 |
No |
|
The Couchbase V1 connector uses the Cross-Datacenter Replication (XDCR) feature of Couchbase to retrieve data stored in Couchbase continuously in real-time. |
Couchbase Server 2.5.1 Enterprise Edition (V1) - Due to a dependency issue, the Couchbase V1 connector does not work as expected in Fusion 4.2.x. |
V1 |
No |
|
The JDBC connector fetches documents from a relational database via SQL queries. Under the hood, this connector implements the Solr DataImportHandler (DIH) plugin. |
Any JDBC compliant Database |
V1 |
No |
|
The JDBC connector fetches documents from a relational database via SQL queries. Under the hood, this connector implements the Solr DataImportHandler (DIH) plugin. |
Any JDBC V2 compliant Database |
V2 |
No |
|
Retrieve data from a MongoDB instance. |
MongoDB 2.6, 3.0, 3.2, 3.4, 3.6, 4.0 |
V1 |
No |
Filesystem connectors |
||||
Name |
Description |
Source Compatibility |
Platform Version |
Security Trimming |
The Box connector retrieves data from a Box.com cloud-based data repository. To fetch content from multiple Box users, you must create a Box app that uses OAuth 2.0 with JWT server authentication. For limited testing using a single user account, you can create a Box app that uses Standard OAuth 2.0 authentication. |
N/A |
V1 |
Yes |
|
The Box connector retrieves data from a Box.com cloud-based data repository. To fetch content from multiple Box users, you must create a Box app that uses OAuth 2.0 with JWT server authentication. For limited testing using a single user account, you can create a Box app that uses Standard OAuth 2.0 authentication. |
N/A |
V2 |
Yes |
|
The File Upload connector provides a convenient way to quickly ingest data from your local filesystem. |
N/A |
V1 |
No |
|
The File Upload V2 connector provides a convenient way to quickly ingest data from your local filesystem. |
N/A |
V2 |
No |
|
Retrieve documents using the File Transfer Protocol (FTP). |
N/A |
V1 |
No |
|
The Fusion Google Cloud Storage (GCS) V2 connector enables indexing datasets from GCS buckets into Fusion 5. The connector leverages the Google Cloud API for authentication and fetching content and metadata. |
All |
V2 |
Yes |
|
The Google Drive connector is used to index the documents in a Google Drive account. |
Google V3 API |
V1 |
Yes |
|
Hadoop Distributed File System (HDFS). It traverses the Hadoop file system as it would a regular Unix filesystem. |
2.7.1 |
V1 |
No |
|
This connector traverses a network file system (NFS), where a shared drive is mounted to the same location on all hosts in the cluster that are running this connector. |
All |
V2 |
No |
|
This connector traverses a network file system (NFS), where a shared drive is mounted to the same location on all hosts in the cluster that are running this connector. |
All |
V1 |
No |
|
OneDrive is a file hosting service that is part of the Microsoft Office Online services. The Fusion OneDrive connector crawls a OneDrive for Business instance and retrieves data from it for indexing within Fusion. |
All |
V2 |
Yes |
|
The AWS S3 V1 Connector can access AWS S3 buckets in native format. |
All |
V1 |
No |
|
The AWS S3 V2 connector crawls items in a single bucket. You must specify the bucket name and AWS region in which that bucket is located. You may crawl specific items in a bucket. If no items are specified, the entire bucket will be crawled. |
All |
V2 |
No |
|
The SolrXML connector indexes XML files formatted according to Solr’s XML structure. It is not a generic XML file crawler; it can only index SolrXML-formatted documents. |
All |
V1 |
No |
|
Windows Share (deprecated) |
The Windows Share connector can access content in a Windows Share or Server Message Block (SMB)/Common Internet File System (CIFS) filesystem. |
SMB 1 protocol |
V1 |
Yes |
The Windows Share connector can access content in a Windows Share or Server Message Block (SMB 2 and 3 protocols)/Common Internet File System (CIFS) filesystem. Available in Fusion 5.x.x releases. |
SMB 2, 3 protocols |
V1 |
Yes |
|
The Windows Share connector can access content in a Windows Share or Server Message Block (SMB 2 and 3 protocols)/Common Internet File System (CIFS) filesystem. |
SMB 2, 3 protocols |
V2 |
Yes |
Hadoop cluster connectors |
||||
Name |
Description |
Source Compatibility |
Platform Version |
Security Trimming |
The Apache Hadoop 2 Connector is a MapReduce-enabled crawler that is compatible with Apache Hadoop v2.x. |
2.x |
V1 |
No |
|
The Hortonworks Connector is a MapReduce-enabled crawler that is compatible with Hortonworks Data Platform v2.x. |
2.x |
V1 |
No |
|
The MapR Connector is a MapReduce-enabled crawler that is compatible with MapR 4.x and 5.x. |
4.x, 5.x |
V1 |
No |
|
The Cloudera Connector is a MapReduce-enabled crawler that is compatible with Cloudera CDH v4.x and v5.x. |
4.x, 5.x |
V1 |
No |
Push content connectors |
||||
Name |
Description |
Source Compatibility |
Platform Version |
Security Trimming |
The Solr Push Endpoint accepts documents and pushes them to Solr using the Fusion index pipelines. You might use this, for example, if you are indexing Solr XML documents from a content management system that natively integrates with Solr, for example using SolrJ. |
All |
V1 |
No |
Repository connectors |
||||
Name |
Description |
Source Compatibility |
Platform Version |
Security Trimming |
The Active Directory Connector for ACLs V2 plugin:
|
N/A |
V2 |
Yes |
|
The Active Directory Connector for ACLs indexes Access Control List (ACL) information into a configured "sidecar" Solr collection, so that it can be used by other connectors. |
N/A |
V1 |
Yes |
|
This connector retrieves data from an Adobe Experience Manager (AEM) repository. The AEM V2 connector is compatible with AEM version 6.5. |
AEM 6.5 |
V2 |
Yes |
|
The Alfresco Connector is a crawler for the Alfresco server, which adheres to the Content Management Interoperability Services (CMIS) standard. |
CMIS 1.1 compliant versions |
V1 |
Yes |
|
The Azure connector is used to crawl an Azure instance. Its connector type is "lucid.azure" and its plugin type is "azure". |
Blob and Table storage |
V1 |
No |
|
Retrieve data from the Atlassian Confluence Wiki CMS. You can configure this datasource to crawl pages, spaces, blog posts, comments, and attachments. |
Confluence Server 5.5 and later; Confluence Cloud |
V1 |
Yes |
|
The Drupal connector requires Drupal’s Services 7.x3.11 Module REST API. Refer to this page to install the necessary packages: www.drupal.org/node/783236 |
Drupal 7.x |
V1 |
No |
|
The GitHub connector retrieves data from GitHub repositories using the GitHub REST API. |
N/A |
V1 |
No |
|
The JIRA connector retrieves data from an instance of Atlassian’s JIRA issue tracking system. |
6.x, 7.x |
V1 |
Yes |
|
The Active Directory Connector for ACLs indexes Access Control List (ACL) information so that it can be used by other connectors. |
N/A |
V2 |
Yes (Graph Security Trimming) |
|
Use the Salesforce REST API to extract data from a Salesforce repository via a Salesforce Connected App. |
N/A |
V1 |
Yes |
|
The ServiceNow Datasource retrieves data from the ServiceNow repository. |
N/A |
V1 |
Yes |
|
The SharePoint Optimized V2 connector retrieves content and metadata from an on-premises SharePoint repository and cloud-based SharePoint repositories. |
2013, 2016, 2019, Online |
Yes (Graph Security Trimming) |
||
The SharePoint connector retrieves content and metadata from an on-premises SharePoint repository. |
2013, 2016, 2019, Online |
Yes |
||
The SharePoint connector retrieves content and metadata from an on-premises SharePoint repository. |
2010, 2013, 2016, Online |
Yes |
||
The SharePoint Online V1 Optimized connector retrieves data from cloud-based SharePoint repositories. Authentication requires a Sharepoint user who has permissions to access Sharepoint via the SOAP API. This user must be registered with the Sharepoint Online authentication server; it is not necessarily the same as the user in Active Directory or LDAP. |
N/A |
Yes |
||
SharePoint V1 (deprecated as of 5.2) |
The SharePoint connector retrieves content and metadata from an on-premises SharePoint repository. |
2010, 2013, 2016, Online |
Yes |
|
SharePoint Online V1 (deprecated as of 5.2) |
The SharePoint Online V1 connector retrieves data from cloud-based SharePoint repositories. Authentication requires a Sharepoint user who has permissions to access Sharepoint via the SOAP API. This user must be registered with the Sharepoint Online authentication server; it is not necessarily the same as the user in Active Directory or LDAP. |
N/A |
Yes |
|
This connector provides full crawl and incremental crawl support for Sitecore versions 8.x and 9.x. It indexes document content and all metadata. |
8.x, 9.x |
V2 |
No |
|
The Slack V2 connector allows you to index Slack channels and messages. |
N/A |
V2 |
Yes |
|
A Solr connector pulls documents from an external standalone Solr instance or SolrCloud cluster using Solr’s javabin response type and streaming response parser. |
All |
V1 |
No |
|
Subversion (deprecated) |
This connector requires a Subversion client that is compatible with JavaHL. |
1.8 and below |
V1 |
No |
The Zendesk connector uses the Zendesk REST API to retrieve tickets and their associated comments and attachments from a Zendesk repository. |
N/A |
V1 |
Yes |
Script connectors |
||||
Name |
Description |
Source Compatibility |
Platform Version |
Security Trimming |
The Javascript connector allows users to write ad-hoc document retrieval routines to fetch content from filesystems and websites. |
All |
V1 |
No |
Social media connectors |
||||
Name |
Description |
Source Compatibility |
Platform Version |
Security Trimming |
Retrieve content from a Jive instance. |
REST API +V3.12 |
V1 |
Yes |
|
The Kaltura V2 connector uses the Kaltura Java API client to retrieve data stored in Kaltura. |
All |
V2 |
Yes |
|
The Twitter Search connector uses Twitter’s search API to query Twitter for tweets that match specific parameters. It allows querying for any keyword, location or other query terms. |
All |
V1 |
No |
|
The Twitter Stream connector uses Twitter’s streaming API to continually index Twitter. The datasource can be configured to limit tweets or it can be run indefinitely, until Twitter cuts off your access or you stop the datasource. This connector only retrieves tweets created after the datasource has been started. |
All |
V1 |
No |
Web connectors |
||||
Name |
Description |
Source Compatibility |
Platform Version |
Security Trimming |
The Web V1 connector retrieves data from a Web site using HTTP and starting from a specified URL. |
All Fusion 4.x and 5.x releases |
V1 |
No |
|
The Web V2 connector retrieves data from a Web site using HTTP and starting from a specified URL. |
Fusion release 5.6.1 and later |
V2 |
No |