Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service REST API
  10. Data Integration Service Applications
  11. Data Privacy Management Service
  12. Enterprise Data Preparation Service
  13. Interactive Data Preparation Service
  14. Informatica Cluster Service
  15. Mass Ingestion Service
  16. Metadata Access Service
  17. Metadata Manager Service
  18. Model Repository Service
  19. PowerCenter Integration Service
  20. PowerCenter Integration Service Architecture
  21. High Availability for the PowerCenter Integration Service
  22. PowerCenter Repository Service
  23. PowerCenter Repository Management
  24. PowerExchange Listener Service
  25. PowerExchange Logger Service
  26. SAP BW Service
  27. Search Service
  28. System Services
  29. Test Data Manager Service
  30. Test Data Warehouse Service
  31. Web Services Hub
  32. Application Service Upgrade
  33. Appendix A: Application Service Databases
  34. Appendix B: Connecting to Databases from Windows
  35. Appendix C: Connecting to Databases from UNIX or Linux
  36. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Search Service Architecture

Search Service Architecture

The Search Service interacts with different components in the Informatica domain when it builds the search index and returns search results. The Search Service can build a search index based on content in a Model repository and a profiling warehouse.
The following diagram shows the Informatica domain components with which the Search Service interacts:
The diagram shows how the Search Service uses extractors to build the search index based on objects in a Model repository and a profiling warehouse. The diagram also shows how Informatica Analyst and Business Glossary Desktop submits search requests to the Search Service.
When you create the Search Service, you specify the associated Model Repository Service. The Search Service determines the associated Data Integration Service based on the Model Repository Service.
To enable search across multiple repositories, the Search Service builds a search index based on content in one Model repository and one profiling warehouse. To enable search on multiple Model repositories or multiple profiling warehouses, create multiple Search Services.
The Search Service extracts content, including business glossary terms, from the Model repository associated with the Model Repository Service. The Search Service extracts column profile results and domain discovery results from the profiling warehouse associated with the Data Integration Service. The Search Service also extracts permission information to ensure that the user who submits a search request has permission to view each object returned in the search results. The Search Service stores the permission information in a permission cache.
Users can perform a search in the Analyst tool or Business Glossary Desktop. When a user performs a search in the Analyst tool, the Analyst Service submits the request to the Search Service. When a user performs a search in Business Glossary Desktop, Business Glossary Desktop submits the request to the Search Service. The Search Service returns results from the search index based on permissions in the permission cache.