Cluster Deployment Descriptor (CDD)
Object management is configured using the Cluster Deployment Descriptor (CDD), an XML file that you edit in TIBCO BusinessEvents Studio using a provided editor.
One EAR file and one CDD file define all the settings for all the engines and agents you want to deploy for a single application.
Because the deploy-time configuration settings for all processing units are in the CDD file, you do not have to rebuild the EAR file to make changes to deploy-time settings. However, as desired, you can use only the copy of the CDD file that is in the EAR, for tighter control and uniformity.
When you deploy a processing unit, you specify these items:
- An EAR file
- A CDD file that you have configured for that EAR
- A processing unit (engine) that is configured in the specified CDD file.
The CDD file you specify can be in the file system or in the EAR file. To specify a CDD located in an EAR file, provide its project path and name.
You can configure multiple CDD files for a project for different purposes such as testing a design, trying out different object management options, dividing the work differently between agents and processing units (engines), and so on. However you use the same CDD file when deploying all the processing units for an application.
CDD Settings at Runtime
It is important to understand the effect of design-time settings in the runtime environment. The tab and section within a tab where you set values in the CDD can affect the scope of those values, and how they can be overridden.
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 at different levels. Here is the scope of each level for these 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 is used when a processing unit is deployed.
Order of precedence at runtime can affect decisions made at design time. This is discussed and explained in the documentation for TIBCO Administrator.