This page contains details about the deployment process that are specific to your data source. Please go to the Deployment section of this documentation for instructions on how to implement your Enterprise RTView deployment option. Return to this page whenever you are instructed to refer to deployment information that is specific to your data source.

System Requirements and Setup
The SQL data source has additional System Requirements and Setup.

Data Source Configuration File
Enterprise RTView saves general application settings as well as data source configuration options in initialization files that are read at startup. If no directory has been specified for your initialization files and files are not found in the directory where you started the application, then Enterprise RTView will search under lib in your installation directory. NOTE: When you start an Enterprise RTView application from the Windows Start menu, it runs from the demos directory.  

Include the following initialization file when you deploy Enterprise RTView with this data source:
 

File Name	Description
OPTIONS.ini	Contains general options as well as data source options for SQL.

NOTE: Options specified using command line and applet parameters override values set in initialization files.

Rich Client Browser Deployment Setup for Direct Data Connection
NOTE: If you are using history data you must include the SQL data source in your applet as detailed below.

A. Required Applet Parameters

In addition to basic applet parameters, to host the Display Viewer Applet you must specify the following in your HTML file.

Include the SQL data source in your applet: 1. Add the following to your ARCHIVE parameter (found under your installation directory in lib): gmsjsqlds.jar 2. Add the following applet parameter: name = ds value = com.sl.gmsjsqlds.GmsRtViewSqlDs NOTE: To specify multiple data sources for the value of the ds parameter, separate them with a ;. 3. If your display contains SQL data attachments which use a JDBC driver, include the jar containing your JDBC driver class. 4. If you are using a JDBC driver to connect to a database for any data attachments in your display, include the jar for your JDBC driver in the ARCHIVE parameter.

B. Optional Applet Parameters

The following options are read from OPTIONS.ini if not included in the applet parameters of your HTML file.

Parameter Name	Description
dbretry	Specify the interval (in milliseconds) to retry connecting to a database after an attempt to connect fails. Default is -1, which disables this feature.
dbfailedlimit	Specify the number of consecutive failed SQL queries after which to close this database connection and attempt to reconnect. Default is -1, which disables this feature.
noquerydbinfo	Set to true if you do not want to query your database for available tables and columns in your database. If a Database Repository file is found, it will be used to populate drop down menus in the Attach to SQL Data dialog. Default is false.
sqlquote	Set to true to enclose all table and column names in quotes when a SQL query is run. This is useful when attaching to databases that support quoted case-sensitive table and column names.

C. Setup Client

1. If you will be viewing displays that include SQL data attachments or history data, modify your Java security settings to include the following permission:

permission java.util.PropertyPermission "file.encoding", "read";

2. If you will be accessing a database on another system, modify your Java security settings to include the following permission:
 

permission java.net.SocketPermission "host", "accept, connect, listen, resolve"; Where host is the system where the database is running.

3. If you are using an ODBC driver to connect to your database, modify your Java security settings to include the following permission:

permission java.lang.RuntimePermission "accessClassInPackage.sun.jdbc.odbc";

4. If you are using a JDBC driver to connect to your database, include the jar for your driver in the ARCHIVE parameter. Depending on your driver, you may also need to add an accessClassInPackage RuntimePermission for your driver package.