Funnelback logo

Documentation

Connector collections

Introduction

Connector collections use custom Java based connector systems to gather data from various enterprise applications. Connectors for these applications are provided by third party vendors, and can be purchased by contacting sales@funnelback.com to discuss your specific requirements.

Installing Connectors

The third party connector systems used by Funnelback are distributed as a collection of .jar (Java Archive) files, which must be installed in $SEARCH_HOME/lib/java/connector. After installing these .jar files, a new 'connector' collection can be created to configure Funnelback to gather data from the desired repository.

Creating Connector Collections

Connector collections are created just like any other Funnelback collection, and have a number of shared parameters.

In addition to these parameters, each repository type requires some specific configuration parameters. The connector parameters field provides a simple interface for including additional parameters to specific connectors, though these can also be configured directly in collection.cfg.

While a range of repositories are supported, documentation on configuration is provided by Funnelback only for those listed below.

Controlling Connector Document Gathering

A number of parameters are available to control how content is gathered from a repository.

Many repositories will contain a variety of content, some of which is not useful to return as a search result. To allow such content to be eliminated, Funnelback provides the ability to define a selection policy to decide whether to store or discard content. The 'Connector selection policies' document below provides an introduction to the process of creating a new selection policy.

Connector Search Security

A common requirement with connector collections is that the search interface should authenticate the user performing the search, and present only results which the user is authorised to view. Funnelback supports this kind of security checking by storing each document's security information when it is gathered, and then checking that the user is able to view each relevant result when a search is performed.

Details on configuring this kind of search security can be found below.

top ⇑