Connectors Configuration Reference

Fusion comes with a standard set of built-in connectors:

  • Local Filesystem connector

  • File Upload connector

  • JDBC connector

  • Web connector

Built-in connectors are in fusion/3.1.x/apps/connectors/bootstrap-plugins/.

Additional connectors are available for download at You can look in fusion/3.1.x/apps/connectors/plugins/ to see which additional connectors are currently installed.

List of connectors

Database connectors


The Couchbase connector uses the Cross-Datacenter Replication (XDCR) feature of Couchbase to retrieve data stored in Couchbase continuously in real-time.



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.


Filesystem connectors

The Box connector retrieves data from a 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 Dropbox connector retrieves data from a Dropbox cloud-based data repository.


File Upload

The File Upload connector provides a convenient way to quickly ingest data from your local filesystem. It’s available in the Quickstart interface in addition to the Index Workbench and the Datasources page.



Retrieve documents using the File Transfer Protocol (FTP).


Google Drive

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.


Local Filesystem

A filesystem-based data store is a network of nodes to be traversed, where each node (such as a Unix file directory) provides information about its child nodes (such as the files in that directory) or references other nodes (such as links in an HTML document).



The S3 connector can access AWS S3 buckets in native format.



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.


Windows Share

The Windows Share connector can access content in a Windows Share or Server Message Block (SMB)/Common Internet File System (CIFS) filesystem.


Hadoop cluster connectors


The Hadoop Connector is a MapReduce-enabled crawler which leverages the scaling qualities of Apache Hadoop.


Push content connectors

Solr Push Endpoint

The Solr Push Endpoint accepts documents and pushes them to Solr using the Fusion index pipelines.


Repository connectors


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 "" and its plugin type is "azure".



This connector uses Drupal’s Services 7.x­3.11Module REST API.



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



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



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



The ServiceNow Datasource retrieves data from ServiceNow repository via the ServiceNow REST API. ServiceNow records are stored in named tables.



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


SharePoint Online

The SharePoint Online 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.


Solr Index

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 which javahl.



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


Script connectors


The Javascript connector allows users to write ad-hoc document retrieval routines to fetch content from filesystems and websites.


Social media connectors


Retrieve content from a Jive instance.



The Slack connector is used to retrieve data from a Slack service. The connector sends requests to the Slack REST API.


Web connectors


The Web connector is used to retrieve data from a Web site using HTTP and starting from a specified URL.


Installing a connector

Connectors are installed by uploading them to the blob store. You can install connectors:

  • By installing connectors as "bootstrap plugins", that is, by putting them in the bootstrap-plugins directory during initial installation or an upgrade

  • By using the Fusion UI after installation or an upgrade

  • By using the Blob Store API after installation or an upgrade.

During upgrades, the migrator handles some aspects of installing connectors. Depending on the target version and the presence or absence of an Internet connection, there might be manual steps. Installing connectors during upgrades is explained where needed in the upgrade procedures.

Installing a connector as a bootstrap plugin

Fusion can install connectors as "bootstrap plugins." All this means is that you put the connector zip files in a specific directory named bootstrap-plugins, and Fusion installs the connectors the first time it starts during initial installation or an upgrade.

How to install a connector as a bootstrap plugin
  1. Download the connector zip file from

    Don’t expand the archive; Fusion consumes it as-is. Also, don’t start Fusion until instructed to do so by the installation or upgrade instructions.

  2. Under the version-numbered Fusion directory, place the connector in the directory apps/connectors/bootstrap-plugins/ (on Unix) or \apps\connectors\bootstrap-plugins\ (on Windows).

  3. Start Fusion when instructed to do so in the installation or upgrade procedure.

Installing a connector using the Fusion UI

  1. Download the connector zip file from

    Do not expand the archive; Fusion consumes it as-is.

  2. In the Fusion UI, navigate to DevOps > Blobs.

  3. Click Add.

  4. Select Connector Plugin.

    Uploading a connector

    The "New 'Connector Plugin' Upload" panel appears.

  5. Click Choose File and select the downloaded zip file from your file system.

    Uploaded connector

  6. Click Upload.

    The new connector’s blob manifest appears.

    Uploaded connector

    From this screen you can also delete or replace the connector.

Installing a connector using the Blob Store API

  1. Download the connector zip file from

    Do not expand the archive; Fusion consumes it as-is.

  2. Upload the connector zip file to Fusion’s blob store.

    Specify an arbitrary blob ID, and a resourceType value of plugin:connector, as in this example:

    curl -H 'content-type:application/zip' -X PUT 'localhost:8764/api/blobs/myplugin?resourceType=plugin:connector' --data-binary

    Fusion automatically publishes the event to the cluster, and the listeners perform the connector installation process on each node.

    If the blob ID is identical to an existing one, the old connector will be uninstalled and the new connector will installed in its place. To get the list of existing blob IDs, run: curl -u user:pass localhost:8764/api/apollo/blobs
  3. Look in fusion/3.1.x/apps/connectors/plugins/ to verify that the new connector is installed.

Updating a connector

If you are updating the Jive connector from Fusion 2.0 or earlier, see Jive Connector and Datasource Configuration in the datasources and connectors reference.

On Unix, you can update a connector by simply uploading the new one. Fusion overwrites the old one, and no restart is needed.

On Windows, a different procedure is needed:

How to update a Fusion connector on Windows
  1. Delete the old connector, as explained below.

  2. Restart Fusion.

  3. Upload the new connector.

Deleting a connector

You can delete a connector using the Fusion UI or the Blob Store API.

Deleting a connector using the Fusion UI

  1. In the Fusion UI, navigate to DevOps > Blobs.

  2. Under Connector Plugin, select the connector to delete.

  3. Click Delete Blob.

    Delete a connector

    Fusion prompts you to confirm that you want to delete the blob.

  4. Click Yes, Delete.

    The connector disappears from the blob list.

Deleting a connector using the REST API

  1. Get the list of blobs of the connector plugin type:

    curl -u user:pass http://localhost:8764/api/apollo/blobs?resouType=plugin:connector
  2. Locate the connector you want to delete, and copy its ID.

    For example, the Jive connector ID is lucid.jive:

  "name" : "lucid.jive",
  "contentType" : "application/zip",
  "size" : 125302,
  "modifiedTime" : "2017-06-13T17:49:20.171Z",
  "version" : 1570112704530612224,
  "md5" : "7032bf2c038bb2d1e27aee82c056c0fb",
  "metadata" : {
    "connectorBootstrapPluginName" : "lucid.jive",
    "resourceType" : "plugin:connector"
  1. Delete the connector as follows:

    curl -u user:pass -X DELETE http://localhost:8764/api/apollo/blobs/<id>

    For example

    curl -u user:pass -X DELETE http://localhost:8764/api/apollo/blobs/lucid.jive

    A null response indicates success. You can verify that the connector is deleted like this:

    curl -u user:pass http://localhost:8764/api/apollo/blobs | grep lucid.jive