The Thin Client deployment is implemented using the Display Server. The Display Server consists of two parts, the Display Server application and the Display Servlet. The Display Server application is generally installed on a dedicated platform. It runs the RTView engine which loads displays, and gathers data which it passes on to the Display Servlet via a socket. The Display Server can either access data directly or it can connect to the Data Server for data. The Display Servlet is a JSP servlet that runs on an application server. Clients communicate with the Display Servlet using HTTP, so the only system requirement for a the client is a standard browser.

This document describes the system requirements, configuration, installation and runtime information for the Display Server application, Display Servlet and the browser client. Some objects and interactions behave differently in the Display Server than they do in the other RTView deployments. See the Runtime Functionality and Limitations sections below for more information.

Display Server Application

System Requirements
The system where you will run the Display Server application must meet the following system requirements:

Java 1.5.0_01+ Basic system requirements In addition to basic system requirements, if you will not be using the Data Server, refer to the Data Sources section of this documentation for system requirements and setup specific to your data source.

Display Server Configuration
Create DISPLAYSERVER.ini in the directory your project directory with the following options:

Option	Description
cellsperexport	Specify to limit the number of table cells included in HTML/Excel exports requested by the Thin Client. This option avoids out-of-memory exceptions and timeouts when exporting tables with many rows. This option is typically used in conjunction with the cellsperpage option, and has the following behavior: If the cellsperexport option is not specified, or if a value of less than a 1000 is specified, the Display Server attempts to export all rows for all tables, regardless of the table size. If a table contains fewer cells than the cellsperexport setting, the Display Server exports all rows for that table. The exported HTM/Excel table starts with the same first row (or near it) that is visible in the Thin Client. That is, if you scroll to row 900 in the Thin Client and perform an HTML/Excel export, the exported table will begin near line 900. If the rows included in an export to HTML/Excel are limited by the cellsperexport option, the first row in the exported file is the same as the first row currently visible in the Thin Client. An export to HTML/Excel requires less CPU and memory than an export to PDF (see cellsperreport), therefore the value of the cellsperexport option is typically larger than the value of the cellsperreport option. For example, if an export to HTML/Excel was performed on a table with 5 columns and 100,000 rows, and the option cellsperexport 30000 was specified when the Display Server was launched, 6000 rows (30000/5) would be included in an exported HTML/Excel file for that table. If the cellsperreport 5000 option was specified, an export to PDF would include 1000 rows from the table. NOTE: This option is not recognized by the Builder or the Viewer. Example: cellsperpage 10000 cellsperexport 30000
cellsperpage	Specify server-side table paging and sorting mode, also referred to as paging mode, for the Thin Client. Paging mode improves the performance of displays containing table objects (obj_table02) with many rows. In paging mode, the Display Server sends a specified maximum number of table data rows at a time to the Thin Client, rather than sending all table data rows at once. This option avoids out-of-memory exceptions, timeouts and sluggish performance that can otherwise occur from processing and transmitting all of the rows at once. This option is typically used in conjunction with the cellsperexport and cellsperreport options, and can also be specified on the command line. The page of rows sent from the Display Server to the Thin Client includes all of the rows currently visible in the Thin Client plus additional rows above and/or below the visible rows. If the user scrolls beyond the rows contained in the current page or clicks on a column header to change the sorting order, the Display Server sends another page of rows in response. To specify in the DISPLAYSERVER.ini file: cellsperpage NNNN where NNNN specifies the number of table cells the Display Server includes per page. Typical values for cellsperpage are 10000 to 30000. The number of cells in a table is equal to the number of rows multiplied by the number of columns. For example, if cellsperpage = 10000, and the display contains a table with 5 columns, the Display Server uses a page size of 2000 rows for the table. This means the Display Server sends a maximum of 2000 table rows to the Thin Client at a time. If the table contains 40,000 rows the Display Server sends rows 1 through 2000 to the Thin Client when a user opens the display. If the user then scrolls to the bottom of the table, the Display Server sends rows 38,001 through 40,000 to the Thin Client. Similarly, if the user clicks on a column header to sort by that column, the Display Server sorts the table and sends the first 2000 sorted rows to the Thin Client. After the user scrolls or sorts a table in paging mode, the Thin Client displays '...' in each cell and an hourglass cursor appears over the table while it waits to receive the new page from the Display Server. The cellsperpage option also has the following behavior: A smaller value for cellsperpage reduces the memory requirements for processing large tables in the Display Server, Application Server, and browser. A larger value smoothens scrolling in the Thin Client because it increases the number of rows through which the Thin Client can scroll before it needs to request another page from the Display Server. If the cellsperpage option is not specified, or if a value less than a 1000 is specified, paging mode is disabled and the Display Server sends all data rows to the Thin Client for all tables regardless of the table size. If a table contains fewer cells than the cellsperpage setting, the Display Server sends all rows for that table. Paging mode only affects the behavior of obj_table02 objects, and only in the Thin Client. The maxNumberOfHistoryRows property on obj_table02 still limits the maximum number of rows that are shown in the table, regardless of the cellsperpage setting. After scrolling to a new page, if the user immediately drags the scrollbar again, the table may not react. The user may need to nudge the scrollbar knob or click on the scroll up/down arrows to make the table react. The Thin Client Export Table to Excel/HTML/PDF feature is not affected by paging mode. Attempts to export a table with many rows may result in timeouts or out-of-memory exceptions in the Display Server or in the Display Servlet. To avoid those errors, see the cellsperexport and cellsperreport Display Server options. When displaying a table with more than 75,000 rows in Internet Explorer version 8, the last row in the table may be partially obscured even if the scrollbar knob is dragged to the bottom position. The last row can be made visible by using the mouse wheel but that may cause unused space to appear at the bottom of the table. After the user clicks a column to sort a table, the table vertical scrollbar is reset to the top position. The Thin Client ignores the scrollToSelectionFlag property on a table that is in paging mode. A table row selection is cleared when a different page of rows is received from the Display Server. If a table is in paging mode, only rows that are on the current page can be selected, even if the table multiSelectFlag property is checked.
cellsperreport	Specify to limit the number of table cells included in PDF exports requested by the Thin Client. This option avoids out-of-memory exceptions and timeouts when exporting tables with many rows. This option is typically used in conjunction with the cellsperpage option, and has the following behavior: If the cellsperexport option is not specified, or if a value of less than a 1000 is specified, the Display Server attempts to export all rows for all tables, regardless of the table size. If a table contains fewer cells than the cellsperreport setting, the Display Server exports all rows for that table. In an exported PDF file, the scroll position of the Thin Client has no effect on the starting row in the PDF file, nor any effect on the rows that are included in the PDF report. An export to PDF requires more CPU and memory than an export to HTML/Excel (see cellsperexport), therefore the value of the cellsperreport option is typically smaller than the value of the cellsperexport option. For example, if an export to HTML/Excel was performed on a table with 5 columns and 100,000 rows, and the option cellsperexport 30000 was specified when the Display Server was launched, 6000 rows (30000/5) would be included in an exported HTML/Excel file for that table. If the cellsperreport 5000 option was specified, an export to PDF would include 1000 rows from the table. NOTE: This option is not recognized by the Builder or the Viewer. Example: cellsperpage 10000 cellsperreport 5000
clearsubs	Set to false to preserve the value of local variables, for which the Use as Substitution option is selected, when navigating to different displays in the same panel. This behavior is consistent with that of the Display Viewer. By default (or if set to true), the Display Server will reset all local variables to their initial values when navigating to a new display regardless of the variable's value in the current display. NOTE: Global variables are not affected by this option.
display_timeout	Amount of time, in seconds, that a display can be kept in memory after the Display Servlet has stopped requesting it. Default is 60 seconds (to allow faster load time when switching between displays).
imageformat	Specify image format: jpg or png. If imageformat is not specified, the Display Server will automatically select the image that results in the fewer number of bytes for each display. By default the png format will be selected for most displays, but the jpg format is preferred for: a background image in the main display background images in graphs or labels images with color gradients (especially those with lower imagequality values).
imagequality	Specify a value between 0 and 100 to control the quality of .jpg images. If the value is 100, the Display Server will output the highest quality image with the lowest compression. If the value is 0, the Display Server will output the lowest quality image using the highest compression. Default is 75. If the -verbose option is specified at startup, image creation time/size for each display refresh will be shown in the Display Server console output. NOTE: The Display Server chooses an image format (.jpg or .png) for each display, depending on which format produces the smallest image size (in bytes). The size of .png images is controlled by the pngcompress option.
history_config	To preload a display, making data immediately available. Preloaded displays are not unloaded unless the Display Server is restarted or the display cache is cleared via JMX. This option may be used multiple times to specify multiple displays to preload: history_config rtvFileName substitution Substitutions are optional and must use the following syntax: $subname:subvalue $subname2:subvalue2 If a substitution value contains a single quote, it must be escaped using a / : $filter:Plant=/'Dallas/' If a substitution value contains a space, it must be enclosed in single quotes. Do not escape these single quotes: $subname:subvalue $subname2:'sub value 2' A substitution string cannot contain the following: : | . tab space , ; = < > ' " & / \ { } [ ] ( )
max_displays	Number of displays kept in memory. Default is 20 (to optimize memory used by the Display Server).
passclientlogin	If true, pass RTView login information into all data sources that have the Use Client Credentials option enabled. NOTE: Some data sources do not support this feature. For information on Application Options for your data source, refer to the Data Sources section of this documentation.
pngcompress	Specify a value between 1 and 9 to control the quality of .png images. If the value is 1, the Display Server will output the highest quality image with the lowest compression. If the value is 9, the Display Server will output the lowest quality image using the highest compression. Default is 9. A value of 3 is a good compromise between speed and quality. If the -verbose option is specified at startup, image creation time/size for each display refresh will be shown in the Display Server console output. NOTE: The Display Server chooses an image format (.jpg or .png) for each display, depending on which format produces the smallest image size (in bytes). The size of .jpg images is controlled by the imagequality option.
port	Port that the Display Server uses to communicate with the Display Servlet. Default is 3279.  NOTE: If you will be running multiple Display Server applications on the same application server, you must specify a unique port for each application.
shared_display	Enables Display Sharing for a display. Add the name of the display (.rtv) file and the substitutions, if any, to be applied when the display is opened:  shared_display <filename> [substitutions] Where: <filename> is the name of a display (.rtv) file to share. [substitutions] is an optional list of substitution string:value pairs, separated by spaces. If a substitution value contains spaces it must be enclosed in single quotes. Example: shared_display navtop.rtv shared_display summary.rtv $region:East

