Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Cluster Deployment Descriptor Reference : Agent Classes Tab Settings and Properties

Agent Classes Tab Settings and Properties
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.
 
Enter a name that is unique across the cluster. Use the NSName standard as in all names in the CDD.
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.
Inference and Query Agent Settings
 
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.
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.
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.
Inference, Query, and Cache Agent Properties
Agent.AgentClassName.recoveryPageSize
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.
Agent.AgentClassName.cacheTxn.updateCache
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.
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.
See Cluster Tab — Cache OM — Domain Objects Settings for details on the Evict From Cache on Update setting.
Agent.AgentClassName.checkDuplicates
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
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).
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.
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.
(For more details see TIBCO BusinessEvents Query Developer’s Guide available with the TIBCO BusinessEvents Event Stream Processing add on product.)
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