Before configuring and starting a TIBCO BusinessEvents application, you configure an enterprise archive resource (EAR) file for your BusinessEvents project within TIBCO Designer.This section gives a general procedure for configuring deploytime properties for command-line startup. See Configuring to Run in a TIBCO Administrator Domain for the equivalent procedure if you want to configure for deployment using TIBCO Administrator.Use of Supplementary Property FilesIf you will start the BusinessEvents application at the command-line, you can configure various settings in the be-engine.tra property file, in supplementary configuration files, or both. How you distribute the properties between the main property file and supplementary ones depends on your needs.For example, you might configure properties for a cache server in one property file, and properties for a regular BusinessEvents engine in another. When you start the server (and run the application), you would specify the appropriate supplementary configuration file, as explained in Deploying a Project Outside a TIBCO Administrator Domain.
The values of properties specified in the supplementary file override values for same-named properties set in the be-engine.tra file.
− Open the be-engine.tra file for editing.
− Open a supplementary property file for editing. You can use supplementary files to configure sets of options for different needs as explained in the section introduction.
2. Set properties and values as explained in the relevant section of this chapter and elsewhere in the guide. See Deploytime Configuration Overview for a summary and references to related information. Also see Table 36, Command-line Engine Startup Options for a list of available properties.
If a property name includes spaces, escape them using a back slash. For example, be.engine.om.berkeleydb.cacheweight.My\ Rulesession.
3. Optionally, specify startup options in the property file, instead of at the command line. Use the tibco.env.APP_ARGS global variable using the following format:tibco.env.APP_ARGS [--propFile startup_property_file] [-p propertiy_file] [-n engine_name] [earfilename]See Deploying a Project Outside a TIBCO Administrator Domain for the deployment procedure.
Copyright © TIBCO Software Inc. All Rights Reserved.