CDD File Overview (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 do not 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.
- Most Runtime Properties are Configured in the CDD File
- 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.
Related concepts
Copyright © Cloud Software Group, Inc. All rights reserved.