Copyright © TIBCO Software Inc. All Rights Reserved |
Many properties can be defined at the cluster level, processing unit level, or agent level, as appropriate (see Using Properties at Different Levels).
Check the checkbox to enable cache storage on this processing unit (PU). Settings available depend on the types of cache agents in the PU.
• In PUs used only for dashboard agents (available in TIBCO BusinessEvents Views only): the checkbox is unchecked and cannot be checked. Dashboard agents cannot function as cache servers.Note: Enable cache storage in PUs running inference and query agents for test deployments only. Not recommended in production. Check the checkbox to enable database concepts functionality for this processing unit. Available only with TIBCO BusinessEvents Data Modeling add-on software. Required for recovery of scorecards. Recommended in all cases, for situations that require an agent instance to be uniquely identified.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. Because of this, the key value must uniquely identify the agent. Specifies the priority of the agent for load balancing purposes. (Not available in TIBCO BusinessEvents Express.)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 log. This log is used only if Oracle Coherence is used as the cache provider. This log is used by cache agents, and only if cache-aside database write strategy 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.Default is stdout.
• 4-9: All the above plus internal debugging messages (the higher the number, the more the messages) 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.Logging occurs on a dedicated low-priority thread to further reduce its impact on the critical portions of the system. You must also specify the following JMX-related properties to enable cluster statistics to appear in the monitored objects table in MM. (MM is not available in TIBCO BusinessEvents Express.)
Copyright © TIBCO Software Inc. All Rights Reserved |