Defining a Federated Source
The head of the Documentation team gives Timothy the link for the SES box where they have a Live Link Content Database source configured. As the documentation set is very huge, they do not want to configure the same on multiple SES boxes. They want to distribute the index load to multiple SES boxes.
As the remote source is an SES instance, Timothy decides to implement
SES-to-SES federation. With this Federation framework, Timothy can make
use of the existing search functionality and need not recrawl the same
data.
Timothy therefore leverages the existing search system to expand the search domain for the documentation team. He first observes the exisiting source and then creates a Federated Source on another SES box, thus facilitating the documentation team to manage their content.
Let's watch Timothy creating a Federated Source.
 |
