TIBCO BusinessEvents Studio Project
Except for excluding entities from the backing store, modifying of the Fraud Detection Cache project to support a backing store can be configured before or after setting up the backing store, and can be changed after the backing store is in place.
- Can I exclude entities from the backing store?
- Yes. You can configure various settings at the individual entity type level. To exclude entities, use the CDD Cluster tab > Object Management > Domain Objects > Overrides feature. Uncheck an entity override’s Has Backing Store checkbox to exclude it from the backing store. See Excluding Entities from the Backing Store in TIBCO BusinessEvents Developer’s Guide for more details (including another way to exclude entities, using their Mode setting).
- Which database connection pool strategy to use, JDBC or Oracle?
- If you use Oracle Database, you have the option of using either the TIBCO BusinessEvents internal pooling implementation, or Oracle Database’s implementation. Various pooling settings are interpreted differently depending on what strategy you choose. You can also not enforce pools, in which case all connection pool settings are ignored.
- Which database write strategy to use, cache-aside or write-behind?
- You can choose how data is written to the backing store. With cache-aside strategy (the default), writes to the database and cache are made simultaneously. With write behind, writes to the cache are done first, and then the cache manager writes to the database. To understand these choices in more detail, see Post-RTC and Epilog Handling and Tuning Options in the TIBCO BusinessEvents Architect’s Guide Threading Models and Tuning chapter.
- What is preloading?
- When you use a backing store, you can preload entity data from the backing store to the cache before the system begins processing events. If you do not preload entities, they are fetched from the backing store as required at runtime (which means the first time objects are fetched is slower).
- Why preload handles?
- Entity object handles are stored in a special cache that can be preloaded or not depending on storage and performance needs. It might be more efficient in some cases to preload handles and not objects, for example. See The Role of the Object Table in TIBCO BusinessEvents Architect’s Guide for more details.
Preloading commonly used objects can improve performance after startup. By default, no preloading is done. You can preload all objects or objects of selected entity types, as desired. See Domain Objects Configuration in TIBCO BusinessEvents Developer’s Guide for the procedure.
Copyright © TIBCO Software Inc. All Rights Reserved.