TIBCO BusinessEvents Express Content relating to Cache OM and backing store does not apply to TIBCO BusinessEvents Express edition.The tables below explain settings and properties used with different types of agent classes. Cache agents have no settings.
See Using Properties at Different Levels to understand the effect of using agent class properties at the cluster level and at the processing unit level to widen the scope of the property.
Table 13 Wizard Settings (All Agent Types) Enter a name that is unique across the cluster. Use the NSName standard as in all names in the CDD. Valid types for your custer depend on object management type, and whether you use any TIBCO BusinessEvents add-on products.Inference Used with all OM types.Cache Used with Cache OM to provide cache storage and other services.Monitoring & Management Used only by the Monitoring and Management component. See Chapter 6, Basic MM Configuration.Query Used with queries, part of the TIBCO BusinessEvents Event Stream Processing add-on product.Dashboard Used with the TIBCO BusinessEvents Views add-on product.
Specifies the maximum number of objects (entities) in each agent’s L1Cache (inference agent) or local cache (query agent). The L1 cache is a local cache used by the inference agent for local access to recently used objects. It is used to optimize access to objects.The query local cache is used in a way similar to the inference agent L1Cache. The query agent’s local cache stores cache data locally for efficient reuse. The local cache listens to and synchronizes the locally stored entity instances with those in the main cache, so that the local cache stays up-to-date. Specifies an age limit on the cached entities in seconds. After this period, they are removed from the local cache.Note Age resets each time an entity is accessed by a query engine. Used for destinations whose threading model is Shared Queue. Set to the same value for all agents configured to deploy in the same processing unit. Used for destinations whose threading model is Shared Queue. Set to the same value for all agents configured to deploy in the same processing unit.In MM Console, this thread appears with the name $default.be.mt$. Specifies the maximum number of active agents of this class. This value is used for fault tolerance. Deployed agents that are acting as standbys can take over from active instances that fail. In many cases, there is no need to keep standby instances.See Load Balancing and Fault Tolerance of Inference Agents in TIBCO BusinessEvents Architect’s Guide for more details. If this project will integrate with a TIBCO ActiveMatrix BusinessWorks project, enter the Repo URL for the ActiveMatrix BusinessWorks project repo URL here.See Task A, Add the Repo URL for BusinessWorks to the CDD in Chapter 21, ActiveMatrix BusinessWorks Integration of TIBCO BusinessEvents Developer’s Guide for more details about the value to use. If checked, agents of this class run concurrent run to completion (RTC) cycles. (Also known as concurrent Rete and, in prior releases, as concurrentwm). Use of the concurrency features requires Cache OM and affects project design. See TIBCO BusinessEvents Architect’s Guide for more on this and other concurrency features. By default, TIBCO BusinessEvents checks if the external IDs (@extId) of entities are unique within the current agent. If you want to check for uniqueness of external IDs across the cluster, check this check box. Performing this check affects performance.
For example, if you set the value to 10,000, then the engine loads handles in blocks of 10,000, instead of trying to load them in a single batch. Smaller batch sizes result in slower recovery. Experiment with batch size to establish the best batch size to use for your environment. If set to false: When a rule action changes the value of an entity’s properties, then the entity instance is evicted from the cache instead of updating it. Updates are saved in the backing store. Use this setting and Agent.AgentClassName.threadcount as needed to improve performance and cache memory management.This property interacts with the Cluster > Domain Objects setting, Evict From Cache on Update (and its override settings if any:
• When this CDD property is set to true, the domain objects Evict From Cache on Update setting is ignored, in the agent for which the property is set.
• When this CDD property is set to false, the domain objects Evict From Cache on Update setting overrides this CDD property.See Cluster Tab — Cache OM — Domain Objects Settings for details on the Evict From Cache on Update setting. If set to true, checks for uniqueness of external IDs across the cluster. Performing this check affects performance so use it with care. Agent.AgentClassName.threadcount Defines the number of threads performing cache writing jobs ($CacheWriter thread tuning). Used only with cache-aside database write strategy.Tip This property is also used to define the number of Recovery threads (used for recovering Cache Plus Memory entity handles at inference engine startup). Agent.AgentClassName.dbthreadcount The number of threads performing database writing jobs ($DBWriter thread tuning). Writes include applying entity inserts, updates, and deletes to the database. Used only with cache-aside database write strategy. Agent.AgentClassName.dbOpsQueueSize The size of the queue (a Java blocking queue) for database writing jobs. Used only with cache-aside database write strategy. Agent.AgentClassName.dbOpsBatchSize Agent.agentClassName.enableParallelOps Set this property to false so that when cache-aside database write strategy is used, all post-RTC operations are done on a single thread, instead of the normal multi-threaded cache-aside strategy (see Cache Aside for details).
3. After locks are released, a new RTC can begin. (If the Concurrent RTC setting is used, however, other RTCs can start at any time. See Table 14, Inference Agent and Query Agent Settings (Sheet 1 of 3) for details on this setting.)This property is used for specific needs. For one use, see Using CLIENT_ACKNOWLEDGE Mode with Websphere MQ and Cache-Aside in TIBCO BusinessEvents Developer’s Guide.Another use is to wait to send a reply event, saying some work has been done, until the result of the work can be seen in the cache. The prefetch feature improves performance, but CPU and memory usage increases as a result of the aggressive prefetching. You may have to try different values till you find the optimal settings for your environment.Default is false. Query agents that perform event stream processing only can be deployed in a standalone mode. Such agents do not use cache objects and do not require cache configuration properties.If true, specifies that the PU containing this query agent is a standalone PU and it does not use any cache features.(For more details see TIBCO BusinessEvents Query Developer’s Guide available with the TIBCO BusinessEvents Event Stream Processing add on product.)Default is false. XML event payloads are validated when this property is set to true. There may be some loss of performance due to the extra processing.Default is false. If set to true, the query agent attempts to use indexing that is enabled and defined as explained in the section Query Optimization, in TIBCO BusinessEvents Developer’s Guide. be.engine.cacheServer.channel.disable By default cache agents connect to channels. In most cases, however, cache agents do not need to connect to channels. To prevent cache agents from connecting to channels, set this property to true.
Copyright © TIBCO Software Inc. All Rights Reserved.