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

Grid and Content Management Service

Grid and Content Management Service

You must associate a Content Management Service with a Data Integration Service to run mappings that read reference data. To associate a Content Management Service with a Data Integration Service that runs on a grid, you must create and configure multiple Content Management Services and multiple Data Integration Services.
To associate a Content Management Service with a Data Integration Service that runs on a grid, perform the following tasks:
  1. Create a grid where each node in the grid includes both the service and compute roles.
  2. Create a Data Integration Service and assign the service to run on the grid. Configure the Data Integration Service to run jobs in separate local or remote processes.
  3. Create a Content Management Service and a new Data Integration Service to run on each node in the grid.
  4. Associate each Content Management Service with the Data Integration Service that runs on the same node.
  5. Associate each Content Management Service and Data Integration Service with the same Model Repository Service that the Data Integration Service on grid is associated with.
    The Content Management Service provides reference data information to all Data Integration Service processes that run on the same node and that are associated with the same Model Repository Service.
The following image shows an example domain that contains three nodes. A total of three Data Integration Services, two Content Management Services, and one Model Repository Service exist in the domain:
A Data Integration Service is assigned to run on a grid that contains two nodes. A separate Content Management Service and a separate Data Integration Service are assigned to run on each node in the grid. A Model Repository Service is assigned to run on a third node that is outside of the Data Integration Service grid.
The following services run in the domain:
  • A Data Integration Service named DIS_grid. DIS_grid is assigned to run on the grid. A DIS_grid process runs on each node in the grid. When you run a job on the grid, the DIS_grid processes run the job.
  • A Data Integration Service named DIS1 and a Content Management Service named CMS1 assigned to run on Node1. CMS1 is associated with DIS1.
  • A Data Integration Service named DIS2 and a Content Management Service named CMS2 assigned to run on Node2. CMS2 is associated with DIS2.
  • A Model Repository Service named MRS1 assigned to run on Node3. Each Data Integration Service and Content Management Service in the domain is associated with MRS1. In this example, the Model Repository Service runs on a node outside of the Data Integration Service grid. However, the Model Repository Service can run on any node in the domain.