Example of the above options set in the DISPLAYSERVER.ini file:

cellsperpage 10000
cellsperexport 30000
cellsperreport 5000  
clearsubs false
display_timeout 60
imagequality 75
history_config trend1.rtv
max_displays 20
port 3279
passclientlogin false
shared_display navtop.rtv
shared_display summary.rtv $region:East

User Name: admin
Password: admin

To use this security feature, do the following:
1. Define the users that can access RTView, assign each user a password and one or more associated roles. If your user definitions are in an XML file, copy this file to your project directory.

2. Set role definitions to specify which displays users can access. If your role definitions are in an XML file, copy this file to your project directory.

3. Enable the Use Client Credentials option if you want to pass RTView login user name and password to database connections. NOTE: Some data sources do not support this feature. For information on Application Options for your data source, refer to the Data Sources section of this documentation.
 

Use the -passclientlogin command line option or the passclientlogin option (see Step 1D-3) in the DISPLAYSERVER.ini configuration file to pass RTView login into these database connections.

Running the Display Server

You can run the Display Server as an application or in the background as a Windows Service.

To run the Display Server as an application: open an initialized command window, go to your project directory, and type:
 

run_displayserver

Several command line options are supported for the Display Server. Java options specified in RTV_JAVAOPTS are used by the run_displayserver scripts.

