When you add a new business measure (metric) to an existing Business
Measures group, a new column is added in some instances tables in the State,
Runtime, and Historical databases.
The tables, which are updated with the new columns, are selected according
to the
Usage in WebSphere Business Monitor attribute
of the metric being added. The affected databases are shown in the following
table:
Metric usage in WebSphere Business Monitor databases
Usage in WebSphere Business Monitor |
State database |
Runtime database |
Historical database |
Temporary calculation |
Yes |
No |
No |
Active data about running processes |
Yes |
Yes |
No |
Quantitative data in dimensional analysis |
Yes |
Yes |
Yes |
Aggregation group in dimensional analysis |
Yes |
Yes |
Yes |
After you add a new business measure (metric) in the
Business Measures Editor,
you use the Schema Generator to generate the scripts needed to alter the created
databases (State, Runtime and Historical databases) and replication settings. To alter the databases, deploy
the Database Definition Language (DDL) scripts on the DB2 command window to add the new columns
to the database tables.
To synchronize replication among databases, update the DB2 Replication
Center with the new columns that correspond to the newly added metric by deploying
replication scripts on the DB2 command window.
When a new metric is added to a process, you need to do the following:
- Backup all databases before you deploy any new or updated business measures
model.
- Stop the monitoring service on that process.
- Stop the replication service for that process.
- Use the Schema Generator to generate the DDL scripts that are deployed
to add new columns and alter the existing databases.
- Deploy the generated replication scripts to reflect the changes in the
topology of the databases.
- Re-import the cube model into DB2 Cube Views and ALPHABLOX so
that the cube reflects any new dimensions that have been created in the Historical
database