![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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).
If later you want to include any excluded entities, you must change the setting and update the backing store setup as explained in Updating an Existing Backing Store Schema in TIBCO BusinessEvents Developer’s GuideWhich 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 Chapter 28, Domain Objects Configuration in TIBCO BusinessEvents Developer’s Guide for the procedure.In TIBCO BusinessEvents Developer’s Guide, see Chapter 26, Backing Store Configuration, and JDBC Connection.
1.
2. In TIBCO BusinessEvents Studio Explorer, right click the project name and select Refactor > Rename. In the New Name field, type FraudDetectionStore and click Preview. You can preview the effect of this change, then click OK.
3. The provided FraudDetectionStore example project ships with this port, and its readme.html points to it as well (see Dependency Between Readme File and Project — Port Number for more details).
1. In TIBCO BusinessEvents Studio, open your project (if it is not already open), right-click the SharedResources folder and select New > Other > TIBCO Shared Resources > JDBC Connection (or select the folder and press Ctrl-N as in earlier tutorials).
2.
3. Optionally, enter a description such as JDBC Connection for the backing store tutorial.
4. In the JDBC Driver field, select the appropriate driver for your database. The tutorial example uses oracle.jdbc.OracleDriver. The database URL format appears in the Database URL field just below:Where 1521 is the default port, and XE is the default instance name for Oracle Database 10G Express. (The default instance name for Oracle Database 10g is ORCL.)
6. In the User Name and Password fields, type the name BE_USER and password BE_USER. (The password field does not display the text.). These are the username and password of the database user you will create (in Task E, Run the Initialize Database Script as the DBA or System User).Begin by renaming the CDD from the Cache OM Tutorial, and add a few configuration details for backing store functionality: click a checkbox to enable backing store functionality, and select the JDBC Connection resource you want to use. Of course, more options are available for different needs.
1. In TIBCO BusinessEvents Studio Explorer, right click the fdcache.cdd resource and select Refactor > Rename. In the New Name field, type fdstore and click Preview. You can preview the effect of this change, then click OK.
2. Open the newly renamed fdstore CDD file in the resource editor.
3.
Cluster Clashes If you have clashes with other clusters running on your machine, use a different cluster name, discovery URL and listen URL from the other cluster or clusters. See Chapter 3, Cache OM Tutorial > Task C, Add and Configure a CDD > step 4, on page 58 for details.
4. Select Cluster tab > Object Management > Backing Store
a. Select Persistence Option Shared All.
b. Select Database Type Oracle (or as needed for your DBMS).
5. Select Cluster > Object Management > Backing Store > Connection on the left and in the URI field, select the JDBC Connection shared resource you configured for the backing store (see Task C, Add a JDBC Connection Shared Resource).You can optionally check that the rest of the CDD configuration is correct. Refer to Task R, Add and Configure a CDD, in Chapter 4, Backing Store Tutorial.
6. Select Domain Objects > Default on the left.
− On the right, ensure that Mode is set to Cache Only (the default for the Cache CDD template).
−
9. In TIBCO BusinessEvents Studio Explorer, highlight the project name, then from the top menus select Project > Build Enterprise Archive.
a. Change the Name to FraudDetectionStore
c. At the end of the location string, change the file name to fdstore.ear. The FraudDetectionStore example ships with this value: BE_HOME/examples/standard/FraudDetectionStore/fdstore.ear.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |