Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 CDD Configuration Procedures : Overview of CDD Configuration

Overview of CDD Configuration
TIBCO BusinessEvents Express  Content relating to Cache OM and backing store does not apply to TIBCO BusinessEvents Express edition.
This chapter explains how to configure deployment settings for a TIBCO BusinessEvents cluster. Configuration is done using the Cluster Deployment Descriptor (CDD) editor. Settings are saved to the CDD file in XML.
This chapter assumes you have read and understood the object management and other deploy-time configuration topics in TIBCO BusinessEvents Architect’s Guide, especially Chapter 6, Object Management Types and Chapter 7, Distributed Cache OM.
Basic settings for all object management (OM) types relate to the following:
For deployment using the TIBCO BusinessEvents Monitoring and Management component, processing units configured in the CDD editor are referenced in the Site Topology editor, where they are associated with physical resources. See Site Topology Overview and sections following for details.
Selecting a Cache Provider (for Cache OM)
When you configure Cache OM, you must first choose a cache provider: TIBCO or Oracle. The internal TIBCO cache provider, TIBCO BusinessEvents DataGrid, is the default choice. You can use Oracle Coherence if you own your own license for it. Additional configuration is required. See Enabling Use of Oracle Coherence as the Cache Provider for details.
Using Properties at Different Levels
The scope of a property depends on the property sheet you add it to. Not all properties are valid at all levels. Use your judgment.
For example, properties that include the agent class name, such as Agent.AgentClassName.checkDuplicates, can be used this way. Here is the scope of each level for the AgentClassName properties:
Cluster level  Applies to all AgentClassName agents in the cluster.
Processing unit level  Applies to any AgentClassName agent deployed in the specified processing unit.
Agent class level  Applies to any AgentClassName agent, used in any processing unit.
(Not all agent-level properties include the agent class in the property name.)
Only one value for a property can be used when a processing unit is deployed. The order of precedence is explained in the section, Order of Precedence at Runtime.

Copyright © TIBCO Software Inc. All Rights Reserved