NOTE: The Display Server is instrumented with JMX to allow you to manage and monitor the display cache and application settings. See Managing the Display Server Using JMX for more information.

High Availability Display Servers
It is possible to designate one or more backup Display Servers to take over during a failover event when the Display Servlet discovers that the current Display Server is no longer accessible. Backup servers may be run in hot standby mode (default) or warm standby mode (designated as a command line option). In hot standby mode all global variable definitions, as well as cache and alert definitions, are loaded and activated at start up. In warm standby mode none of these actions are performed, thereby avoiding the overhead of maintaining Alert and Cache data sources until the backup server has become the primary.

You can specify a primary Display Server, as well as one or more backup Display Servers, in the rtvdisplay.properties file.

At startup, the Display Servlet will connect to the primary server if available, otherwise it will connect to the backup server. If neither is available, the Display Servlet will periodically retry connecting to both. If the Display Servlet connects to either the primary or the backup, and later the connection is lost, it will then try to connect to the other server. If a Display Servlet connects to a backup server and later the primary server becomes available, the Display Servlet will not switch to the primary unless the connection to the backup server is lost.

If the Display Server is using the Data Server to connect to data, primary and backup Data Servers can also be specified. Refer to Running the Data Server for more information.

Display Servlet
The Display Server uses the Display Servlet, a JSP servlet that runs on your application server. Clients communicate with the Display Servlet using HTTP. The Display Servlet communicates with the Display Server via socket to request HTML for display in the browser. The servlets\rtvdisplay directory contains files (JSP, HTML, classes, properties) necessary to install the Display Servlet.

