Enterprise RTView communicates with your database using either a direct JDBC connection or an ODBC-JDBC bridge connection. Both connections require some setup before Enterprise RTView can communicate with your database.

Once you have setup your database connection, you will need to add your database in the Display Builder from the Application Options dialog on the SQL tab. Enterprise RTView will attempt to connect to your database. If Enterprise RTView is unable to connect to your database, this means that either the driver is not setup correctly or that you do not have permission to access the database. NOTE: Databases that have been setup to Use Client Credentials will not connect unless you are logged in and you have objects in your display that are using that connection.

If the connection is successful, and the Get Tables and Columns from Database checkbox is selected in the Application Options dialog, Enterprise RTView will use information from this database to populate drop down menus in the Attach to Data dialog with available tables and columns. If a Database Repository is found, information from your database will be merged with data from the repository file. If you deselect the Get Tables and Columns from Database checkbox Enterprise RTView will no longer query your database for this information, but the Database Repository will still be used to populate drop down menus. Using a Database Repository to populate drop down menus makes it possible to specify which tables and columns from your database will be listed in the Attach to Data dialog and gives you the ability to build displays while databases are offline.
 

Direct JDBC Connection
In order for Enterprise RTView to communicate with your database using a straight JDBC connection, you must have a JDBC driver for your database. JDBC drivers are available from most database vendors. To make your database driver available to Enterprise RTView, locate the driver on your machine and define an environment variable named RTV_USERPATH so that it includes the path to the driver class or the jar that contains the driver class. The RTV_USERPATH variable is included in the classpath for Enterprise RTView. It may contain paths to multiple driver classes. You must know the fully qualified class name for the driver class and the database URL required to connect to your database when you add the database in the Application Options dialog. The database URL typically contains the protocol and sub-protocol strings for your database as well as the path to the database and a list of properties. If you do not know the syntax for your database URL, consult the documentation for your JDBC driver.
 

ODBC-JDBC Bridge Connection
In order for Enterprise RTView to communicate with your database using an ODBC-JDBC bridge, you must have an ODBC driver for your database. Most databases that run on Microsoft Windows come standard with an ODBC driver. You must also register your database with ODBC before accessing it from Enterprise RTView. The name specified for the ODBC data source name during the ODBC driver setup is the name you will use when accessing the database from Enterprise RTView.
 

Register Your Database with ODBC

Windows:

1. From the Windows Control Panel, double-click on the ODBC Data Sources icon. If this icon is not listed, double-click on the Administrative Tools icon and then double-click on the Data Sources (ODBC) icon. This will open the ODBC dialog.

2. In the ODBC dialog, click Add. In the Create New Data Source window, select the driver for which you want to setup a data source. Click Finish to bring up the Setup dialog.

3. Enter a Data Source Name. This is the name you will use in Enterprise RTView when creating data attachments.

4. Click the Select button and choose your database.

5. Click OK in the Select Database, Setup, and ODBC dialogs.

UNIX:

UNIX systems do not come standard with an ODBC driver. Contact your system administrator for information on how to install and setup an ODBC driver for your database.

Database Repository File
A Database Repository file may be used to populate the initial values of drop down menus in the Attach to Data dialog. See Application Options for information on how to create a Database Repository file.

It is possible to edit an existing Database Repository file, however the file name sqlrepository.xml cannot be modified. If sqlrepository.xml is not found in the specified directory or your current working directory, Enterprise RTView will look in the lib directory. If the Database Repository file is not found, drop down menus will remain empty until databases are added from the Application Options dialog or typed directly into the Attach to SQL Data dialog.

To edit an existing Database Repository file, supported tags and attributes are as follows:
 

Tag	Attribute		Description
sqlrepository	xmlns		Top level tag that includes the namespace attribute xmlns, which must be defined as www.sl.com (xmlns="www.sl.com")
db	name		Database name
	table	name	Table name
		col	Possible column value

An example Database Repository file:

<?xml version="1.0"?>
<sqlrepository xmlns="www.sl.com" version="3.0">
        <db name="SampleDB">
                <table name="production_table">
                        <col>Plant</col>
                        <col>Units in Production</col>
                        <col>Units Completed</col>
                        <col>Status</col>
                        <col>On Schedule</col>
                </table>
                <table name="system_table">
                        <col>System</col>
                        <col>Status</col>
                        <col>%Free Space</col>
                        <col>CPU Usage</col>
                       <col>On Site</col>
                </table>
                <table name="trade_table">
                        <col>Customer</col>
                        <col>Symbol</col>
                        <col>Shares</col>
                        <col>Purchase Price</col>
                        <col>Current</col>
                        <col>High</col>
                        <col>Low</col>
                </table>
        </db>
</sqlrepository>

Excluding Tables From The Attach To SQL Data Dialog
To exclude tables from the Attach to SQL Data dialog, copy the sqlrepository.xml file to a new sqlexcludedtables.xml file and remove the table references that you want to include in the Attach to SQL Data dialog drop down menus. For example:

<?xml version="1.0"?>
<sqlrepository xmlns="www.sl.com" version="3.0">
        <db name="SampleDB">
                <table name="production_table">
                        <col>Plant</col>
                        <col>Units in Production</col>
                        <col>Units Completed</col>
                        <col>Status</col>
                        <col>On Schedule</col>
                </table>
        </db>
</sqlrepository>

Save the sqlexcludedtables.xml file to your RTV_HOME\lib directory. Table information stored in sqlexcludedtables.xml will now be excluded from the initial values of Table Name drop down menus in the Attach to SQL Data dialog.

NOTE: It is not necessary to create a Database Repository file in order to use sqlexcludedtables.xml. Enterprise RTView will still use the sqlexcludedtables.xml file to exclude tables from the Attach to SQL Data dialog. If you have an sqlexcludedtables.xml file and you click the Save Database Repository button, the new sqlrepository.xml file will not contain any of the tables listed in your sqlexcludedtables.xml file.

To create your own sqlexcludedtables.xml file without creating a Database Repository File, supported tags and attributes are as follows:
 

Tag	Attribute		Description
sqlexcludedtables	xmlns		Top level tag that includes the namespace attribute xmlns, which must be defined as www.sl.com (xmlns="www.sl.com")
db	name		Database name
	table	name	Table name to exclude

NOTE: The file name sqlexcludedtables.xml cannot be modified.