Unsupported changes in a model

Unsupported changes in the current deployed business measures model will result in requiring a new model (accomplished by changing the name of the model project). The Schema Generator will consider this model as a new model because it is named completely different from the deployed business measures model, therefore it will not validate any changes made between versions.

The unsupported changes in the model change the structure of the databases, process model, or activities. In this case, the deployment will be as a different model. For more information about the unsupported changes, refer to change management artifacts generation in database services section.

The different model deployment scenario is similar to the first-time deployment scenario, but unlike that scenario where the databases are empty and populated for the first time, in this scenario, the databases are populated with previously deployed model data. Consider the following before you deploy a model:
The scenario steps are same as those in A new model deployment scenario.
Note: Be sure to keep a copy of the generated artifacts as a backup. It is recommended also to keep the log files that were generated during deployment. These log files can aid during un-deployment and if error determination is required at a later time (e.g. when deployment of a new version fails).

Copyright IBM Corporation 2005, 2006. All Rights Reserved.