This section is intended for users with standard working knowledge of HTML, JSP and servlet deployment on an application server.

System Requirements
Display Servlet requires an application server with a servlet container such as Apache Tomcat.  An Apache Tomcat application server is included with your RTView installation for prototyping and testing your deployment before going into the production environment. The following instructions will work for your application server or the one that comes with RTView.

Display Servlet Configuration
The Display Servlet reads rtvdisplay.properties and rtvdisplay_strings.properties to get configuration information. NOTE: The rtvdisplay_strings.properties file provides the ability to localize messages that appear in the browser.

The file rtvdisplay.properties is located in servlets\rtvdisplay with the default settings. If you do not want to use the default settings, copy this file to your project directory and modify. 

Set the following options in rtvdisplay.properties:

Option	Description
DisplayServerBackup	The name of the host and port for designated backup servers. Designation of backup servers is optional; multiple backup servers should be separated by a comma.
DisplayServerConnectionFailback	When set to true, the rtvdisplay servlet attempts to reconnect to its primary Display Server, approximately every 30 seconds, while connected to its backup Display Server. When the connection to the primary server is restored the servlet disconnects from the backup server and resumes using the primary server. By default, this option is false. To enable this behavior add DisplayServerConnectionFailback=true, then rebuild and deploy the rtvdisplay.war file.
DisplayServerConnectionPool	Specifies the maximum number of simultaneous connections the Display Servlet makes to the Display Server, and, consequently determines the maximum number of display requests the Display Server processes simultaneously. The default value is 10. This option improves response times on multi-CPU systems by enabling the Display Servlet to manage a pool of threaded requests to the Display Server. By default, the Display Servlet opens to 10 simultaneous connections to the Display Server, allowing it to process up to 10 display requests simultaneously.
DisplayServerHost	The name of the host on which the Display Server is running. Default is localhost. NOTE: Default localhost assumes the Display Server and Display Servlet are running on the same application server.
DisplayServerPort	Port for communicating with the Display Server. Default is 3279. This must be the same port specified in your DISPLAYSERVER.ini file. NOTE: If you will be running multiple Display Server applications on the same application server, you must specify a unique port for each application.
DisplayServerTimeout	Amount of time (in seconds) the Display Servlet waits for replies from the Display Server. Default is 15 seconds.
DefaultRefreshInterval	Rate (in seconds) at which displays are refreshed. Default is 15 seconds. Set this interval to 0 if you do not want displays automatically refreshed. NOTE: The refresh rate specified in the rtvRefreshInterval property or the URL or DIV tag used to open a display will override this value.
LoginEnabled	Set to true to enable role management security. If enabled, a login dialog will appear when the client browses to the URL for the Display Servlet, unless single sign-on is configured. The default is false.
MaxSharedDisplays	Used to configure Display Sharing, specifies the maximum number of shared displays for which the Display Servlet stores content. The default is 10. (This property does not need to be included in the rtvdisplay.properties file if the default setting is used.) NOTE: Best practices dictate that the MaxSharedDisplays property be set to a value at least as large as the number of shared_display entries in DISPLAYSERVER.ini.
SharedDisplayRefreshInterval	Used to configure Display Sharing, specifies the time interval at which the Display Servlet updates the content it uses for a shared display. The default is 15 seconds.
VirtualThreshold	Set the cell count of a table at which point Virtual Mode is used. Default is 500.  For smooth scrolling, data is preloaded into tables with less than 500 cells. For tables with more than 500 cells, Virtual Mode is used in which data is paged into the tables to speed processing time for displaying, refreshing and sorting. However, the table may blink while scrolling in this mode.

