Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Values Used to Establish the Engine Name

When establishing the engine name, TIBCO BusinessEvents searches for a value, and accepts the first found value.

- 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 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`.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.