Features

OpenText Federated Query Server provides a single access point to simultaneously query multiple content repositories

With Federated Query Server, you can quickly provide users with a unified search system that enables them to find the information they need, improving productivity, and saving time and money.

  • Search federation: A query is routed simultaneously to multiple search engines and content repositories - for example, OpenText Content Server, Microsoft SharePoint, Wikipedia and Google. With a single search, users gain access to a wide range of valuable information from both inside and outside the organization.
  • Query translation: Queries are translated into the appropriate syntax for each content repository, eliminating the need for users to learn multiple query languages. Boolean, proximity, wildcard, thesaurus, metadata and fielded query operators may be translated, as well as metadata values and field names. The query syntax used with Federated Query Server is defined by the administrator, who can choose to develop a new standard or adopt an existing standard that is already familiar to end users.
  • Result parsing: Federated Query Server can parse results returned by a content repository in HTML, XML, JSON and most other textual formats.
  • Merged results: Duplicate results from different content repositories can be merged to eliminate repeat listings.
  • Sorted results: Results can be sorted by any element of a result (for example, score, date, author, etc).
  • Clustered results: Results sharing the same content or location can be grouped together to form clusters, helping users find the information most pertinent to their query.
  • Relevance ranking: Customizable ranking algorithms can be applied to results, to either modify relevance scores returned by a content repository or assign relevance scores to results from content repositories without ranking capabilities.
  • Authentication: Federated Query Server has support for accessing content repositories that require the following forms of authentication: Web form log-in, static HTTP authentication, delegated HTTP authentication, cookies generated by SSO (single sign-on) software, and user impersonation.
  • Customization: Results from multiple repositories are displayed in a single format, which can be adopted from an existing portal or content repository, or customized to meet an organization's individual requirements, or created specifically for further processing or formatting (e.g. XML or JSON). The administrator can also fully customize the interface through which end users issue searches, creating unique interfaces for different classes of users.
  • Integration: Federated Query Server ships with HTML and OpenSearch interfaces, as well as an integration with OpenText Content Server. The OpenSearch description document can be used to directly integrate Federated Query Server with the search bar of a browser (e.g. Google Chrome), an operating system (e.g. Windows 7), or any other OpenSearch client (e.g. SharePoint).
  • Administration: Federated Query Server includes a user-friendly Windows configuration tool with built in wizards to perform most administration tasks. No coding is required to create a new repository connector. There are built in rules for several OpenText products, for OpenSearch and CMIS AtomPub repositories, and for other search engines that return RSS or Atom.

Downloads

Download more information about OpenText Federated Query Server

Demos

  • Web Search

    Six general purpose Web search engines

  • Social Search

    Four social media sites, grouping results by source

  • News Search

    Five TV and newspaper sites, sorting results by date

  • Health Search

    Nine sites containing health and medical information