Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Other Deployment Tasks

You might need to perform additional tasks while deploying a project with the TIBCO Administrator.

## Set default or specific CDD file and processing unit names

If you want to let the target engines find the CDD at a default location, name the CDD file `default.cdd` and keep it in the root of the project folder. If you want to let the target engines choose a processing unit by default, then in the CDD file, name one of the processing units `default`. When you deploy, the processing unit named `default` starts. Note that these names are case-sensitive.

You can also specify different CDD file and processing unit values at deploy time.

## Enable hot deployment, as needed

If you want to be able to hot deploy changes to the running engine, open the CDD file in the TIBCO BusinessEvents Studio project, select the processing unit or units you will deploy, and check the Hot Deploy checkbox. See "Agent and Processing Unit Configuration" in theTIBCO BusinessEvents Developer Guide.

## Enable service-settable global variable overrides and build the EAR

Service settable global variables are only available if the "Include All Service Level global variables" checkbox in the Build Enterprise Archive dialog is selected. Select as needed.

Then build the EAR. See Building an Enterprise Archive (EAR File). See Enterprise Archive (EAR) Files for details.

## Enable custom log configurations

To use custom log4j logconfiguration for a project through teagent, do the following settings:

- Add a custom property

  Add the property `log4j2.configurationFile` for a project. For a detailed process, see Adding a New BusinessEvents Property.

- Add a custom log configuration file to the engine classpath

  On the Machine Management page, by using the Upload External Artifacts wizard, upload your log configuration XML file to the selected BE_HOME. For a detailed process, see Uploading External Artifacts .

  Note: Keep a different name for your custom log configuration file from the default `log4j2.xml` file name.

- Disable CDD Log Configurations

  To disable the CDD Log Configurations, open the CDD file for the project in the TIBCO BusinessEvents Studio and uncheck the Enable option in the Log Configurations.

  This setting makes TIBCO BusinessEvents use your custom log configuration XML file from the engine classpath instead of the CDD configurations.

  For a detailed process, see Configuring Log Configurations.

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.