Introduction

Connectors operate at the beginning of the Exalead CloudView indexing process. They send documents coming from different data sources to the Push API server (PAPI server), through the PAPI protocol.

This chapter gives you the basics about Exalead CloudView connectors:

This page discusses:

See Also
Creating a Standard Connector
Deploying Standard Connectors

The Push API

The Push API is the public document API that allows Exalead CloudView to index data from any source.

It supports the basic operations required to develop new connectors, both managed and unmanaged.

  • A managed connector is a piece of code running within Exalead CloudView. Package it as a Exalead CloudView Plugin to deploy and configure it in Exalead CloudView.

    Develop it in Java, using the Connectors Framework API available in:

    • <INSTALLDIR>\sdk\java-customcode for V6R2014 and higher versions.
    • <INSTALLDIR>\sdk\cloudview-sdk-java-connectors in previous versions.

  • An unmanaged connector is an external component that sends data to Exalead CloudView using the Push API. You can develop an unmanaged connector in any language, either by using Exalead CloudView Push API clients (available in Java, C# and PHP), or by directly targeting the HTTP API.

    Manage and deploy unmanaged connectors yourself, as Exalead CloudView is not aware of these connectors.

Note: For more details on the Push API and connector customization, see the Exalead CloudView Connector Programmer's Guide

Default and Optional Connectors

This guide covers the configuration of the connectors installed by default with Exalead CloudView.

You can also install optional connectors for other data sources, for example, Microsoft SharePoint, ENOVIA ER, EMC Documentum, etc. For more information, contact your NETVIBES representative.