To run an engine outside of a TIBCO Administrator domain, you start the engine at the command line. Before starting the server and running a TIBCO BusinessEvents engine at the command line, you configure an enterprise archive resource (EAR) file for your BusinessEvents project within TIBCO Designer, and, as needed, you configure deploytime properties.Read Chapter 26, Deploytime Configuration to understand the deploytime configuration tasks. See Configuring to Run Outside of a TIBCO Administrator Domain for the procedure. Also see Chapter 15, Configuring In Memory Object Management for information about fault tolerance as used for In Memory object management.For information about deploying a BusinessEvents project using TIBCO Administrator, see Deploying a Project in a TIBCO Administrator Domain.A simple command-line interface allows you to start the BusinessEvents engine and run the application specified in a project EAR file, with some startup options.Optionally, you can provide startup options in the be-engine.tra file itself (or a supplementary property file). Putting the options in the property file allows you to start the engine using the simple command with no arguments.
1. Open a command window and navigate to the location of the be-engine executable file. It is generally in BE_HOME\bin, for example: c:/tibco/be/3.0/bin.
Alternatively, you can specify the startup properties in the be-engine.tra file itself using a line of the same format:tibco.env.APP_ARGS [--propFile startup_property_file] [-p propertiy_file] [-n engine_name] [earfilename]See Command-line Engine Startup Options for details on using the options.
Using property file: C:\tibco\be\version\bin\be-engine.tra
You also see project initialization messages. When the engine starts you see a message like: Engine engine_name started.Table 36, Command-line Engine Startup Options, provides detailed information about the options.
Table 36 Command-line Engine Startup Options When you execute be-engine, by default it looks in the working directory 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 a different startup property file using the --propFile parameter.See Default Location of Log Files and Other Files and Directories for more on how working directory is determined. -p path_to_properties_file Allows you to pass one or more supplementary property files to be-engine. 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.tra and third.tra set different values for (for example) tibco.clientVar.BUILDEAR, and first.tra does not include this parameter, BusinessEvents uses the value in second.tra. However, if first.tra also includes a value for tibco.clientVar.BUILDEAR, BusinessEvents uses the value in first.tra. -n engine_name
Copyright © TIBCO Software Inc. All Rights Reserved.