Longitude Federator
for SharePoint 2010, FAST, and FAST ESP Search
 
  
Extending Unified Search to the Four Corners of Your Global Enterprise with Longitude Federator
Globally distributed organizations often struggle with unifying information across the boundaries of country borders or their IT infrastructure. This could be for a variety of reasons, such as privacy concerns, contractual obligations with customers, bandwidth constraints, or simply lack of IT agreement for a centralized search deployment. Simply put, in some cases you just cannot index the content at remote locations. So if you can't index it, what do you do? The answer: Federate it.

Federated Search enables secure, search-based access to information across an organization regardless of its location, without it being indexed remotely.

The Longitude Federator is the ideal solution for distributed organizations that cannot deploy search centrally and must deploy search at several different locations. The Longitude Federator is the only federation tool in the marketplace that unifies the search results from multiple SharePoint Search, FAST Search for SharePoint and FAST ESP servers into a single unified view of data from all divisions and locations across your organization. This topology is often deployed to address several different concerns, including bandwidth constraints and privacy/security concerns arising from the transfer of confidential data across borders as it's being indexed.
 
 
Why Use Federation?
  • Mitigate privacy and/or security concerns – Indexing content creates a copy of some of the content in the index. In some cases, this can cause privacy and/or security concerns. For example, the European Union has agreements with the United States that, among other things, requires the owner of data to be notified if it is moved outside of its country of origin. An American company indexing content in Europe can avoid violating such agreements using Federation.
     
  • Bandwidth constraints – Organizations that are geographically dispersed often don't have the bandwidth to deploy search globally, because indexing consumes considerable bandwidth. With federation, the only data that moves is one page of search results from each server that is being federated.
     
  • Divisions within an organization may have different search requirements – There are occasions when different divisions within a company want to maintain control of their own search environment. They may have developed their own user interfaces and use different search connectors, for example. A centralized search environment would lose these customizations.
     
  • Limit the size of the search index – In some large distributed organizations with billions of records, it may be undesirable to have a single unified index because of the infrastructure requirements. Federation enables each division to host its own search environment, while also enabling each division to search against all content available.
 
 
LEARN MORE
Request a Demo

SUPPORTED TECHNOLOGIES
Microsoft SharePoint 2010 Search; FAST Search Server for SharePoint 2010; FAST ESP