Example of the rtvdisplay.properties file:

DisplayServerHost=localhost
DisplayServerConnectionPool=10
DisplayServerPort=3279
DisplayServerTimeout=15
DefaultRefreshInterval =15
LoginEnabled=true 
MaxSharedDisplays=10
SharedDisplayRefreshInterval=15
VirtualThreshold=500
DisplayServerBackup=host:3238
DisplayServerConnectionFailback=true

Localize Display Server
The file rtvdisplay_strings.properties contains settings for text displayed by the thin client (i.e. popup menus, login window, status window, error messages, etc.). This file is located in the WEB-INF/classes/gmsjsp directory of the rtvdisplay.war file. For localization, extract this file from rtvdisplay.war and modify. Make a copy of this file with the desired locale suffix (e.g. rtvdisplay_strings_ja.properties for Japanese) and pack into rtvdisplay.war, in WEB-INF/classes/gmsjsp.

The locale setting of the application server (e.g. tomcat) will determine which .properties file to load. If the app server does not have the desired locale setting for the thin client, then edit the original file (rtvdisplay_strings.properties) instead.

Create Custom Servlet Files
The Display Servlet comes with a few HTML files for testing. You can use these to deploy, or you can create your own HTML files or JSP files  which make calls to the Display Servlet to show your displays. All custom HTML or JSP files should be saved in your project directory or a subdirectory.

Create War File
If you will not be using the Deployment Wizard to generate your deployment, you will need to create a .war file that contains rtvdisplay.properties,  rtvdisplay_strings.properties and any custom servlet files:

1. Copy sample_make_war.bat (for Windows) or sample_make_war.sh (for UNIX) into this directory from servlets\rtvdisplay and rename it to make_war (with the appropriate extension).

2. This script takes a name for the web archive, without the .war extension, and builds a web archive file that includes all of the necessary RTView Display Servlet files along with all .html, .js, .gif and .jpg files from the current directory. If there are other files you would like to include in your web archive, add them to the following line in your make_war script:

        jar uf %1.war *.html *.jpg *.gif *.js *.jsp WEB-INF

NOTE: You may receive an error message if the script does not find at least one of each of the file types specified (.html, .jpg, etc). Disregard this error message.

3. Type make_war warName where warName is the name of the war file to create.

Deploying War Files
Once you have created a war file for the Display Servlet, you will need to install it to your application server. An Apache Tomcat application server is included with your RTView installation for prototyping and testing your deployment before going into the production environment. You can either use this application server or your own. 

If did not create a war file, use servlets\rtvdisplay as your project directory and rtvdisplay as your appname in the steps below.

Otherwise, use your project directory and your web archive file name for appname.
NOTE: If you will be running multiple Display Server applications on the same application server, each Display Servlet war file must have a unique name.

1. In an initialized command window, go to your project directory and type:
 

make_war appname

This script creates a web archive (.war) that includes all of the files necessary to run the Display Servlet.

2. Your RTView installation includes an Apache Tomcat application server, so that you can prototype and test your deployment before moving it to your production server. If you will be using this application server, run the following script to install the Display Servlet:
 

install_to_demoserver appname

This script installs the web archive to the Apache Tomcat server included in your RTView installation.  NOTE: This script will shutdown and restart Apache Tomcat and requires administrative permissions.

3. If you will be using your own Apache Tomcat application server, run the following script to install the Display Servlet:
 

install_to_tomcat appname

This script installs the web archive to your Apache Tomcat server.  NOTE: This script will shutdown and restart Apache Tomcat and requires administrative permissions.

4. If you will be using an application server other than Apache Tomcat, install the files in the web archive to your application server according to the documentation for that product.

Configure and Install Display Server Portlet (Optional)
The Display Server can optionally be deployed as a portlet. The portlet is tested in Liferay and contains configuration files specific to Liferay, but should work with any JSR-168 compliant portal. If you want to deploy the Display Server as a servlet, skip this step.
 

