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.
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:
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.