Controlling Task Processing on Specific Nodes

Overview

There are various reasons to control which nodes in an Oracle Health Insurance application’s cluster will and will not participate in task processing. For example, it is a reasonable scenario that a client may have a 7 node cluster with 3 machines dedicated to the UI and 4 machines dedicated to task processing. This allows the cluster operator to better maintain the utilization of resources throughout a clustered installation.

In order to facilitate this scenario, the cluster operator will have to configure the load balancer to only direct traffic to the UI nodes, and configure the Oracle Health Insurance application’s nodes to only process tasks if they are part of the set of processing nodes.

Configuring Task Processing

By default, if a managed server that executes an Oracle Health Insurance application is started then it will start processing tasks from the work backlog queue. The default behavior can be overridden by setting command-line parameter ohi.startup.start.task.processing; if it is set to false a managed server that executes an Oracle Health Insurance application will not process tasks after it is started. The default value is true, meaning the managed server that executes an Oracle Health Insurance application will start processing tasks from the work backlog queue after it is started.