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

Metadata Access Service Architecture

Metadata Access Service Architecture

The Metadata Access Service receives requests from the Developer tool at design time to fetch an object metadata from a Hadoop cluster. The Metadata Access Service access the Hadoop cluster and provides the object metadata to the Developer tool.
The Metadata Access Service uses HTTP or HTTPS to communicate with Hadoop clusters and the Developer tool that sends metadata access requests. The following image shows how the Metadata Access Service components complete job requests:
  1. When importing a data object, the Developer tool sends a request to the Metadata Access Service along with the reference to the connection object.
  2. The Metadata Access Service accesses the cluster configuration defined in the connection object.
  3. The Metadata Access Service uses the Hadoop details from the cluster configuration and extracts the object metadata from the Hadoop cluster.
  4. The Metadata Access Service returns the metadata to the Developer tool.
  5. When you save the data object, the information is saved in the Model repository.