Cluster Deployment Descriptor Reference : Processing Units Tab — General Settings and Properties

Processing Units Tab — General Settings and Properties
For example, for well-known address cluster discovery configuration, you would add tangosol.coherence.localhost and tangosol.coherence.localport properties at the processing unit level (see Localhost and Localport Properties).
 
Check the checkbox to enable database concepts functionality for this processing unit. Available only with TIBCO BusinessEvents Data Modeling add-on software.
Note: In certain TIBCO BusinessEvents Monitoring and Management methods, you may be prompted for a session name. For session name you generally put the agent class name. However, if the agent class also has a key, you must instead use the key value. For this reason the key value must uniquely identify the agent.
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.
Ensure that inference agents of the same class in different PUs have different values. This value determines the order of each instance of an agent class for startup, as well as failover and failback in fault tolerance situations.
The properties in this section are used to configure the Coherence (cache) log. This log is used only by cache servers, and only if cache-aside strategy for database updates is used.
jdk (Requires JDK 1.4 or later)
log4j (Requires log4j libraries to be in the classpath)
If you specify jdk or log4j you must also perform appropriate configuration of the JDK or Apache log4J logging libraries.
Specifies the maximum number of characters that the logger daemon processes from the message queue before discarding all remaining messages in the queue.
All discarded messages are summarized by the logging system with a single log entry detailing the number of discarded messages and their total size. When the queue empties, the logger is reset and subsequent messages are again logged.
The purpose of this setting is to avoid a situation where logging can itself prevent recovery from a failing condition, for example by contributing to timing issues.