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

Content Management Service and High Availability

Content Management Service and High Availability

Configure a Content Management Service on a backup node in a domain to support the high availability of run-time operations that use Content Management Service properties.
For example, in a domain with a primary node that runs a Data Integration Service and a master Content Management Service, create a Content Management Service on a backup node. You do not need to associate the Content Management Service on the backup node with a Data Integration Service. When you update the properties of the Content Management Service on the backup node, the properties of the Data Integration Service on the backup node are also updated.
Consider the following rules and guidelines when you configure a Content Management Service on the backup node:
  • If you use user-generated content, such as content sets that contain probabilistic or classifier models, verify that the Content Management Service on the backup node runs continually. When the Content Management Service on the backup node runs continually, any change to the user-generated content on the primary node is copied to the backup node.
  • The Content Management Service properties on the backup node can differ from the properties on the primary node. For example, the address reference data and identity population data locations can differ.
  • When the Content Management Service on the primary node is down, you cannot import reference table data from a flat file or a relational table, and you cannot create a probabilistic or classifier model from a flat file. To import flat-file data, restart the Content Management Service on the primary node. Or, reconfigure the master status of the Content Management Services on the primary and backup nodes, so that the Content Management Service on the backup node becomes the master Content Management Service.