Deployment Using TIBCO Administrator or at the Command Line : Before Deploying a Project in a TIBCO Administrator Domain

Before Deploying a Project in a TIBCO Administrator Domain
You must update the be-engine.tra files to include the TIBCO Hawk information. You must build the EAR file. Do other tasks as needed.
Update Engine TRA Files for TIBCO Hawk Information
Update the be-engine.tra files on all machines where you will deploy TIBCO BusinessEvents engines as follows.
1.
Open the BE_HOME/bin/be-engine.tra file for editing.
2.
Set the value of tibco.env.HAWK_HOME.
3.
   %PSP%%HAWK_HOME%/lib%PSP%
4.
   %PSP%%HAWK_HOME%/bin%PSP%
5.
Set Default or Specific CDD File and Processing Unit Names
If you want to use default values, name the CDD file default.cdd and keep it in the root of the project folder. In that CDD file, name one of the processing units default. When you deploy, the processing unit named default will start. Note that these names are case sensitive.
You can also specify different CDD file and processing unit values at deploy time.
Enable Hot Deployment, as needed.
If you want to be able to hot deploy changes to the running engine, open the CDD file in the TIBCO BusinessEvents Studio project, select the processing unit or units you will deploy, and check the Hot Deploy check box. See Configuring the Processing Units Tab (All OM Types).
Enable Service-Settable Global Variable Overrides and Build the EAR
Service settable global variables are only available if the "Include All Service Level global variables" checkbox in the Build Enterprise Archive dialog is checked. Then build the EAR. See Building an Enterprise Archive (EAR File) in TIBCO BusinessEvents Developer’s Guide for details.