|
Product Details
Livelink ECM - Federated Query Server provides a single access point, using a single search format, to simultaneously query multiple content repositories.
The following sections describe the functionality of the Federated Query Server product in more detail:
Alternatively, you can download the Federated Query Server Product Overview.
If you would like more information about Federated Query Server, and how you can use this technology in your own organization, please contact us.
Unification of Repositories
Federated Query Server routes queries simultaneously to multiple HTTP-compatible content repositories, including:
With a single query, users gain access to a wide range of valuable information both within and outside the organization.
top
Configurable Query Options
Federated Query Server automatically translates the user's query into the appropriate syntax for each content repository, eliminating the need to learn multiple query languages. Boolean, proximity, wildcard, keyword, metadata and fielded queries are all supported.
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.
The administrator can also fully customize the interface through which end users specify query parameters, creating unique interfaces for different classes of users.
top
Configurable Result Listings
Federated Query Server formats results from multiple repositories to conform to a single standard specified by the administrator.
The result format 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).
Search terms can be highlighted, even if the content repository does not return highlighting information.
The administrator can also fully tailor the portions of the result page around the result list, for example by adding logos, graphics, and navigational links.
top
Sorted, Merged & Clustered Results
Federated Query Server provides a number of features to enhance search results:
- Results can be sorted by any element of a result (for example, score, date, author, etc)
- Duplicate results from different content repositories can be merged to eliminate repeat listings
- 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
- Results sharing the same content or location can be grouped together to form clusters, helping users find the information most pertinent to their query
top
Security
Federated Query Server has support for accessing content repositories that require the following forms of authentication:
- Web form log-in
- Static HTTP authentication - Basic, NTLM or Kerberos
- Delegated HTTP authentication
- Cookies generated by SSO (single sign-on) software
- User impersonation
Federated Query Server also supports access to HTTPS content repositories, either directly or via a proxy server using SSL tunneling.
top
Administration
Federated Query Server ships with a user-friendly Windows configuration tool with built in wizards to perform most administration tasks. Click here to view some screen shots of the configuration tool.
top
Summary of Benefits
| Simpler queries | - | Extends a search across multiple content repositories, allowing users to quickly and easily find information that would otherwise require greater expertise and more time |
| Quality results | - | Helps users find the information most pertinent to their query by conceptually clustering the results - users can save time by restricting their viewing to only those groups of results relevant to their query |
|
|
top
Summary of Features
| Ease of administration |
- User-friendly configuration tool
- Wizard for adding new content repositories, and modifying existing ones
- Preset configurations for Open Text products
|
| Search multiple repositories |
- Parallel searching across multiple Internet and Intranet repositories and indexes
- Query operator translation and automatic degradation
- Support for keyword and Boolean queries, including wildcards and proximity
- Support for metadata queries, including negative field qualification and numeric ranges
- Progress reporting during a query
- Support for multiple URLs per repository, including ability to optionally skip URLs
|
| Display results from multiple repositories |
- Aggregation of results into a single page
- Results sorted into a single list, or grouped according to repository
- Duplicate result removal, with configurable result comparisons
- Results restyled into a common format
- Generation of table of contents for a result page
- Pagination of results, allowing multiple pages of results to be retrieved from each repository
- Modification of result URLs
|
| Added value to results |
- Clustering of results according to their content, location, or both
- Modification of result relevance scores
- Calculation or estimation of result relevance scores
- Search term highlighting
|
| End user control |
- Up to 50 full-text query boxes, with default and conjunctive operators
- Up to 50 metadata query boxes, with field qualification and numeric range operators
- Most query and display options selectable from the search page
|
| High configurability |
- Multiple user interfaces, selectable from the search page
- Results page can be displayed as HTML, XML, CSV, or virtually any other format
- Configurable error messages
|
| Conformance to Web standards |
- Support for Basic, NTLM, Kerberos and delegated HTTP authentication
- Support for Web form authentication
- Cookies can be passed to and from Intranet repositories
- Ability to access secure servers using SSL 2.0, SSL 3.0 or TLS 1.0
- Compatible with proxy servers
- Support for HTTP redirection
- Generation of usage logs
- Character set translation between UTF-8 and ISO 8859-1
|
|
|
top
System Requirements
Federated Query Server is currently supported on Windows NT 4.0 Server (SP3, 5, or 6a), Windows XP, Windows 2000 Server, Windows Server 2003, Solaris 7+ and HP-UX 11+. The following hardware and software are required.
| Windows NT/XP/2000/2003 |
- Intel Pentium class CPU
- 64MB free RAM
- 20MB free disk space
- SVGA graphics (800x600)
- CGI-compatible Web server
|
| Solaris |
- SPARC CPU
- 64MB free RAM
- 10MB free disk space
- CGI-compatible Web server
|
| HP-UX |
- PA-RISC CPU
- 64MB free RAM
- 10MB free disk space
- CGI-compatible Web server
|
|
|
top
|