Configure the Historian Database

This section describes how to configure the Historian database. RTView Enterprise Monitor is delivered with HSQLDB as the default database. To use the Historian database you deploy an alternate database that is accessible via JDBC, configure the database connection by editing a configuration file and enable the Historian database. In RTView Enterprise Monitor, the Historian, by default, is configured so that almost all Data Servers share the same database.

At this point you have:

Verified System Requirements.

Completed instructions in Installation for the full RTView Enterprise Monitor platform.

Completed instructions in Configure Central Servers.

Completed instructions in Configure Solution Package (you have configured a local RTView Enterprise Monitor deployment and Web Browser RTView Enterprise Monitor deployment. That is, displays such as the All Management Areas - Area Heatmap are populated with JVM data from RTView Enterprise Monitor servers and the CMDB database).

Have Solution Package-specific displays showing monitoring data from your environment (you do not yet see Solution Package data in displays such as the All Management Areas - Area Heatmap).

Completed instructions in Configure Service Data Model.

Completed instructions in Configure Databases of the Central Servers (you have configured the Central Server Database for your production environment).

To configure the Historian database:

Perform the steps described in Configure Databases of the Central Servers to setup the Alert Historian using the following Historian-specific instructions:

Edit the emcommon.properties file (rather than the central.properties file), located in your project directory/conf directory. In the emcommon.properties file under the HISTORY CONFIGURATION, Define the RTVHISTORY DB section, uncomment and modify the following entries as appropriate for your environment:

collector.sl.rtview.sql.sqldb=
	Add the required connection information. For example, for an Oracle database you make the following edits: ConfigCollector.sl.rtview.sql.sqldb=RTVHISTORY myusername mypassword jdbc:oracle:thin:@myhost:9099:myinstance oracle.jdbc.driver.OracleDriver - false false
historian.sl.rtview.historian.driver=
	Driver of your database. For example: historian.sl.rtview.historian.driver=oracle.jdbc.driver.OracleDriver
historian.sl.rtview.historian.url=
	Full URL to use when connecting to this database using the specified JDBC driver.
historian.sl.rtview.historian.username=
	User name to enter into this database when making a connection.
historian.sl.rtview.historian.password=
	Password to enter into this database when making a connection. If there is no password, use “-“. See Encrypt Password to use an encrypted password.

Note: These instructions assume that the Historian database connection is shared by all Data Servers. However, this configuration might not be suitable for your system needs and architecture.

Create database tables using the .sql template files provided for each supported database platform, located in your project directory/dbconfig directory of each installed Solution Package:

create_<package>_tables_<db>.sql

where <package> ={emsmon, bwmon, ocmon, wlm, etc.} and <db> ={db2, mysql, oracle, sqlserver, sybase}

Note: For details about improving database performance and Historian response time, see the -charlimit property and the -index_history_tables property.