Start page / Documentation / Additional Documentation / FirstSpirit Exalead CloudView

FirstSpirit Exalead CloudView Integration

This document describes the different possibilities for integrating the Content Management System FirstSpirit and the Enterprise search engine technology EXALEAD CLOUDVIEW™.

In general, both products can be used independently. But, in combination both modern technologies can be connected with each other so that the user of the website, who wants to find specific information within FirstSpirit contents in a simple way, has a high usage value.

The following five aspects are described:

Architecture of the integration solution between FirstSpirit and Exalead
Description of the der FirstSpirit runtime component for displaying Exalead search results (webserver-sided, module “Exalead Live”)
Explanation of how to provide documents with permissions for a personalised search
Incremental update of the index by means of the FirstSpirit module “Exalead Content-Update”
Use of auto-completion

Technically seen, the FirstSpirit Exalead integration divides thus into two sub-modules: “Exalead Live” for the search representing the results, and “Exalead Content-Update” for an incremental update of the index.

This documentation refers to version 2.0 of the modules FirstSpirit Exalead Live and FirstSpirit Exalead Content-Update!

FirstSpirit Exalead CloudView Integration

This documentation is relevant for the following user groups:

User group	Chapter
Administrators	Chapter 2: describes the architecture of integration solutions and the necessary components by means of diagrams. Chapter 3: describes the FirstSpirit runtime component for displaying Exalead search results (webserver-sided, module "Exalead Live")
Developers	Chapter 2: describes the architecture of integration solutions and the necessary components by means of diagrams. Chapter 3: describes the FirstSpirit runtime component for displaying Exalead search results (webserver-sided, module "Exalead Live") Chapter 4: Exalead provides the possibility to read out user and group information from documents so that these documents will be shown in the list of search results only to authorised users. In this way, personalised search results can be displayed. This chapter treats with the options to provide documents with permissions. In this context, the use of the Push-API will be explained, too. The Push-API permits to transfer documents separately into the index. Chapter 5: The Push-API of Exalead provides an interface for transferring documents directly into the index of the search engine ("push"). By this means, changes at documents can be given notice to the index immediately, without the next crawling date must be awaited. In this chapter the steps necessary for configuring the Push-API. Subsequently, the FirstSpirit sub-modul "Exalead Content-Update" which bases on the Push-API will be described. Chapter 6: Use of the auto-completion.

User group

Chapter

Administrators

Chapter 2: describes the architecture of integration solutions and the necessary components by means of diagrams.
Chapter 3: describes the FirstSpirit runtime component for displaying Exalead search results (webserver-sided, module "Exalead Live")

Developers

Chapter 2: describes the architecture of integration solutions and the necessary components by means of diagrams.
Chapter 3: describes the FirstSpirit runtime component for displaying Exalead search results (webserver-sided, module "Exalead Live")
Chapter 4: Exalead provides the possibility to read out user and group information from documents so that these documents will be shown in the list of search results only to authorised users. In this way, personalised search results can be displayed. This chapter treats with the options to provide documents with permissions. In this context, the use of the Push-API will be explained, too. The Push-API permits to transfer documents separately into the index.
Chapter 5: The Push-API of Exalead provides an interface for transferring documents directly into the index of the search engine ("push"). By this means, changes at documents can be given notice to the index immediately, without the next crawling date must be awaited. In this chapter the steps necessary for configuring the Push-API. Subsequently, the FirstSpirit sub-modul "Exalead Content-Update" which bases on the Push-API will be described.
Chapter 6: Use of the auto-completion.

Print version | Page start