During runtime, some changes to the business measures model may
be required. Those changes are made in the Business Measures editor,
and they require a new deployment for the model. According to the changes
made, the Schema Generator will assess whether this model will be a new model
or a new model version.
For more information on the applicable changes, refer to change
management artifacts generation in database services section.
For a new model version, the Schema Generator generates the scripts to
alter the corresponding databases. The DBA decides whether to generate all
artifacts of the model as a first-time deployment or to generate the artifacts
to alter the databases, based on the changes only. To deploy a new model version,
you have to perform the following steps:
- Export the business measures model from
the Business Measures editor. The exported
file monitor.zip contains the business measures model.
- Configure the Schema Generator through the WebSphere® Business Monitor administrative
console. As part of the configuration you should have a strategy for saving
the generated artifacts. When choosing an output directory, choose a directory
which include the business measures model project
name, project version and date. Using a mechanism such as this will help aid
in managing the generated artifacts as well as aiding IBM® support in case of any support is needed
. For more information about administrating Schema Generator, refer to Managing Schema
Generator section .
- Regenerate the artifacts from the Schema Generator through the WebSphere Business Monitor administrative console.
Note: To
generate the artifacts of the differences between the new model and the deployed
model only, clear the ignore previous deployments when generating
artifacts check box. If you want to populate an empty database,
select this check box.
The generated artifacts are packaged into a
separate folder with the business measures model.
- Check the Schema Generator output to ensure that no incompatible changes
were made in the model. If there were any, export the business measures model as
a new model.
- The DBA should backup the databases before executing the new scripts.
For more information about database backup, refer to DB2® Data Recovery section.
- Run the generated Database Definition Language (DDL) scripts to alter
the existing databases tables according to the changes. For more information
on executing the generated scripts, refer to Creating
dynamic database tables section.
- Deploy the replication artifacts to enable replication between WebSphere Business Monitor databases. For more information
about deploying replication artifacts, refer to Deploying
data movement services section.
- Import the Cube
Views™ definitions into DB2 OLAP Server™. For more information about
deploying cube views model, refer to deploying
cube views database schema section.
- Create the ABX cubes manually in the DB2 ALPHABLOX® admin console. For more
information about manual creation of ABX cubes, refer to creating ABX cube manually section.
- Start the data movement services to start synchronization between WebSphere Business Monitor databases. For more information
about starting data movement services, refer to starting/stopping
a data movement service section.
- Import the zip compressed file that includes the business measures model and
cube views definitions into the WebSphere Business Monitor administrative
console. You must restart the WebSphere Application
Server after
this step in this case.
The new model version deployment may not perform as expected for the following
reasons:
- Repository metadata is not synchronized with the database table structure,
resulting in create or alter statements that are not compatible with the current
database state. You may have to manually manipulate the DDL scripts to change
them into a valid state. This problem is most likely to occur when a model
version has been removed from the server.
- Additional metric columns can result in a table exceeding its table-space
page size. Manually migrate this table to a larger page-size table space before
you run the alter commands to add the new columns.
Note: - After the model is deployed, the dashboard will show the information of
the latest version of the business measures model only.
- Be sure to keep a copy of the generated artifacts as a backup.
- Be sure 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).