Connectors Configuration Reference

Description

The Couchbase V2 connector uses the Couchbase Java client to retrieve data stored in Couchbase.

The JDBC connector fetches documents from a relational database via SQL queries. Under the hood, this connector implements the Solr DataImportHandler (DIH) plugin.

Retrieve data from a MongoDB instance.

Description

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.

The File Upload connector provides a convenient way to quickly ingest data from your local filesystem.

Retrieve documents using the File Transfer Protocol (FTP).

The Google Drive connector is used to index the documents in a Google Drive account.

Hadoop Distributed File System (HDFS). It traverses the Hadoop file system as it would a regular Unix filesystem.

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.

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.

The AWS S3 V1 Connector can access AWS S3 buckets in native format.

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.

Description

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.

Description

The Active Directory Connector for ACLs V2 plugin:

The Alfresco Connector is a crawler for the Alfresco server, which adheres to the Content Management Interoperability Services (CMIS) standard.

The Azure connector is used to crawl an Azure instance. Its connector type is "lucid.azure" and its plugin type is "azure".

Retrieve data from the Atlassian Confluence Wiki CMS. You can configure this datasource to crawl pages, spaces, blog posts, comments, and attachments.

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

The GitHub connector retrieves data from GitHub repositories using the GitHub REST API.

The JIRA connector retrieves data from an instance of Atlassian’s JIRA issue tracking system.

Use the Salesforce REST API to extract data from a Salesforce repository via a Salesforce Connected App.

The ServiceNow Datasource retrieves data from the ServiceNow repository.

The SharePoint connector retrieves content and metadata from an on-premises SharePoint repository.

The SharePoint connector retrieves content and metadata from an on-premises SharePoint repository.

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.

This connector provides full crawl and incremental crawl support for Sitecore versions 8.x and 9.x. It indexes document content and all metadata.

A Solr connector pulls documents from an external standalone Solr instance or SolrCloud cluster using Solr’s javabin response type and streaming response parser.

This connector requires a Subversion client that is compatible with JavaHL.

The Zendesk connector uses the Zendesk REST API to retrieve tickets and their associated comments and attachments from a Zendesk repository.

Description

Retrieve content from a Jive instance.

The Kaltura V2 connector uses the Kaltura Java API client to retrieve data stored in Kaltura.

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.

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.

Description

The Web V1 connector retrieves data from a Web site using HTTP and starting from a specified URL.