Change management and artifacts generation

The business measures model includes many events and processes definitions. Based on these definitions, the Schema Generator generates the corresponding artifacts needed for creating the database tables, Cube Views™ definitions, and replication scripts. Changes in the business measures model induces changes in the generated artifacts.

If such a change occurs, you need to rerun the Schema Generator to generate the new business measures model scripts. This activity is called change management.

Change management is required in the following cases: Any changes in the business measures model require you to repeat the following steps:

The Schema Generator examines the previous version of the business measures model and the new version. If the new model has not been deployed or does not exist in the repository, the Schema Generator generates the artifacts that correspond to the new model. If a previous version of the new model exists, the Schema Generator examines the differences between the deployed model version and the new model version. If changes are found, the appropriate scripts are regenerated to modify the databases, based on these differences. For more information on creating a new model from an existing one, refer to WebSphere Business Modeler documentation.

Some changes in the business measures model are restricted because of limitations in altering the database tables of the existing business measures model. If the following changes have occurred, regenerate the entire model and redeploy it as a new one. A full new set of artifacts is generated and deployed. The changes are:
Note: Deleting an entire process does not require model regeneration even though that it may result in the deletion of a metric. Only the changes could be generated.
According to the changes in the business measures model, there are three deployment scenarios:

Related concepts
Business Measures Model deployment scenarios

Copyright IBM Corporation 2005, 2006. All Rights Reserved.