Preparation of database artifacts deployment

Before you start creating WebSphere® Business Monitor databases using the Launchpad, you need to plan for the databases. Planning includes allocating databases sizes, preparing backup strategies, configuring data movement services, and setting table spaces and buffer pools parameters as well as determining the settings for the database instances and the individual databases.

During installation, the Launchpad creates the State, Runtime and Historical databases and the database objects that will be used for administrative purposes. In addition to these objects, the Schema Generator created a set of business measures model dedicated database objects (like tables). The Launchpad creates a set of default table spaces and buffer pools for the State, Runtime and Historical databases. These default table spaces are referenced in a table space configuration file and are designed to allow users to quickly get up and running for testing and proof of concept scenarios. To avoid performance problems and resource constraints, it is essential to plan ahead how tables will be spread across table spaces, which containers and buffer pools will be used by the table spaces.

During installation, the databases are created and only the static table definitions are created. During the artifacts generation, the dynamic tables are assigned to table spaces in the State, Runtime and Historical databases based on a customizable text configuration file. WebSphere Business Monitor is shipped with a default configuration file which is located in the <Monitor_install_dir>\install\mondb directory. This default configuration file maps all tables to exactly one table space of the appropriate size. To support ad-hoc deployments, Launchpad created during installation a set of table spaces (with 4KB, 8KB, 16KB and 32KB page size) that correspond to the entries in the default configuration file. The following example shows an excerpt from the default table space configuration file that ships with WebSphere Business Monitor:

#
# State database
#
db2.state.Default.TABLE.4K.0=DSDFLTTS4
db2.state.Default.TABLE.8K.0=DSDFLTTS8
db2.state.Default.TABLE.16K.0=DSDFLTTS16
db2.state.Default.TABLE.32K.0=DSDFLTTS32  

This simple configuration is used during artifacts generation, all tables that need to be created in the State database that fit into a table space with 4KB page size would be assigned to DSDFLTTS4. Tables with a page size of 8 KB would be stored in a table space named DSDFLTTS8, and tables with a page size of 16 KB to DSDFLTTS16. As table space requirements may vary (depending on the complexity of the model for which the data is to be stored as well as the amount of data), it is advisable not to use the default table space configuration settings in a test or production environment. Planning ahead and determining a suitable storage strategy ensures good performance.

More advanced configuration file settings can be used to map tables to table spaces not only based on the page size but also on what kind of data is going to be stored. Check the example configuration file for more information.

To determine which table space a table will be assigned to, the Schema Generator performs the following tasks:
You can edit the table space configuration file using any text editor or create a new one. Use the general configuration tab in the Schema Generator Administration console to force Schema Generator to use an alternate configuration file.
Note: The Schema Generator does not actually create any table spaces for the entries in this configuration file. This needs to be done manually prior to deploying the generated database artifacts. Artifacts deployment will fail if a table was assigned to a table space that does not exist.

Related concepts
Business Measures Model deployment scenarios

Copyright IBM Corporation 2005. All Rights Reserved.