Cache Provider Selection (Cache OM only)
Beginning with TIBCO BusinessEvents 5.0.0, Oracle Coherence is no longer provided with TIBCO BusinessEvents. An internal component, TIBCO BusinessEvents DataGrid, is used by default.
See Migrating from Coherence to TIBCO BusinessEvents DataGrid Cache Provider for important information about migration of Coherence functions. If you use cache OM, action is required:
- If you want to switch from Oracle Coherence to TIBCO BusinessEvents DataGrid, you must manually reconfigure the CDD file settings. See TIBCO BusinessEvents Configuration Guide for details.
- If you want to continue using Oracle Coherence as the cache provider, you must acquire a licensed copy of Oracle Coherence software and do some configuration. See TIBCO BusinessEvents Configuration Guide for details on enabling use of Oracle Coherence as the cache provider.
- The property tangosol.coherence.distributed.localstorage is migrated automatically to the cache-provider-neutral property be.engine.cluster.isSeeder. However, a change in design makes this property redundant. Cache storage is now set at the processing unit level, using a checkbox labeled Enable Cache Storage. It is not possible to set this checkbox at migration time. To complete migration, remove the isSeeder property and instead configure cache storage for non-cache agents as needed use the processing unit setting Enable Cache Storage in the project CDD file. Note that enabling cache storage on non-cache agents is not recommended for production. It can be useful for testing and demonstration purposes.
Related concepts
Related tasks
Copyright © Cloud Software Group, Inc. All rights reserved.