Upgrading enterprise search collection types

Funnelback supports a number of collection types that are mostly used for intranet and enterprise search. Most of these won’t be usable in the DXP.

If you find any of these collection types you will need to have a discussion with the content owners to look at alternate ways of accessing the content, or to de-scope items from the search.

Creating an index of database-like content provides some alternate methods of indexing content that was previously indexed via database or directory collections.

Filecopy collections

Filecopy collections are used to index content from network fileshares. Access to these fileshares is unlikely to be granted from the DXP.

Database collections

Database collections are used to index the output of a SQL query from a supported SQL databases.

Remediation should focus on indexing an export of the desired data e.g. as an XML feed, or via an API.

Directory collections

Directory collections are used to index records from within a JDNI directory service such as LDAP.

Remediation should focus on indexing an export of the desired data e.g. as an XML feed, or via an API.

TRIM collections

The TRIM (trimpush) collection type was a special connector used to index the content of a HP TRIM/HP Records Manager/Content Manager repository. This was only supported on the Windows version of Funnelback and is not supported in the DXP.