Processing Units Configuration Settings

CDD Processing Units Tab Settings
Property Notes
Name Enter a name that is unique across the cluster.
Log Configuration Browse to and select a log configuration, configured on Collections tab. See Log Configurations for more details.
Hot Deploy Check the check box to enable hot deployment for this processing unit.

See TIBCO BusinessEvents Administration for details about hot deployment.

Enable Cache Storage Check the check box to enable cache storage on this processing unit (PU). Settings available depend on the types of cache agents in the PU.
  • In PUs used to host cache agents: The check box is checked and cannot be unchecked.
  • In PUs that host inference agents or query agents (or both):
    • If checked, the PU is used for storing cache data.
    • If unchecked, the PU is not used for storing cache data.
Note:
Enable cache storage in PUs running inference and query agents for test deployments only. Not recommended in production.

Default value for PUs containing inference agents or query agents (or both) is unchecked.

Enable DB Concepts Check the check box to enable database concepts functionality for this processing unit.
Agents Section
Agent Name of the agent class you selected. Agent classes are defined on the Agent Classes tab.
Key Specifies a value that uniquely identifies an instance of an agent of this class at deploy time.

Required for recovery of scorecards. Recommended in all cases, for situations that require an agent instance to be uniquely identified.

The value for Key must uniquely identify the agent.

No default value.

Priority Specifies the priority of the agent for load balancing purposes.

The priority indicates the order in which standby agents become active, and conversely, the order in which active agents become standbys, when new agents join the cluster.

The lower the number, the higher the agent is in the activation priority list. For example, an agent with priority 2 has a higher priority than an agent with a priority of 6.

For agents with equal priority, the cluster decides which ones to activate.

No default value.