Copyright © TIBCO Software Inc. All Rights Reserved |
Determining the Engine NameWhen establishing the engine name, TIBCO BusinessEvents software searches for a value from one of the settings in the order shown, accepting the first value it finds:
1. For deployment using MM, the name specified in the Processing Unit Configuration Name field in the site topology file. See Site Topology Reference.
2. API setting. If TIBCO 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.
3. 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 CDD file or be-engine.tra or supplementary property file.
4. The engine name set by the be.engine.name property in the TRA file. For command-line startup it can be set in a supplementary property file.
6. 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.
8. This string: engine.
Copyright © TIBCO Software Inc. All Rights Reserved |