The document describes an enterprise search scenario involving querying multiple data sources. It involves a crawler that initially extracts data from sources like SAP, Exchange and CRM databases. Indexing and linking of this data is handled by a BEPL engine. When a query is run, the BEPL engine interprets it and retrieves relevant information from the search index and linked data. Caches are also used to improve system performance and manage user credentials and permissions.

1. Enterprise Search Scenario II. Query management I. Data provision Load too high for source systems Direct access is too time-consuming Get. Sources SAP Exchange CRM DB …

2. Enterprise Search Scenario Get. II. Query management I. Data provision Sources SAP Exchange CRM DB … Server Crawler "sucks" data in the initial run 1 Agents control updates, which are carried out daily 2 Agent Crawler Timing

3. Enterprise Search Scenario Get. II. Query management I. Data provision Sources Server BEPL Engine Crawler "sucks" data in the initial run 1 Agents control updates, which are carried out daily 2 BEPL engine interprets information in queue and stores it with its corresponding keywords 3 Information is already being linked at this point 4 Employ ee Client Order Agent Crawler

4. Enterprise Search Scenario Get. II. Query management I. Data provision Sources Server BEPL Engine Crawler "sucks" data in the initial run 1 Agents control updates, which are carried out daily 2 BEPL engine interprets information in queue and stores it with its corresponding keywords 3 Information is already being linked at this point 4 Agent Crawler 5 Search index is created from copied databases Index

5. Enterprise Search Scenario Get. II. Query management I. Data provision Sources Server BEPL Engine Query Crawler "sucks" data in the initial run 1 Agents control updates, which are carried out daily 2 BEPL engine interprets information in queue and stores it with its corresponding keywords 3 Information is already being linked at this point 4 Agent Crawler 5 Search index is created from copied databases Index Query is started 6

6. Enterprise Search Scenario Get. II. Query management I. Data provision Sources Server BEPL Engine Query Client BEPL Engine Crawler "sucks" data in the initial run 1 Agents control updates, which are carried out daily 2 BEPL engine interprets information in queue and stores it with its corresponding keywords 3 Information is already being linked at this point 4 Agent Crawler 5 Search index is created from copied databases Index Query is started 6 7 BEPL engine controls the interpretation of the query

7. Enterprise Search Scenario Get. II. Query management I. Data provision Sources Server Query Client Cache Query and Result Set Cache Credentials Cache Crawler "sucks" data in the initial run 1 Agents control updates, which are carried out daily 2 BEPL engine interprets information in queue and stores it with its corresponding keywords 3 Information is already being linked at this point 4 BEPL Engine Agent Crawler 5 Search index is created from copied databases Index Query is started 6 7 BEPL engine controls the interpretation of the query 8 Cache relieves the system and manages user rights BEPL Engine