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:
- A new process is added, resulting in the addition of a new table.
- A new metric is added, which is not part of a dimension, or is created
in a new dimension, and a new column is added to the appropriate process tables.
- The length of a metric of type string is changed, resulting in a change
in the corresponding column length.
Any changes in the
business measures model require you to repeat the following
steps:
- Import the changed business measures model into
the Schema Generator in the WebSphere® Business Monitor administrative
console to generate the corresponding artifacts.
- Run the newly generated Database Definition Language (DDL) scripts to
update the database with the changes.
- Deploy the replication scripts to synchronize the State, Runtime, and
Historical databases after the changes.
- Deploy the newly generated Cube Views™ definitions.
- Deploy the business measures model into
the WebSphere Business Monitor administrative
console.
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:
- Changing the Usage in WebSphere Business Monitor attribute
of a business measure, for example, changing a metric from a Active
data about running process value to a Quantitative
data in dimensional analysis value.
- Changing the dimension group to which a metric belongs.
- Changing the status of isPartOfDimensionKey check box on a dimension
metric in the Business Measures editor.
- Changing the data type of the metric. Changes in the metric data type
are handled by deleting a current metric and creating a new one.
- Deleting a metric that is part of a dimension key.
- Creating a new metric as part of a dimension key for an existing dimension.
- Changing a timer between accumulating and non-accumulating types.
- Changing the process model or the activities.
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:
- New model deployment
- New version model deployment
- Different model deployment