Products | Versions |
---|---|
TIBCO BusinessEvents Enterprise Edition | - |
Not Applicable | - |
Description:
Description:
============
TIBCO BusinessEvents 5.1.1 hotfix01 enabled the hot deployment of new properties into existing TIBCO BusinessEvents concepts. In addition to the information provided in the hotfix readme, note the updated list of limitations when using this functionality:
Environment:
==========
o TIBCO BusinessEvents 5.1.1 hotfix 01 and above
Resolution:
===========
Please see the updated list of limitations when using this functionality.
1. Projects with state machines, database concepts, or views will not build in Studio when the property com.tibco.be.hotdeploy.concept is set to true.
2. When enabling this functionality with no backing store, ensure that the property “be.engine.cluster.as.tuple.explicit = true” is set in the CDD file. This property is set to true by default when using shared nothing persistence.
3. Adding a concept property of type contained concept with the contained concept type set to an existing concept is not supported.
4. While adding or removing concept properties is allowed, updating an existing concept property is not supported. For example, modifying the datatype of a concept property from int to long is not supported.
References:
==========
For your reference, here is the defect description from the hotfix readme.
BE-17971
This hot fix enables the hot deployment of new properties into existing TIBCO
BusinessEvents concepts. This functionality is only available when:
- Cache Object Management is enabled with no persistence or Shared Nothing
persistence.
- The concepts with new properties are cache-only.
To enable this functionality:
Before starting TIBCO BusinessEvents Studio to build the EAR file:
1. Add the following line to the vmargs in the studio.ini file:
-Dcom.tibco.be.hotdeploy.concept=true
2. Set the property com.tibco.be.hotdeploy.concept=true in the CDD file.
Note the following restrictions:
- When enabling this functionality with no backing store, ensure that the
property be.engine.cluster.as.tuple.explicit=true is set in the CDD file.
This property is set to true by default when using shared nothing persistence.
- Adding a concept property of type contained concept with the contained
concept type set to an existing concept is not supported.
Symptoms:
Cause: