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.
Updating the Content Management Service Master Status
You can use infacmd to set the Master CMS property of a Content Management Service to true or false. For example, use infacmd to update the master status of the Content Management Services on the primary and backup nodes if the primary node fails in a high availability environment.
To update the master status of the services on a primary and backup node, perform the following steps:
1. Run infacmd cms updateserviceoptions to set the master status of the Content Management Service on the primary node to false.
Note: The MultiServiceOptions.Master option controls the status of the service.
2. Run infacmd cms updateserviceoptions to set the master status of the Content Management Service on the backup node to true.
3. Associate the backup Content Management Service with a non-grid Data Integration Service running on the same node.
4. Restart the Content Management Service on the backup node.