Configure Display Server Portlet Options
The servlets\rtvportlet directory contains all of the files necessary to install the Display Server portlet. It includes a web.xml and several other configuration files necessary for use in a Liferay portal. Make any necessary changes to these files, or if you are using another JSR-168 compliant portal, copy any required configuration files to this directory. The Display Server portlet requires the Display Servlet to run and will access it at http://host:port/rtvdisplay, where host and port are the host and port where the portlet is running.  If this is not the case, modify the value for the rtvServletUrl parameter in portlet.xml to point to the correct location of the Display Servlet. Rebuild the rtvportlet.war file using the make_war.bat script.
 

Install Display Server Portlet
Install servlets\rtvportlet\rtvporlet.war to your portal according to the documentation for that product.
 

Instance the Display Server Portlet in Your Portal
Once the Display Server portlet is installed to your portal, you can instance it according to the documentation for that product. The Display Server portlet supports edit mode and view mode. In edit mode, you can specify the display, refresh rate, window name, width and height for the portlet.

Browser Client

System Requirements
The client requires a standard browser.

Accessing the Project 

1. Open a browser and navigate to the URL for the Display Servlet. For example:
 

http://host:8080/rtvdisplay/index.html

Where host and port are correct for the application server hosting the Display Servlet.

2. Login to the Display Server. By default, the Display Server does not require a login. Login can be enabled in the Display Servlet to support role based security, If login is enabled, the default user name and password are:

User Name: admin  Password: admin

NOTE: It is possible that your system administrator may have configured another user name and password. In this case, you may also need to select a role.

Problem: An error message appears in the browser.
Solution: Check the command window where you started the Display Server as well as the Display Servlet log file on your application server.

Limitations

• Threshold commands are not supported in the Display Server, as well as the following commands:
  • Beep
  • Play Audio File
  • Run DOS Command or UNIX Shell
• The commandCloseWindowOnSuccess property is not supported in the Display Server.
• The Display Server does not support command failure notification on the client. Notification only appears as a console message on the server.
• Drill down displays have the following limitations:
  • The Topmost Window Mode has no effect in the Display Server, it is equivalent to the Normal setting.
  • If the user clicks outside of a display from which a drill down in Modal Window Mode was opened, but still within the same browser instance (i.e.: in another frame or iframe), the modal drill down may be obscured. When the mouse is moved across or clicked in the parent display, the modal drill down will return to the top.
  • In Modal Window Mode the user can close the main browser window without first closing the drill down window.
  • If the Window Position specified is completely off-screen, the coordinates will be adjusted so that the window is partially on-screen.
  • If the Window Position is set to Center of Screen or Center of Parent the window open slightly lower than expected.
  • In Firefox, when drill down window is closed the next mouse click in the parent window may be ignored.

Table Objects

• The Display Server generates JavaScript to display table objects (obj_table02). The JavaScript table has the following limitations:
  • The scrollbarMode, tabIndex and editDataEnabledFlag properties are ignored. The default values are used.
  • The minimum requirements for viewing in a web browser are Internet Explorer 5.5, Netscape 7.1 and Firefox 1.0.
  • For smooth scrolling, data is preloaded into tables with less than 500 cells. For tables with more than 500 cells, Virtual Mode is used in which data is paged into the tables to speed processing time for displaying, refreshing and sorting. However, the table may blink while scrolling in this mode. To modify, use the VirtualThreshold property in rtvdisplay.properties.
  • If a sort column is configured in the table object in the Display Builder, the sort icon does not appear in the column header when viewed in the Display Server. The sort icon appears if the sort column is selected at the time the Display Server is started.
     
• Table object (obj_table02) has the following limitations:
  • When the multiSelectFlag property is enabled:
    • Multiple rows can only be selected using Ctrl+Left click.
    • A mouse click must be used to select columns.
    • A right-click does not select a row under the mouse pointer
    • Once a table is displayed, changes to the value of the multiSelectFlag property are ignored.
    • In Firefox, a double right-click must be used to open popup menus.
  • When the indexColumns property is enabled it is ignored. Also, a selection made in the table gets cleared if the number of rows in the table changes after a data update.
  • The columnResizeEnabledFlag cannot be toggled.
  • The rowHeaderEnabledFlag cannot be toggled.

Graph Objects

• The scrollbarSize property is ignored. The system default value is used.

Object Grid

• The scrollbarSize property is ignored. The system default value is used.

