Enabling and disabling Case History

When Case History threads run on more than four Content Platform Engine nodes, the Content Platform Engine might show performance symptoms. You can disable Case History on some nodes to prevent performance effects.

About this task

Case History is enabled on the Content Platform Engine by default in all Content Platform Engine versions up to V5.5.4. Case History threads run on the Content Platform Engine nodes to collect event data for the Case History store. This enablement is in place even if Case Manager is not configured.

When Case History threads run on more than four Content Platform Engine nodes, then the Content Platform Engine might show performance symptoms.

In larger Content Platform Engine clusters, it is not necessary to have Case History threads run on all of the Content Platform Engine nodes. Case History data collection can keep up with Content Platform Engine event generation when Case History threads run on one or two Content Platform Engine nodes in most Content Platform Engine clusters. It is recommended to keep Case History enabled on four or fewer nodes in Content Platform Engine clusters.

You can use the following instructions to enable or disable Case History in the Administration Console for Content Platform Engine.

Procedure

To disable Case History for a server:

  1. Start the administration console. For more information, see Starting the administration console.
  2. Go to Global Configuration > Administration > Sites > Initial Site > Virtual Servers > node_name > server_name.
  3. Go to the Properties tab, find the Subsystem Configurations property, click the drop-down list, and choose Process Engine Configuration.
  4. On the Process Engine Configuration tab, find the History Exporter Enabled property.
    The value for this property is True by default.
  5. For each server where you want to disable Case History, set the History Exporter Enabled property to False.
    Do not close the tab. This tab does not have a Save button, and closing the tab before you save will discard the change.
  6. Click back to the Properties tab, which is named the same as the server, and click Save.
    Your updates on the Process Engine Configuration are saved, and Case History is disabled for that server.

What to do next

If you want to re enable the Case History setting, use the same technique but change the History Exporter Enabled property back to True. Remember to save changes on the Server Properties tab before you close the Process Engine Configuration tab.