Deploytime configuration settings affect the behavior of the deployed nodes and agents. Deploytime settings can apply at the agent level, node level, or at a higher level such as that of a cache cluster.
Some deploytime configuration is done in TIBCO Designer, when you configure the EAR and BAR resources, for example, choosing which rule sets to deploy.
An EAR file deploys as one BusinessEvents node. A node can contain one or more inference agents, or one or more query agents, or both, or it can be deployed as a cache server. You can deploy one ear multiple times with different (or the same) deploytime settings.
The methods you use for configuring your projects and managing the deployed applications depend on whether the application is deployed to a TIBCO Administrator domain or not.
TIBCO BusinessEvents includes a command-line utility for starting and stopping BusinessEvents servers and setting deploytime properties. The properties are set in the engine property file (
be-engine.tra) and (optionally) supplementary property files. These files are used by the command-line utility.
All properties that are set in the engine property file can be added to the Advanced tab for the merged BAR file, which appears as a single service within the application when viewed in the TIBCO Administrator user interface. See
Customizing the List of Properties on the Advanced Tab for the procedure.
You can also use global variables in your project, and set their values at deploy time. All global variables set in a project automatically appear in the Advanced tab of the application in the TIBCO Administrator user interface. See
Defining and Using Global Variables.