Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Migrating Projects from Earlier Versions : Understanding the CDD File (For 3.x Users)

Understanding the CDD File (For 3.x Users)
Beginning with the 4.0.0 release, most runtime properties and other deploy-time settings are configured using a structured XML file called the Cluster Deployment Descriptor (CDD). A big advantage of this change is that you can change CDD file values at deploy-time without having to rebuild the EAR file (the CDD file used is stored outside the EAR file).
A multi-tab editor in TIBCO BusinessEvents Studio enables easy maintenance of this file. This section explains the role of the CDD file for the benefit of those migrating projects from 3.x.
The EAR file now includes all resources  In the current architecture, you don’t select what resources to include in the EAR file. The EAR includes all project resources and can be very large. During runtime however, the resources are enabled (filtered) through the CDD Agent Classes and Collections tabs.
Read this section before beginning your migration. Also read related topics in TIBCO BusinessEvents Architect’s Guide and TIBCO BusinessEvents Getting Started.
See Property Migration Reference for a list of 3.x runtime properties and their equivalent CDD settings or properties in the current version. Documentation about the CDD settings and properties is provided in the TIBCO BusinessEvents Administration guide.
Most Runtime Properties are Configured in the CDD File
3.x Configuration
In 3.x (and earlier), runtime properties were set using individual properties set in one or more TRA files. In some cases, runtime properties were set in TIBCO Designer, specifically in the BAR resource, and some were set in the TIBCO Designer TRA file.
5.0 Configuration
Now only JVM-level properties (those that need to be used before the engine starts up) are set in the be-engine.tra file. Properties that were set in the TIBCO Designer TRA file (designer.tra) are now generally set in the studio.tra file:
BE_HOME/studio/eclipse/configuration/studio.tra
Other runtime properties are configured in the CDD file. The CDD file provides fields for all commonly used settings, and it has property sheets where you can add other properties as needed. The property sheets are available at various levels, cluster, processing unit, and agent, so that you can scope the effect of the property appropriately and provide overrides at lower levels.
Processing Units (Engines) and Agent Classes are Configured in the CDD File
In the CDD, you configure processing units (equivalent to an engine at runtime). A processing unit references the agent or agents you want to include in the processing unit (engine) at runtime. At deploy time you specify which processing units to deploy.
In 3.x agents were configured using individual properties in the TRA files. Each TRA file provided the configuration for one engine.
Beginning with the 4.0.0 release, you configure all the processing units you need to deploy in a single CDD file. When you deploy an engine, you specify the processing unit to use. The processing unit configuration in the CDD determines which project resources and settings are used at runtime.
Some agents and processing units are created for you when you import a 3.x project into Studio based on 3.x information available. After you import the project into TIBCO BusinessEvents Studio, edit the CDD file to fully configure the agents and processing units as needed.
Metadata Properties (Extended Properties) are Configured in the CDD File
The entity metadata properties (also known as extended properties) for cache and backing store are now configured in the CDD. Preloading configuration has also been simplified. This is explained in the migration sections.

Copyright © TIBCO Software Inc. All Rights Reserved