Resolution:
Description:
============
Configuring Hot Deployment in TIBCO BusinessEvents (BE) when deployed through TIBCO Administrator.

Environment:
==========
Operating system: All
TIBCO BusinessEvents (BE) version: All

Resolution:
==========
In order for Hot deployment to work for BE engines deployed to TIBCO Administrator, make sure hotdeploy is enabled for the inference engine in the Cluster Deployment Descriptor(CDD) file and comment the property 'be.engine.hotDeploy.enabled' in be-engine.tra (under &ltBE_HOME>/bin).

You can confirm Hot deployment is working by examining the inference engine log files when redeployment is done.

2011 Aug 19 16:42:17:046 GMT -7 TestVRF-TestVRF Info [HotDeployPoller] - [runtime.session] Project reloaded from location: C:/tibco/tra/domain/Admin57/datafiles/TestVRF_root
2011 Aug 19 16:42:17:046 GMT -7 TestVRF-TestVRF Info [HotDeployPoller] - [runtime.session] Analyzing project...
2011 Aug 19 16:42:17:062 GMT -7 TestVRF-TestVRF Info [HotDeployPoller] - [runtime.session] Hotdeploy applying...
2011 Aug 19 16:42:17:062 GMT -7 TestVRF-TestVRF Info [HotDeployPoller] - [runtime.session] Hotdeploy applied.
2011 Aug 19 16:42:17:062 GMT -7 TestVRF-TestVRF Info [HotDeployPoller] - [runtime.session] Resuming all threads...
2011 Aug 19 16:42:17:062 GMT -7 TestVRF-TestVRF Info [HotDeployPoller] - [runtime.session] Acquired Lock, signal all threads
2011 Aug 19 16:42:17:062 GMT -7 TestVRF-TestVRF Info [inference-class-eventQueueListener] - [runtime.service] Resuming thread: inference-class-eventQueueListener

Note: When Hot deployment is done, the engine shows the text 'out-of-sync' next to Running status. This is because the Hot deployment feature is applicable only for BE.  Administrator is unaware of this feature.

Configuring Hot Deployment in TIBCO BusinessEvents when deployed through TIBCO Administrator.