In order to deploy a new
business measures model,
you will pass through a series of activities to create and deploy all databases
artifacts before you can start the monitoring services. The basic flow of
activities is:
- Prepare the business measures model in
the Business Measures editor.
- 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 .
- Generate the artifacts from the Schema Generator through the WebSphere Business Monitor administrative console for
the imported business measures model. The
generated artifacts are packaged into a separate folder with the business measures model. The contents of this folder
are:
- A zipped file containing the business measures model and
the cube views definitions files that will be imported through the WebSphere Business Monitor administrative console.
- The Database Definition Language (DDL) scripts (three ddl files) needed
for creating the State, Runtime, and Historical database tables that correspond
to the imported business measures model.
- The cube views definitions that contain the description of the star schema.
- The replication scripts (three zipped files) required to maintain the
replication among the State, Runtime, and Historical databases.
- Execute the generated DDL scripts to create the dynamic tables in the
State, Runtime, and Historical databases. These tables correspond to the business measures model that will be imported. For
more information on executing the generated scripts, refer to Creating
dynamic database tables section.
- Deploy the replication artifacts to enable replication between the 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.
- Configuring Common Event Infrastructure (CEI) bus on the remote WebSphere Application
Server machine. For more information about configuring CEI bus, refer to configuring
CEI Bus on remote WebSphere Application Server cell topic.
- Configuring dashboard client. For more information about dashboard configuration,
refer to administering
dashboards and views topic.
- Configuring adaptive action manager. For more information about adaptive
action manager configuration, refer to Administering Adaptive
Action Manager topic.
- Import the .zip file, which is created by the Schema Generator and includes
the business measures model and Cube Views definitions,
into the WebSphere Business Monitor administrative
console.
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).