When testing a project it can be helpful to run it at the command line. Here is the format to use (see Table 36, 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.You can specify the path and filename of a startup property file explicitly using the --propFile parameter.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, --propFile jmx_port=4567. Allows you to pass one or more supplementary property files to be-engine. Specify the path and filename.Supplementary property files can be used in addition to be-engine.tra (or alternate file you specified using --propFile).Supplementary property files typically have a .cfg or .tra extension. Properties are defined as a list of name-value pairs (property=value).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, BusinessEvents uses the value in the left-most file in the command line. For example, consider this command line:If second.cfg and third.cfg set different values for (as an example) tibco.clientVar.BUILDEAR, and first.cfg does not include this parameter, BusinessEvents uses the value in second.cfg. However, if first.cfg also includes a value for tibco.clientVar.BUILDEAR, BusinessEvents uses the value in first.cfg.Note: If a property name includes spaces, escape them using a back slash. 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.The default is default.cdd. Specify the processing unit ID you want to use for this engine. This ID must exist in the CDD file you reference in the -c option.The default is default.
Copyright © TIBCO Software Inc. All Rights Reserved.