Enabling and disabling Case Analyzer
When Case Analyzer threads run on more than four Content Platform Engine nodes, the Content Platform Engine might show performance symptoms. You can disable Case Analyzer on some nodes to prevent performance effects.
About this task
When Case Analyzer is enabled on the Content Platform Engine, Case Analyzer threads run on the Content Platform Engine nodes to collect event data for the Case Analyzer store.
When Case Analyzer 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 Analyzer threads run on all of the Content Platform Engine nodes. Case Analyzer data collection can keep up with Content Platform Engine event generation when Case Analyzer threads run on one or two Content Platform Engine nodes in most Content Platform Engine clusters. It is recommended to keep Case Analyzer enabled on four or fewer nodes in Content Platform Engine clusters.
- Removing dimensions with many of members from the Case Analyzer configuration
- Compressing the Case Analyzer data for a long time period
You can use the following instructions to enable or disable Case Analyzer in the Administration Console for Content Platform Engine.
You can do these steps with all server_name nodes, with the exception of at least one, in the cluster. Do not disable Case Analyzer on the top domain level.
Procedure
To disable Case Analyzer for a server:
- Start the administration console. For more information, see Starting the administration console.
- Go to .
- Go to the Properties tab, find the Subsystem Configurations property, click the drop-down list, and choose Process Engine Configuration.
- Double click the server_name, and go to the Workflow Subsystem tab.
- Click the Configuration source to "this object".
- Clear the Case Analyzer enabled control, and click Save.
- Restart the Content Platform Engine cluster so that the new configuration takes effect.
What to do next
RemoteServerUrl
parameter in the WcmApiConfig.properties file in the
/config subdirectory where the captm.sh or
captm.bat script is located.