Depending on which data sources are licensed in your Enterprise RTView application, additional setup may be required. For information on setup for your data source, refer to the Data Sources section of this documentation. If you will be using the Oracle Coherence Monitor, refer to the System Requirements and Setup for the Oracle Coherence Monitor.

Once setup is complete, please refer to the Registration section for instructions on how to obtain a license key.

Setup Environment
 Append the following to the PATH environment variable:
 

Name	Description	Example
<java installation directory>\bin	The bin subdirectory of the Java installation subdirectory.	c:\Program Files\Java\jdk1.5.0_01\bin

Set RTV_HOME Locally or Globally

Locally
Use the following initialization scripts to set the RTV_HOME environment variable and append RTV_HOME\bin to the PATH environment variable. NOTE: You must initialize each command or terminal window you open.
 

Globally
Alternatively, you may set RTV_HOME and append RTV_HOME\bin globally. NOTE: In order to use shortcuts (available in the Shortcuts directory) the environment variable RTV_HOME must be set globally on your system and RTV_HOME\bin must be included in your PATH environment variable. Shortcuts are available for use on Windows platforms only.

Include lanscan in PATH Environment Variable (HP users only)
If the hostid script is not available on your system, HP users must include the location of lanscan in their PATH environment variable. The standard location is /usr/bin.

RTV_USERPATH
Java options specified in RTV_USERPATH will be added to the classpath by all of the Enterprise RTView run scripts. These options are also used when Enterprise RTView applications are run from the Windows Start menu:
 

Name	Description	Example
RTV_USERPATH	Java options. These will be passed into the java process from the Enterprise RTView run scripts. These are also used when Enterprise RTView applications are run from the Windows Start menu. This environment variable is optional.	c:\mycustomjars\myjar.jar

RTV_JAVAOPTS
Java options specified in RTV_JAVAOPTS will be used by all of the Enterprise RTView run scripts. These options will not be used when Enterprise RTView applications are run from the Windows Start menu:
 

Name	Description	Example
RTV_JAVAOPTS	Java options. These will be passed into the java process from the Enterprise RTView run scripts. These will not be used when Enterprise RTView applications are run from the Windows Start menu. This environment variable is optional.	-verbose
	Specify the name of a directory, including path, for configuration files to be saved to and read by the Display Builder, Display Viewer, Display Server, Data Server and Historian. -Dcom.sl.rtview.optionsFileDir=(directory) This option is useful when you want to run multiple Enterprise RTView applications from the same project directory, but with different configuration files. Let's suppose you want to run both the Display Viewer Application and the Display Server from the same project directory, but for the Display Server you want a direct data connection and for the Display Viewer you want to use the Data Server. Since both applications require an OPTIONS.ini file to determine whether to use direct connect or served data, a separate OPTIONS.ini file is necessary for each application. To resolve this issue, and avoid having separate project directories for each application, you can create a subdirectory for the Display Viewer OPTIONS.ini file and specify that subdirectory in the RTV_JAVAOPTS environment variable. Then, as usual, you may run the Display Server and the Display Viewer from your project directory, but the OPTIONS.ini file for the Display Viewer will be located in the directory you specified. If no alternate directory is specified and configuration files are not found in your project  directory (i.e. the directory where current application is running), 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. To startup in a directory other than demos, you must run Enterprise RTView from a command window.	-Dcom.sl.rtview.optionsFileDir=MyOptionsFilesDir

Demo Server, Data Server, Display Server and JSP Example
To use the Demo Server, Data Server, Display Server or Java Server Pages Example you must also set the following variables:
 

Name	Description	Example
CATALINA_HOME	Web server installation directory.	C:\Tomcat
JAVA_HOME	JDK1.5.0_01+ installation directory. Only required if you will be using the Demo Server.	C:\Program Files\Java\jdk1.5.0_06
RTV_DEMOSERVER	The location of the Demo Server in your Enterprise RTView installation. This variable may be setup in the Windows installer. It is also set to the correct location when you run the rtv_init script to initialize a command window. Only required if you will be using the Demo Server.	C:\Program Files\ERTV\servers\apache_tomcat-5.5.17_sl

TIBCO EMS Manager
In addition to the environment variables listed above, if you will be using the TIBCO EMS Manager you must set TIBJMS_ROOT. If you will be using SSL, you must set both TIBJMS_ROOT and RTV_USERPATH:
 

Name	Description	Example
TIBJMS_ROOT	TIBCO EMS installation directory. If you installed Enterprise RTView using the Windows installer, this variable may already be set globally on your system.	C:\TIBCO\ems
RTV_USERPATH	TIBCO EMS SSL support jars.  NOTE: If this variable already exists append the TIBCO EMS jars to it.	If you are using SSL for communication include:  C:\TIBCO\ems\clients\java\tibcrypt.jar;C:\TIBCO\ems\clients\java\jnet.jar; C:\TIBCO\ems\clients\java\jcert.jar;C:\TIBCO\ems\clients\java\jsse.jar