Control Objects

• Since Firefox does not support multi-line tool tips, any returns (i.e. \n) found in mouseOverText entries will be replaced with spaces.
• Invalid numeric characters that are copied and pasted into text entry fields are not rejected.

Slider Control

• The Slider Control (obj_c1scale) is drawn as a scrollbar rather than a slider.
• The updateWhileAdjustingFlag, bgColor, and objHeight properties are not supported.
• The enabledFlag property is not supported in Firefox.

Button Control

• In Firefox, the defaultButtonFlag is ignored unless a control object in the display has focus.

Combo Box Control

• The textEditEnabledFlag property is not supported.

Date Chooser Control

• Uses the Datejs date library for parsing and formatting dates and times. The Datejs library subclasses the standard javascript Date object. If you embed a display with the Date Chooser control object inside your javascript application, it may pickup the Datejs date class instead of the standard date class. The Datejs library is distributed under the MIT License and can be downloaded at http://www.datejs.com.
• The month and day names can be localized by replacing the date.js file in the Display Servlet with a localized version. To do this, go to servlets\rtvdisplay in your RTView installation directory. Extract the appropriate date*.js file for your language from datejs_loc.zip. Rename this file to date.js in the servlets\rtvdisplay directory and rebuild the Display Servlet .war file. NOTE: The default date.js is a copy of date-en-US.js from the datejs_loc.zip file.
• The following dateFormat specifiers are not supported:

G, w, W, D, F, E, k, K, S, z, Z

• No validation against specified dateFormat for date entered in text entry field.

Generated HTML Controls

• Control objects are generated with your browser's default font and color settings. The bgColor and valueTextFont properties are ignored.
• In older browsers that do not support CSS, HTML control objects may not be positioned correctly and appear outside the image.
• Control objects are reset to their initial values when a Drill Down is executed. To display the current value, attach the selectedValue property to a variable or Get Substitution function for the substitution set.

Fx Graph Objects

• The Fx graph objects can be resource intensive during display loading and updating. This should be kept in mind when designing displays. A display containing several Fx graph objects may load slowly.
• If the context menu is opened near an Fx graph object, the menu will be partially hidden by the Fx graph. 
• A right-click inside an Fx graph object will open the Flash Player menu, not the Thin Client's context menu.

iPad Safari

• In the iPad settings for Safari, JavaScript must be ON and Block Pop-ups should be OFF. As of this writing, the Thin Client has been tested only on iOS 4.3.5 in Safari.
• The iPad does not support Adobe Flash, so the Fx graph objects (obj_fxtrend, obj_fxpie, obj_fxbar) are unavailable. The Thin Client automatically replaces the Fx graph objects with the equivalent non-Fx object (obj_trendgraph02, obj_pie, obj_bargraph). Note that the replacement objects behave the same as the Fx objects in most cases but not in all. In particular, obj_trendgraph02 does not support the sliding cursor object nor the legendPosition property. Custom Fx objects are not supported on the iPad.
• The Thin Client implements scrollbars for table objects and graph objects. However, unlike the scrollbars used on desktop browsers, the scrollbars used on the iPad do not have arrow buttons at each end. This can make it difficult to scroll precisely (for example, row by row) on objects with a large scrolling range.
• At full size, users may find it difficult to touch the intended display object without accidentally touching nearby objects and performing an unwanted drill-down, sort, scroll, and so forth. This is particularly true of table objects that support drill-down and also scrolling, and also in panel layouts that the tree navigation control. In those cases, the user may want to zoom the iPad screen before interacting with the Thin Client.
• If the iPad sleeps or auto-locks while a Thin Client display is open in Safari, or if the Safari application is minimized by clicking on the iPad's home button, the display is not updated until the iPad is awakened and Safari is reopened. In some cases it may be necessary to refresh the page from Safari's navigation bar.

Because the iPad uses a touch interface there are differences in the Thin Client appearance and behavior in iOS Safari as compared to the conventional desktop browsers that use a cursor (mouse) interface, such as Firefox and Internet Explorer. These are described below.

