Deployment Using TIBCO Administrator or at the Command Line : Starting a TIBCO BusinessEvents Engine at the Command Line

Starting a TIBCO BusinessEvents Engine at the Command Line
When testing a project it can be helpful to run it at the command line. Here is the format to use (see Table 42, TIBCO BusinessEvents Command Line Engine Startup Options for details):

 
BE_HOME\be-engine [-h] [--propFile startup property file] [--propVar varName=value][-p custom property file] [-n engine name] [-d] [-c CDD file] [-u processing unit ID]  [EAR file]

 
 
When you execute be-engine, by default it looks in the working directory (the directory where you execute the command) for a property file of the same name (be-engine.tra). This property file provides startup values and other parameters to the executable.
For example, if you start the engine from a directory other than BE_HOME/bin, then you would generally use --propFile to specify BE_HOME/bin/be-engine.tra.
Used to provide a value for a specified global variable. This value overrides any other design-time value. The format is --propVar varName=value, for example, --propVar jmx_port=4567.
Allows you to pass one or more supplementary property files to be-engine. Specify the path and filename. Not often needed. See Supplementary Property Files.
The name provided here is used in the console and in log files. If you do not provide a name, the host name of the machine is used.
Specify the path and filename for the cluster deployment descriptor (CDD) file you want to use. TIBCO BusinessEvents looks first in the file system, and then in the EAR file.
The default is default.cdd.
If you don’t specify the EAR file name then the engine will use the property tibco.repourl as the EAR file path and name. To use this property, add it to the be-engine.tra file. If you deploy using TIBCO Administrator this property is added to the generated TRA file automatically.
Supplementary Property Files
Supplementary property files can be used in addition to be-engine.tra (or alternate file you specified using --propFile). See the -p option in Table 42 for basic information. This section provides more details.
In TIBCO BusinessEvents 4.0 and higher, property files are less likely to be needed, because only system level configuration is done in the TRA files. configuration formerly done in TRA files is now done using the Cluster Deployment Descriptor file.
Supplementary property files typically have a .cfg or .tra extension. Properties are defined as a list of name-value pairs (property=value).
Note: If a property name includes spaces, escape them using a back slash.
Order of Precedence
Values in supplementary property files override the values in the startup property file. Values provided at the command line override values in the supplementary property files.
If you specify multiple property files that include different values for the same parameters, TIBCO BusinessEvents uses the value in the left-most file in the command line. For example, consider this command line:
be-engine -p first.cfg -p second.cfg -p third.cfg
If second.cfg and third.cfg set different values for (as an example) tibco.clientVar.MyVar, and first.cfg does not include this parameter, TIBCO BusinessEvents uses the value in second.cfg. However, if first.cfg also includes a value for tibco.clientVar.MyVar, TIBCO BusinessEvents uses the value in first.cfg.