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

Application Service Guide

Application Service Guide

Grid and Content Management Service

Grid and Content Management Service

The Content Management Service provides information about reference data to the Data Integration Service. You must configure a Content Management Service locally to each Data Integration Service or Data Integration Service process that reads reference data.
When you create a Data Integration Service on a grid, you can assign a Data Integration Service process from the grid Data Integration Service to each node that will run a mapping. To provide reference data information to the Data Integration Service process on each node, configure a Content Management Service on each node. Associate each Content Management Service with the Model Repository Service that you associate with the Data Integration Service on the grid.
The following image shows an example domain that contains three nodes and that defines two of the nodes on a grid:
A Data Integration Service runs on a grid that contains two nodes. A Data Integration Service process and a Content Management Service run on each node. A Model Repository Service runs on a third node in the domain.
The following application services and processes run in the domain:
  • A single Data Integration Service named DIS_grid that runs on the grid.
  • Data Integration Service processes that you assign from DIS_grid to each node in the grid. The process names are DIS_process_1 and DIS_process_2.
    The Data Integration Service processes run on Node1 and Node2 respectively. When you run a job on the grid, the Data Integration Service processes run the job.
  • A Content Management Service named CMS1.
    CMS1 runs on Node1 and is associated with DIS_process_1.
  • A Content Management Service named CMS2.
    CMS2 runs on Node2 and is associated with DIS_process_2.
  • A single Model Repository Service named MRS1 that runs on Node3.
    DIS_grid is associated with MRS1. The Content Management Services CMS1 and CMS2 are also associated with MRS1.
In this example, the Model Repository Service runs on a node outside the Data Integration Service grid. However, the Model Repository Service can run on any node in the domain.

0 COMMENTS

We’d like to hear from you!