Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 24 Cache OM and Cluster Configuration : Schema/Model Migration with Shared Nothing Persistence

Schema/Model Migration with Shared Nothing Persistence
You can choose one of these options:
1.
2.
The new field must be nullable as is the case for all user fields in BusinessEvents .
alter space name"dist-unlimited-bs-readOnly-Test--be_gen_Concepts_Simple" add (field name "long_field" type 'LONG' nullable true)
alter space name"dist-unlimited-bs-readOnly-Test--be_gen_Concepts_Simple" add (field name "con_cept_array" type 'BLOB' nullable true).
Then start the inference engines.
3.
Adding a concept property of type contained concept with the contained concept type set to an existing concept is supported only for optione 1. and 2.
4.
This option is available only in AS-2.1.2 release. Keep the existing unused fields as is, without assigning any values.
5.
Hot Deployment of New Properties
Hot deployment of new properties into existing TIBCO BusinessEvents concepts is available only in these cases:
To Enable hot deployment of new properties:
Before starting TIBCO BusinessEvents Studio, do the following:
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 in setting this functionality::
When enabling it 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.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved