This section explains where various runtime items are located, and how the engine name is determined at runtime.Determining the Engine (Node) NameWhen establishing the engine name, BusinessEvents software searches for a value from one of the settings in the order shown, accepting the first value it finds:
1. API setting. If BusinessEvents is started using the public API, and a non-null instance name is provided when getting the RuleServiceProvider with RuleServiceProviderManager.newProvider(String instanceName, Properties env)—this takes precedence over all other name settings.
2. The engine name set at the command line using the -name option. An engine name set at the command line overrides the engine name property set in the be-engine.tra or supplementary property file (see next).
3. the engine name set by the be.engine.name property. This property can be set in the usual ways:
− For command-line startup it can be set in the be-engine.tra file or in a supplementary property file.
−
4. The name of the TIBCO Hawk microagent instance. This name exists if TIBCO Hawk is enabled at runtime. The microagent name can also be set in the be-engine.tra file using the property Hawk.AMI.DisplayName.
6. This string: engine.When applications are started outside of a TIBCO Administrator domain, the TIBCO repo URL is the file location of the project EAR file. You add a property to the engine property file, be-engine.tra to specify the location:tibco.repourl location of EAR fileWhen TIBCO Administrator is used to deploy a BusinessEvents application, the tibco.repourl property is added to the generated TRA file (see Location of TIBCO Administrator-Generated Property File).The value of this property is the URL of the project repository. The URL format depends on the deployment transport used. Supported formats for the URL are tibcr, http, https, and file (local).You can use a tibcr:// URI to identify the server-based repository location. For full details about its allowable parameters, refer to TIBCO Adapter SDK™ documentation.
One way to determine the repo URL is to temporarily deploy the BusinessEvents EAR. The repo URL is in the deployed BusinessEvents instance TRA file. However, you must remove the escape characters (back-slashes). You must then undeploy the BusinessEvents instance after obtaining the tibco.repourl value.When it deploys a BusinessEvents project, TIBCO Administrator reads the properties from the engine property file located in BE_HOME/bin/be-engine.tra and then incorporates the deploytime configuration values set in the TIBCO Administrator user interface. (Property values set in TIBCO Administrator override those set in the BE_HOME/bin/be-engine.tra file).The working directory and various file locations depend on the method of deployment: startup at the command line, or deployment using TIBCO Administrator.Path names that do not start with the root directory are assumed by the operating system to start from the working directory.Also see BE Working Directory (and Log File Location) for a note about how working directory is determined when you use BusinessEvents Tools
TIBCO Administrator Deployment BE_HOME/bin/be-engine.tra Directory in which you start the be-engine.exe executable Where TIBCO_DOMAIN_HOME is the location configured when creating the administration domain. For example, c:/tibco/tra/domain/Acme/application/logsUse Engine.Log.Dir to change the log file directory. Use Engine.Log.Dir to change the log file directory Database Environment Directory (for Persistence object management) designer_home/bin/logs
Copyright © TIBCO Software Inc. All Rights Reserved.