Upgrading from Version 2.x—Cache Object ManagementIt is strongly recommended that you read relevant sections of the TIBCO BusinessEvents User’s Guide documentation to understand the new object management options and reconfigure your projects accordingly. The main items that require reconfiguration are presented in this migration guide. However, some impacts of configuration changes may not be not documented here.
● Caching and backing store tutorials in TIBCO BusinessEvents Getting Started.
● All object management options documented in TIBCO BusinessEvents User’s Guide, beginning with Chapter 14, Understanding Object Management and Fault Tolerance.Note that cluster discovery configuration has not changed and does not require migration. However caching scheme configuration has changed.In 3.x all caching schemes supported out of the box are distributed caching schemes. The best options for most use cases have been determined and much of the need for custom configuration has been removed.In 2.x you chose the caching scheme using a Cache Name setting in the BAR resource Configuration tab (the field does not exist in 3.x).To determine how many storage-enabled nodes start before data is loaded from a backing store, and before agents become fully active: be.engine.cluster.minCacheServersSee Configuring Caching Scheme, Multi-Engine, and Cluster Properties in TIBCO BusinessEvents User’s Guide.Improvements to caching schemes used in 3.x mean that customizing the cache configuration file is generally not required.If you used a customized coherence-cache-config.xml file contact TIBCO to determine how to implement the same functionality in the current version.To deploy any EAR file that contains at least one BAR resource engine as a cache server, set one engine property:In BusinessEvents 2.x, one engine has the role of cache loader. The cache loader was a cache server with an extra job: it loads the objects from the backing store database to the cache at startup.In BusinessEvents 3.x, any node can take on the role of cache loader at startup and you do not configure one engine to act as the cache loader. Before cache loading begins, a specified number of cache servers and other storage-enabled nodes must be started to hold the data which must be loaded from the backing store.With Cache OM, inference agents can be deployed in multi-engine mode to achieve load balancing and ruleset chaining between agents in an agent group.
Carefully read all related content in TIBCO BusinessEvents User’s Guide. You may need to make some changes to the design of your project to account for concurrently active agents. See Designing With Multiple Active Inference Agents in TIBCO BusinessEvents User’s Guide.From version 3.0 and higher, BusinessEvents BAR resources deploy as inference agents, by default. With Cache OM, you must configure agent settings as follows.(A new Type field on the BAR resource Configuration tab lets you deploy a BAR as a query agent or an inference agent. Inference agent is the default value. Query agents, available in BusinessEvents Enterprise Suite only, and used only with Cache OM, are new in 3.x and so they won’t pose any migration issues.)Agent Groups An agent group created when you deploy the same EAR, containing one or more inference agent BAR files, more than one time. Each instance of an agent in each JVM forms an agent group. Many agent-levels settings require you to specify the agent group name.
1. Open the project in TIBCO Designer and in the BAR resource Configuration tab, enter a name for the inference agent group. It is recommended that you use BAR resource name as agent group name.
2. in each node’s TRA file, uniquely identify each agent in a group using the following property (required for recovery of scorecards).If you use Cache OM, you must reconfigure fault tolerance when you configure the inference agents.Fault tolerance in 3.x is set at the inference agent level. Fault tolerance is provided between agents in an agent group.
1. Remove the following properties from your engine properties files (be-engine.tra files or supplementary files you use to set engine properties):
2. If you are using multi-engine mode, configure the following property to the same value in all nodes:If you deploy more agents in a group than the maxActive number, those agents are deployed in inactive mode.
3. For both multi-engine and single-engine modes, configure the following property using a different value in each node:Priority determines which agents start up first and therefore which agents remain inactive. Smaller numbers indicate higher priorities (one is the highest priority).Each instance of an agent deploys in a different node (engine). Therefore set the priority as needed in each engine’s property file to determine failover and failback behavior. Remember to configure the settings for each agent group, if an EAR file contains more than one BAR.
Copyright © TIBCO Software Inc. All Rights Reserved.