Values Used to Establish the Engine Name
When establishing the engine name, TIBCO BusinessEvents searches for a value, and accepts the first found value.
- For deployment using MM, the name specified in the Processing Unit Configuration Name field in the site topology file. See Site Topology.
- 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.
- 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.
- 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.
- The engine name set in the CDD file, in the Name field of the Processing Unit tab. See Agent and Processing Unit Configuration in TIBCO BusinessEvents Developer’s Guide.
- The name of the TIBCO Hawk microagent instance. This name exists if TIBCO Hawk is enabled at run time. The microagent name can also be set in the be-engine.tra file using the property Hawk.AMI.DisplayName.
- The host name.
- This string: engine.
Copyright © TIBCO Software Inc. All Rights Reserved.