SES联邦搜索.ppt

Oracle Confidential * Hello. Today, I will begin this session of Oracle Secure Enterprise Search, with a focus on secure Federated search. * This is the agenda planned for this session. I will start with an overview of secure federated search. Then, we’ll look at the federation architecture. We’ll discuss the federation trusted entities. We will discuss the reasons for using SES-to-SES federation also. We will then discuss federator, and Searchlet. We will also look at the entity translations, and directory mappings. We’ll look at the steps to create a federated sources. Federation is also possible for non-SES sources. Finally, we will explore the Suggested content feature that SES provides. * That said, lets begin with the topic. Oracle Secure Enterprise Search provides the capability of searching multiple Oracle SES instances with their own document repositories and indexes. It provides a unified framework to search the different document repositories that are crawled, indexed, and maintained separately. Unlike the traditional centralized search solution, federation enables distributed search. In this solution, a federation broker calls the federation endpoint to collect content matching the search criteria for the sources managed at that endpoint. Thus, this solution enables scalability, leverages an existing index and so on. Federated search allows a single query to be run across multiple repositories. It aggregates the search results from various repositories to show one result list to the user. All query information including user credentials, are passed along with the search so that each remote application can process the query against its own document repository. The federation framework includes SES-to-SES federation and the Suggested content. We’ll look at the SES-to-SES federation 1st and in the last section we will discuss Suggested content. * We’ll now discuss the reasons for using SES-to-SES Federation. Federation between SES instances is used