Configure RTViewCentral Databases

This section describes how to configure the use of a production database for the Alert Threshold Database Connection, the Historian Database Connection, the CMDB Database Connection, the Diagram Generator Connection and the Metric Explorer Connection.

RTViewCentral requires the following databases: ALERTDEFS, RTVCMDB and RTVHISTORY, each of which contain several tables. RTView Enterprise is delivered with a default memory resident HSQLDB database, which is suitable for evaluation purposes. However in production deployments, it is recommended that a supported database engine be used that is accessible via JDBC. This section describes how to setup an alternate database and, if needed, how to manually create the database tables (which requires table-creation permission in your database engine).

To configure RTViewCentral databases:

  1. Select and install a database of your choice. Supported databases are Oracle, Sybase, DB2, Microsoft SQL Server and MySQL.

  2. Note: Users of the Docker platform have access to an image of MySQL 5.7 configured for use with RTView, on Docker hub at slcorp/mysql-rtview. For more information refer to rtvapm/containers/docker/mysql-rtview/README.txt.

  3. Gather the following information for each database you wish to connect:

  4. Note: The Run Queries Concurrently option should be used with caution since it may cause SQL errors when used with some database configurations and may degrade performance due to additional database server overhead. See your database documentation to see whether it supports concurrent queries on multiple threads.

  5. Open the RTView Configuration Application and go to Server Configuration/Databases:

  6. Enter your gathered information for each database you wish to connect:

  7. Tip: Click Copy to clipboard to copy/paste a database connection details into another database connection.

  8. Click icon_save.gif (in title bar) to save your changes, then click cui_requires_restart.gif to apply them.


    Note: cui_requires_restart00006.gif appears in the title bar when a project has changes not yet applied.

  10. Manually create the tables needed for each database connection. To create tables for your database, use the .sql template files provided for each supported database platform, located in the RTVAPM_HOME/common/dbconfig directory:






Templates for the central RTVHISTORY tables are located in RTVAPM_HOME/common/dbconfig:


Templates for solution package-specific RTVHISTORY tables are located in the dbconfig subdirectory of each solution package under RTVAPM_HOME. For example, the .sql templates file for the Solution Package for TIBCO Enterprise Message Service™ are located in /rtvapm/emsmon/dbconfig (%RTVAPM_HOME%\emsmon\dbconfig on Windows (or $RTVAPM_HOME/ emsmon /dbconfig on Linux). Use the schemas for the solution packages that you plan to use.

The following is the file naming format for the dbconfig directory:


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


Templates for RTVMX tables are located in the RTVAPM_HOME/mx/dbconfig directory:


where <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.

You have finished configuring RTViewCentral databases.

Note: RTView DataServers that are configured to integrate with EM will access the Alert Threshold Database via the Central Server. However, each RTView DataServer is configured with a separate Historian database by default. If you want to use the central Historian database for your RTView DataServer, copy the connection information entered here to the Historian database field in your RTView DataServer Configuration Application.