Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 CDD Configuration Procedures : Configuring a Cache OM Cluster — Cluster Tab

Configuring a Cache OM Cluster — Cluster Tab
TIBCO BusinessEvents Express  This section relates to Cache OM functionality and does not apply to TIBCO BusinessEvents Express edition.
Use this procedure if you picked Cache OM in the second page of the New Cluster Configuration wizard.
This is a detailed area of configuration. The procedure guides you at a high level. For details on settings and properties, see the referenced tables shown in Chapter 4, Cluster Deployment Descriptor Reference, and see other referenced sections for actions that require more explanation.
To Configure the Cluster Tab for Cache OM
For the preceding (wizard) procedure, see Adding a Cluster Deployment Descriptor.
1.
In the Cluster tab, click General. On the right, specify settings as shown in Cluster Tab — General Settings.
For deployment with TIBCO Administrator  The message encoding specified in the CDD file General settings must match the TIBCO Administrator domain’s message encoding.
2.
The Object Management element should look like this: Object Management: [Cache], indicating that Cache OM is selected. If Cache OM is not already selected, right-click the Object Management element and select Change to Cache. Or close the editor and begin again. Use the wizard to select OM type.
Cluster Discovery
3.
Add properties as needed for cluster discovery. Depending on your situation, you can use defaults and it may not be necessary to add properties:
If the cache provider is TIBCO BusinessEvents DataGrid, and you need to use non-default values, add the following two properties:
be.engine.cluster.as.discover.url
be.engine.cluster.as.listen.url
The properties can be omitted if you use multicast with default values. See Configuring a TIBCO BusinessEvents DataGrid Cluster for all the options.
Backing Store
4.
Click Backing Store in the tree on the left and complete the fields on the right. See Cluster Tab — Cache OM — Backing Store Settings for details.
Click Backing Store > Connection and complete the fields on the right to reference the JDBC connection for the backing store, and the pool settings. See Cluster Tab — Cache OM — Backing Store Settings for details.
Domain Objects
5.
Click Domain Objects > Default and specify the default object management settings for domain objects (entity instances). see Table 7, Cluster Tab — Cache OM — Domain Object Default Settings for details on all the settings.
Preload and limited cache settings are used with a backing store. The settings are applied at the object level. For example, a contained concept can have a different limited cache setting from its container concept, and could be evicted from the cache at a different time.
Default settings can be overridden at the entity type level. For example, when a cache is configured for the cluster, but only objects of a few entity types need to be persisted in the cache, you would set the default mode to Memory Only, and set domain object overrides for selected entities to Cache Only. Similarly you can choose which entity types to persist in the backing store.
If a backing store is already set up, and you enable any Use Backing Store settings, you must update the backing store setup. The backing store will not operate correctly unless you do so. See Updating an Existing Backing Store Schema.
6.
As desired, add domain object override entries. Any entity types not overridden use the Default level mode and related settings.
When a project is migrated from 4.x to 5.0, domain object override entries are automatically added for all entities. See Migration from 4.x to 5.0 — Automatic Migration Changes in TIBCO BusinessEvents Installation for details.
a.
In the tree on the left, click Overrides and click Add. Select the entity or entities you want to override and click OK.
b.
In the tree on the left, select the /uri entry for each selected entity in turn, and configure the settings on the right. You can use the defaults set in step 5, or override them. You can also edit existing override entries, and remove entries not needed (by clicking Remove).
c.
If any domain objects use Cache+Memory, also set the Subscription Preprocessor setting and the Subscribe Cluster setting as needed, using the Overrides.
See Table 8, Cluster Tab — Cache OM — Domain Object Override Settings (Sheet 1 of 4) for override settings.
Database Concepts
7.
If you use database concepts, available in the TIBCO BusinessEvents Data Modeling add-on product, select Database Concepts on the left and complete the fields in the configuration section on the right. See TIBCO BusinessEvents Data Modeling Developer’s Guide for details.
Other Properties
8.
Go to Configuring the Collections Tab (All OM Types) to continue configuration.

Copyright © TIBCO Software Inc. All Rights Reserved