• Popup browser windows: An RTView object's drill-down target can be configured to open a display in a new window. In a desktop browser, when the RTView object is clicked the drill-down display is opened in a popup browser window. But in iOS Safari 4.3.5, only one page is visible at a time, so when the RTView object is touched a new page containing the drill-down display opens and fills the screen. The Safari navigation bar can be used to toggle between the currently open pages or close them.
• Mouseover text: When mouseover text and drill-down are both enabled on an RTView object (for example, a bar graph), in iOS Safari the first touch on an element in the object (for example, a bar) displays the mouseover text for that element and the second touch on the same element performs the drill-down.
• Resize Mode and Layout: By default, the Display Server runs with resizeMode set to crop. In crop mode, if a display is larger than the panel that contains it only a portion of the display is visible. In a desktop browser, scrollbars become available to allow the user to scroll to view the entire display. In iOS Safari, scrollbars do not appear but the display can be scrolled by dragging two fingers inside the display. (Dragging one finger scrolls the entire page, not the display).

If the Display Server is run with resizeMode set to scale or layout, the display is resized to fit into the panel that contains it. If a desktop browser is resized after a display is opened, the display is resized accordingly. On the iPad, the Safari browser can only be resized by reorienting the iPad itself, between portrait mode and landscape mode.

The panel layout feature is supported in the Thin Client. However, unlike a desktop browser which resizes to match the layout size, the size of Safari is fixed. So if the Display Server is run with resizeMode set to crop or scale mode, there may be unused space at the edges of the display(s) or, in crop mode, the panels and displays may be cropped.

This means that layout mode should be used for best results on the iPad. For layout mode to be most effective, displays should use the anchor and dock object properties. Please see RTView documentation for more information.

• Scrolling: The Thin Client implements scrollbars for table objects and graph objects. The scrollbars are activated by dragging with one finger.

If an RTView display is viewed in crop mode and is too large to be displayed entirely in Safari, scrollbars do not appear (as they would in a desktop browser) but the display can be scrolled by dragging with two fingers inside the display.

Scrollbars do not ever appear in a text area control. If the text area contains more text than is visible, use the two finger drag in the text area to scroll the text.

Regardless of the size of a listbox control, it can only display a single item (typically, the selected item). When the listbox is touched, the list of items appear in a popup list. In other words, on iOS Safari the listbox control and the combobox control behave identically.

On the default Thin Client page (opened as http://hostname/rtvdisplay), the panels cannot be resized by dragging the border between the left and right frame, as they can in a desktop browser. The list of displays in the left hand panel can be scrolled by dragging with two fingers inside the panel.

• Context menu: The Thin Client context menu is opened by a right mouse button click in a desktop browser. It is opened in iOS Safari by touching any location on a display and holding that touch for 2 seconds. The menu appears in the top left corner of the display, regardless of where the display is touched. The items Export Table to Excel, Drill Down, and Execute Command are not included on the context menu in Safari. All other items are available. The Export Table to HTML item is enabled if a table object is touched (unless the table object's drillDownTarget is configured to open another display). After and Export to PDF/HTML is performed, the exported content opens on another page in Safari. From there, the content can either be opened by another application (for example, the iBooks application opens PDF) and emailed, or it can be copied ands pasted into an email.

Test Displays
Two HTML files are included in the rtvdisplay.war for testing. You can also open a display by entering the JSP directly in the URL.

1. Open index.html (e.g., http://host:port/rtvdisplay/index.html).

In the left frame of index.html is a list of display (.rtv) files available in the directory where you started the Display Server. The main frame should show the selected display.

2. Open panels.html (e.g., http://host:port/rtvdisplay/panels.html).

The panels.html file arranges multiple display panels in frames according to your panel configuration file. If the panel configuration file is not found in the project directory where you are running the Display Server, the Display Server searches under lib in your installation directory. See the Multiple Display Panels section for information on creating panel configuration files.

NOTE: The CardPanel and GridPanel are not currently not supported in the Display Server.

3. Specify the panel configuration file name and the border width (in pixels) in the URL:

4. To specify a display to open in the URL:

5. Specify substitutions to apply to your display and a refresh rate (in seconds) which overrides the DefaultRefreshRate in rtvdisplay.properties (specified in Step 2A):
 

NOTE: To specify multiple substitutions, separate them with a + (plus). If a substitution value contains a single quote, escape it with a / (forward slash). If a substitution value contains a space, enclose it in single quotes (do not escape these quotes) and replace the space with a +.