Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 23 Cluster Deployment Descriptor (CDD) : How CDD Settings Apply at Runtime

How CDD Settings Apply at Runtime
It’s 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. The order of precedence is explained in the section, Order of Precedence at Runtime.
Order of Precedence at Runtime
This section also appears in TIBCO Administrator and is reproduced here for your information, because order of precedence at run time can affect decisions made at design time.
The order of precedence at run time, from highest priority to lowest, is as follows:
1.
2.
3.
4.
a.
b.
5.
a.
b.
6.
a.
b.
c.
EAR file properties (such as global variable overrides)
 
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved