The Schema Generator generates database and cube views artifacts
based on each imported Business Measures-Modell.
The database administrator (DBA) executes the artifacts as a step in the
Business Measures-Modell deployment phase. The following
tasks must have been completed prior to deploying any
Business Measures-Modell:
- Participate in pre-planning exercises. This involves deciding about the
topology, determining event rates, number of users supported, database instance
and database parameters, buffer pools and table spaces, and a backup and recovery
strategy. It is also important to a have a strategy for determining how and
where generated artifacts are stored. It would be wise to be able to find
a set of previously generated artifacts by model and version number and whether
they were deployed. This is useful for both change management and support
scenarios.
- Create the Repository, State, Runtime, and Historical databases using
the WebSphere Business Monitor Launchpad. Creating
a database includes creating a set of static database tables, setting up the
State and Runtime databases to be replication sources, and also creating some
other database objects like stored procedures and udfs which are specific
to various components of WebSphere Business Monitor.
- Run the Schema Generator to generate Business Measures-Modell related
artifacts.
Anmerkung: It is recommended to back up all databases before you deploy any
generated artifacts
After you have generated the artifacts, perform the following to deploy
them:
- Deploy the generated DDL scripts to create the Business Measures-Modell dynamic
tables in the State, Runtime, and Historical databases.
- Execute the replication scripts to enable databases replication.
- Import the cube view definition file into DB2 Cube Views.
The following figure describes the artifacts deployment phase: