Other Deployment Tasks
You might need to perform additional tasks while deploying a project with TIBCO Administrator.
Set default or specific CDD file and processing unit names
If you want to let the target engines find the CDD at a default location, name the CDD file
default.cdd
and keep it in the root of the project folder. If you want to let the target engines choose a processing unit by default, then, in the 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 "Agent and Processing Unit Configuration" in TIBCO BusinessEvents Developer’s Guide.
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" check box in the Build Enterprise Archive dialog is selected. Select as needed.
Then build the EAR. See Building an Enterprise Archive (EAR File). See Enterprise Archive (EAR) Files for details.
Set stack size to 264K on HP-UX Itanium
The default stack size is not sufficient to create the Java Virtual Machine and start the engine on HP-UX Itanium. Edit the be-engine.tra file and set the stack size to 264K:
java.thread.stack.size=264K