Configure Runtime Properties in the CDD File

Most of the configuration that was done in TRA files is now done in the CDD file. Ensure that all valid 3.x runtime settings (except JVM and system level properties) are configured in the CDD. Some properties are not relevant in the current version, and additional properties not used in 3.x have been added to the product. You may have to add some properties manually to CDD property sheets.

Here are some tips:

Procedure

  1. Add runtime engine properties to the CDD file at the appropriate level for the scope of the property:
    • Cluster level for cluster-wide scope.
    • Processing Unit level for engine-wide scope in the specified type of engine (Processing Unit). You will have to think about your engines differently, as running different kinds of agent classes.
    • Agent level to limit the scope to the agent class.
  2. TIBCO BusinessEvents properties that were configured in the TIBCO Designer TRA file generally go in the TIBCO BusinessEvents Studio TRA file:

    BE_HOME/studio/eclipse/configuration/studio.tra

  3. Remove the runtime properties that are now configured elsewhere from the TRA file and ensure that only JVM or system level properties remain. Leaving these properties in the TRA can cause problems at runtime.

Result

See CDD File Overview (For 3.x Users) for background information that helps you work with the CDD file.