• New Feature
  • Status: In Progress
  • 3 Minor
  • Resolution:
  • Kit & Installation,X-System Administration
  • prodmgmt
  • Reporter: drb
  • November 30, 2006
  • 0
  • Watchers: 0
  • March 19, 2010


To facilitate minimizing scheduled downtime, support upgrading the application on the applications nodes (L1s) without stopping the cluster.

New Features:

* Similar to the "onLoad" BeanShell script, add an "onSet" method that can be called when fields are mutated.
* Create an "Open" mode for loading config files that allows the application node (L1) to be restated with a new and different config file. If reasonable, just rename "Development" mode to "Open" mode.
* Add capability to attach a version number to objects via a new "metadata" attribute in the "<include>" tag.

Customer Steps:

* Run Terracotta in "Open" mode.
* Identify new fields and fields whose type has changed in the new version of the application.
* For new fields, edit the existing config file to initialize the field value using custom BeanShell script off the "onLoad" method.
* For fields whose type has changed, edit the config file to handle upgrading and downgrading the field value using custom BeanShell script off the "onSet" method. Optionally, leverage the metadata information to track version number.
* Modify the existing config file to use custom BeanShell scripts in the "onSet" of fields where the data type has changed or other computation is required to convert old values to new values ...
* fields to new...