Version 4.2.0 Release Notes

Configuration

23135: Fixed bug with removing vpn from Solace connection
	In the previous release, it was not possible to remove all Solace vpn's from the 
	connections dialog. This has been fixed. 

23140: New Connection icon no longer disappears from Configuration Application after toggling tabs on SYSLOG connections.
	The Solace Add Syslog Connection ('+') button now always appears as expected.

23187: IE 11 Compatibility mode is now recognized as not supported
	IE 11 Compatibility mode is now flagged as being unsupported for the 
	Configuration Application. 

Data Historian

22195: RTView Historian now uses PreparedStatements
	The Historian now uses PreparedStatements for repeated SQL Queries against the 
	historian database 
	- For raw data insert
	- For data compaction
	- For retention deletion
	 
	Previously the historian used literal SQL queries with unique timestamps.

Data Server

23210: Improved error reporting for start_rtv.bat/sh scripts
	The start_rtv scripts have been enhanced to report possible port conflicts before 
	trying to start a server, and to report if a server is not actually started due 
	to some other cause (e.g. expired license key). 
	
	if a server's data and/or JMX port is already in use by another process, 
	start_rtv will report e.g.: 
	
	dataserver: JMX port xxx in use by PID yyy
	dataserver: Data port xxx in use by PID yyy
	
	If the server fails to start for some other reason, start_rtv will report e.g.:
	
	dataserver:  Executing rundata -propfilter:receiver
	dataserver:  ... was not started, check log file.

23211: Message now shown in dataserver console when Java is not available.
	The scripts which start servers have been improved to give a clear indication if 
	the java command is not available. 
	
	If java(.exe) is not found on the PATH but JAVA_HOME is defined, the scripts will 
	add JAVA_HOME/bin to the PATH and try again. 
	
	If JAVA_HOME is not defined or java(.exe) cannot be found in JAVA_HOME, the 
	scripts will fail with the error "java not found on PATH and JAVA_HOME not 
	defined or not valid." On Windows this will be followed by a pause and "Press any 
	key to continue". 

General

23064: Configuration Application now displaying proper warning after failing to write property.
	An alert dialog has been added to display any warning msgs that follow a 
	successful save. 

23177: Renamed project directories in RTViewSolaceMonitor
	The project directory names have been changed:
	
	RTViewSolaceMonitor\projects\solmon -> RTViewSolaceMonitor\projects\rtview-server
	RTViewSolaceMonitor\projects\rtvmgr-> RTViewSolaceMonitor\projects\rtvmgr-server

RTView Core Functionality

Data Historian

22195: RTView Historian now uses PreparedStatements
	The Historian now uses PreparedStatements for repeated SQL Queries against the 
	historian database 
	- For raw data insert
	- For data compaction
	- For retention deletion
	 
	Previously the historian used literal SQL queries with unique timestamps.

Data Server

23211: Message now shown in dataserver console when Java is not available.
	The scripts which start servers have been improved to give a clear indication if 
	the java command is not available. 
	
	If java(.exe) is not found on the PATH but JAVA_HOME is defined, the scripts will 
	add JAVA_HOME/bin to the PATH and try again. 
	
	If JAVA_HOME is not defined or java(.exe) cannot be found in JAVA_HOME, the 
	scripts will fail with the error "java not found on PATH and JAVA_HOME not 
	defined or not valid." On Windows this will be followed by a pause and "Press any 
	key to continue". 

Scripts

23032: New validate_install.bat/sh script
	A new script has been added to the RTView distributions to validate the RTView 
	installation. It will verify the environment and directory structure and on Unix 
	it will also fix file permissions and file formats as required. 
	
	The script is validate_install.bat/sh. It is used in a command prompt or terminal 
	window by changing to the toplevel/rtvapm directory and typing 
	"validate_install(.sh)". 
	
	On Unix, if file permissions or formats are fixed, the script will print a count 
	of the files fixed. Additionally, if invoked with the argument "-v" (verbose) it 
	will list the names of the files fixed. 
	
	Examples:
	
	Validating installation in /opt/rtview/RTViewSolaceMonitor
	... Java installation correct.
	... rtvapm installation correct.
	... file permissions correct.
	... file formats correct.
	
	Validating installation in C:\rtview\RTViewDataServerKafka
	... Java installation correct.
	... rtvapm installation correct.

Solution Package

Solace

23037: Table Displays now present subset of available data, with a toggle to view full data
	To improve ease of location of metrics in the tabular displays of the RTView 
	Solace Monitor, these displays have been enhanced to show a limited set of 
	metrics by default. If the user needs the full set of metrics in the tables, a 
	toggle element in the form of the hyperlink is present. 
	
	This feature will improve usability and assist users on toggling between tables 
	showing all available metrics for the corresponding monitoring item or a limited 
	set of the most outstanding metrics. 
	
	Affected display are: All Msg Routers Table, All VPN's Table, All Clients Table, 
	CSPF Neighbors, All Bridges Table, All End points Table, Message Router Capacity 
	Table. 

23060: Two new automated topology views for CSPF Neighbors and Bridges
	Two new automated topology views for CSPF Neighbors and Bridges have been added 
	to the RTView Solace Monitor. 
	
	The first display allow users to see the topology view of their CSPF Neighbor 
	Message Routers, showing which Servers are active and which Message Routers 
	connected to each other. 
	
	The second display allow users to see the topology view of their Bridges, showing 
	the bridge connectivity as arrows between VPNs from the same or different Message 
	Routers. 
	
	LIMITATIONS
	
	- Only the Chrome browser is supported
	- Clicking on objects in the Bridges topology diagram will allow users to drill 
	down, but this functionality is not currently supported for the Neighbors toplogy 
	diagram. 

23173: Physical memory used percentage and subscription memory used percentage added to SOL_APPLIANCE database table
	Two new message router metrics have been added to the history of the 
	SolAppliances cache: physical memory used percentage and subscription memory used 
	percentage. 
	
	These metrics are shown in the Message Router Summary display in the fourth 
	metric card and under the trend tab titled "Memory". 
	
	Users will need to update the table structure of the SOL_APPLIANCE historian 
	table by executing the following alter table SQL sentences in your selected 
	database administrative tool: 
	
	Oracle:
	ALTER TABLE "SOL_APPLIANCE" ADD ("memory-used-percent" REAL , 
	"subscript-mem-used-percent" REAL); 
			
	DB2:
	ALTER TABLE "SOL_APPLIANCE" ADD "memory-used-percent" DOUBLE;
	ALTER TABLE "SOL_APPLIANCE" ADD "subscript-mem-used-percent" DOUBLE;
		
	SyBase:
	ALTER TABLE "SOL_APPLIANCE" ADD "memory-used-percent" FLOAT NULL, 
	"subscript-mem-used-percent" FLOAT NULL; 
	
	MySQL:
	ALTER TABLE "SOL_APPLIANCE" ADD "memory-used-percent" DOUBLE;
	ALTER TABLE "SOL_APPLIANCE" ADD "subscript-mem-used-percent" DOUBLE;
	
	SQLServer:
	ALTER TABLE [SOL_APPLIANCE] ADD [memory-used-percent] FLOAT;
	ALTER TABLE [SOL_APPLIANCE] ADD [subscript-mem-used-percent] FLOAT;

Version 4.1.0 Release Notes

22843: Configuration Application added to RTView Monitor for Solace
	The Solace Monitor has been enhanced to include the Configuration Application 
	which is available at the following url: 
	
	http://localhost:8068/rtview/solmon_rtvadmin
	
	The login is rtvadmin/rtvadmin. The Configuration Application can be used to 
	setup connections and poll rates and configure history. 

Configuration

22891: Configuration Application now uses basic authentication instead of digest
	In the previous release, the Configuration Application used Digest authentication 
	which cause occasional problems with the login dialog coming up repeatedly when 
	single sign on was not enabled in the app server. It has been modified to use 
	BASIC authentication instead which does not require single sign on. 
	
	Basic authentication sends the username and password as a base64-encoded string. 
	This a public encoding scheme and is therefore not secure unless https is used. 
	If you are concerned about keeping the login credentials of the Configuration 
	Application secure, you should deploy it using https which will secure all data 
	including the login credentials. 

22892: New Restart Data Server option added to configuration application
	The RTView Configuration Application has been enhanced with a button to restart a 
	Solution Package data server. This button is available whenever there are 
	unapplied changes. To restart a solution package data server: 
	
	1. Make some configuration changes and click SAVE to save them.
	2. A Restart button will appear in the top right corner of the page. When you 
	click the Restart button, you will be taken back to the top level page. The data 
	server for the solution package project will exit, then start back up with the 
	changes applied. The button is also available on the top level page if you want 
	to restart your data server later. 
	
	There is a delay of 10 seconds between the shutdown of the server and the restart 
	in order to allow system resources to be released by the exising process. It may 
	take several more seconds before Configuration Application and other clients 
	reconnect to the data server. 
	
	Note that this process only restarts the data server. Settings for the display 
	server or historian processes will not be applied until those processes are 
	restarted using the scripts. They cannot be restarted from the Configuration 
	Application. 

Distribution

22794: New user interface for RTView Monitor for Solace
	RTView Monitor for Solace UI has been updated. 
	
	To reach the new UI, open a browser window and redirect to:
	YourHost:8068/rtview/solmon
	
	where YourHost is the host name or IP address where the RTView Monitor for Solace 
	Monitor was installed. 

Solace

22796: Added Tomcat security for RTView Monitor for Solace
	Tomcat digest security has been added to RTView Monitor for Solace.

RTView Core Functionality

Distribution

22853: rtvpost servlet added to Jetty
	RTView Enteprise Monitor html server feature has been enhanced to include the 
	%RTV_HOME%\servlets\rtvpost\rtvpost.war servlet in Jetty. 

Solution Package

Solace

22721: Support Solace Cloud Edition
	Support for Solace Cloud Edition has been added. Connections can be defined using 
	the RTView Configuration Application. 

22787: Wrong metric name in renaming function will generate a wrong zero value
	A typo on the name of the spool message size in MB metric for topic endpoints was 
	preventing the correct value to be collected. This typo has been fixed and now 
	the spool message size in MB for topic endpoints is collected properly. 
	
	Also, several typos on client bridge received bytes metrics have been removed 
	which prevented the correct values to be stored in the SolBridges cache. Now the 
	client received total, data, persistent, non persistent, and direct bytes are 
	stored properly into the cache. 

22789: Collect SEMP version automatically to avoid configuration problems
	As of Solace VMR version 8.7+ and Solace Appliance version 8.3+, it is no longer 
	required to include a SEMP version string in connection properties. See 
	https://docs.solace.com/SEMP/Using-Legacy-SEMP.htm. 
	
	For earlier versions of Solace VMR and Solace Appliance, the SEMP version string 
	should be entered in connection properties. Not using the proper SEMP version 
	string would impair the collection of monitoring metrics. See RTView Solace 
	Solution Package documentation for a description to determine the SEMP version 
	string in your Solace Message Router and to enter this value in your connection 
	properties. 

22799: Full EM deployment no longer an alterative deployment option
	The RTView Monitor for Solace no longer contains the option to run a full RTView 
	Enterprise Monitor deployment. 
	
	The URLs for RTView Monitor for Solace are the following:
	- SOLMON UI: host:8068/rtview/solmon 
	      Username: solmon 
	      Password: solmonpw
	- SOLMON Configuration Application: host:8068/rtview/solmon_rtvadmin
	      Username: rtvadmin
	      Password: rtvadmin
	- SOLMON Alert Manager UI: host:8068/rtview/solmon_manager
	      Username: solmon 
	      Password: solmonpw
	- RTVMGR UI: host:8068/rtview/rtvmgr_manager
	      Username: solmon 
	      Password: solmonpw

Version 3.8.0 Release Notes

Configuration

22053: EM property handling has been enhanced
	In previous releases, sender properties could be overriden by project properties 
	unintentionally. In order to address this, the EM property handling has been 
	enhanced to give precedence to the properties that use the sender property filter 
	for processes that are run with the sender property filter. 

22069: Port inconsistencies fixed in multiple solution packages
	The following solution packages were set to use an incorrect port in rtvagent.war 
	to communicate with the dataserver: 
	
	acwmon
	mqmon
	mysqlmon
	ocmon
	syslog
	
	These have been corrected.

Deployment

21919: $rtvTimeZoneOffset substitution has been removed from emcommon and emreference
	The $rtvTimeZoneOffset substitution has been removed from 
	emsample\conf\emcommon.properties. This substitution is not used in any standard 
	EM displays. Customers who have created custom displays for use with EM, should 
	check to see if they have used that substitution and if so, add it to their 
	project properties. 

Distribution

21983: Fixed an issue with .war file creation
	Previously some solution packages could not be built from scratch in a 
	deliverable using the make_wars_package.bat script, due to a file missing from 
	the package library. This has been fixed. 
	
	The effected solution packages are:
	
	Solution Package for Amazon Cloudwatch (acwmon)
	Solution Package for VMWare (vmwmon)
	Solution Package for TIBCO ActiveSpaces (tasmon)

RTView Core Functionality

Data Historian

21921: Microsoft SQL Server 2014 and 2016 now supported
	Microsoft SQL Server 2014 and 2016 are now supported as databases for use with 
	the Data Historian, provided that the latest JDBC driver is used (sqljdbc41.jar 
	with Java 1.7, sqljdbc42.jar with Java 1.8). 

Display Server

21909: Tomcat logs no longer produce gratuitous rtvCleanup errors
	In previous releases the following error message appeared in the Tomcat log at 
	shutdown, for each deployed copy of the rtvdisplay servlet: 
	
	"SEVERE: The web application [/rtvdisplay] appears to have started a thread named 
	[rtvCleanup] but has failed to stop it. This is very likely to create a memory 
	leak." 
	
	Starting with this release, the error message should be seen less often in the 
	log file, although it may still appear occasionally. In any case, there is no 
	danger of a memory leak when tomcat is shutdown. 

21990: Fixed a vulnerability in the thin client
	An XSS (cross-site scripting) vulnerability in the thin client login.jsp file has 
	been fixed. 

21996: Fixed an issue with thin client resizing
	In previous releases, after a display is resized by the thin client to fit the 
	browser window, the black border around the default button (if any) was drawn in 
	the button's original position, rather than the button's new position. This is 
	fixed. 

Object Library

21045: Misconfigured table objects no longer cause javascript exceptions in the thin client
	A bug in the thin client has been fixed which could cause a javascript exception 
	if the columnFormat on a table object was misconfigured to specify a format for a 
	string column, and a backslash character appeared in the column. 

Scripts

22049: EM enhanced to automatically read local project.property files
	EM applications have been enhanced to automatically read project.properties if it 
	exists in the directory where they were started. If project.properties does not 
	exist, no error is printed. 
	
	Upgrade Notes: If you are upgrading from a previous version and your project 
	contains a project.properties file, be aware that this file will be used even if 
	it is not specified on the command line. To avoid this, rename or remove your 
	project.properties file. 

Solution Package

Solace

21815: Message Router drop down enhanced to show availability of message routers
	The Message Router drop down has been enhanced to indicate the availability of 
	the Message Router. When the Message Router is disconnected, the connection name 
	contains the string [?] appended to indicate the quality state: "No Data". When 
	the Message Router has expired, the connection name contains the string [X] 
	appended to indicate the quality state: "Lost Data". No string is appended to the 
	connection name if the Message Router has no monitoring issues. 

21886: Removed unnecessary link in Message Routers navigation tab
	The link to the CSPF Neighbors has been removed from the Message Routers 
	navigation tab. 

21997: Multiple improvements made to some SOLMON displays
	To avoid having the SOLMON Client displays blank when there is an error in the 
	SEMP request that populates the SolClients cache, an improvement in our displays 
	has been introduced to show the data available mainly from the SolClientStats 
	cache and leave the SolClients cache as a secondary source of data. 
	As a result, the All Clients Table can show the data coming from the available 
	SolClientStats cache. The missing columns that are primarily static strings will 
	be blank in this display. 
	In regard the Clients Summary, a quality measurement of the available data is 
	being performed so the display shows the existing data and hides the graphical 
	elements for which we don't have available current data. If the data is Expired, 
	the background of this display is shown grey with the string "[X]" appended to 
	the Client name in the drop down. Finally, the background of the display will be 
	shown as light red and the Alert State grayed out if there is no client 
	available. 

22036: Properties related to SOLMON history tables moved to conf directory
	The properties that enable/disable the SOLMON history tables have been moved from 
	the sample.properties file to the rtvapm.solmon.properties file located in the 
	conf directory. To change the default settings, follow the instructions provided 
	in the second file. 

Version 3.7.0 Release Notes

Distribution

21836: MySQL now provided via Docker Hub
	For the convenience of users who utilize Docker, the slcorp repo on Docker Hub 
	now includes an image of MySQL Database configured to work with RTView. 
	
	This container only works with Docker 1.10 and later.
	
	See rtvapm/containers/docker/mysql-rtview/README.txt for more information.

Drill Down

21887: Fixed an issue with navtrees
	In previous releases, when drilling down from within a display to another display 
	in the navtree, the tree selection sometimes failed to update correctly. This 
	happened in the case where there were multiple navtree items for the same display 
	with different subs and the user drilled down to that display from within another 
	display. This has been fixed. 

RTView Core Functionality

Alerts

21924: Fixed an issue with disabling event alerts
	In previous releases, disabling event alerts was sometimes ignored due to a bug 
	that was introduced in RTView Classic 6.7.0, RTView EM 3.2.0. This has been 
	fixed. 

Builder

21672: Builder enhanced to remember dialog window sizes and positions
	The Display Builder has been enhanced to automatically save and restore the size 
	and location of the following dialogs: 
	
	- Open (File->Open)
	- Save (File->Save/Save-As)
	- Function Results (Function Dialog->Result Button)
	
	The Tools->Reset Window Layout menu option and the -resetlayout command line 
	option restore the size and location of these windows in addition to the other 
	windows that were previously reset. 

Builder - Property Dialogs

15582: Japanese label for "Update Mode" property now shown on certain dialogs
	Previously, the Japanese label for "Update Mode" property was not shown on 
	certain polled ds attach to data dialogs when running on a Japanese OS. The 
	English label was used instead. This is no longer the case. 
	
	Affected dialogs include the custom polledds and polledds2 example data sources, 
	and the http rest data source 

Data Server

21898: Fixed an issue with rtvquery returning errors on valid query strings
	In previous releases, the rtvquery servlet would sometimes return an error of "No 
	data received before timeout, query may be invalid" for a specific, valid cache 
	query string, on every attempt. The servlet needed to be restarted to clear the 
	error. This has been fixed. 

Display Server

21906: Thin client enhanced to check user role access on each request
	In prior releases, after a user had logged into the thin client, the user could 
	manually enter a specific URL in the same browser instance and possibly view data 
	from rtview displays to which the user's role should have denied access. This is 
	fixed. 

21908: Enhanced display server with option to limit access to specific panel files
	The display server now supports a "permitpanel" option to specify the panel 
	layout files that the server will read. 
	
	A panel layout for the thin client is requested from the display server with a 
	URL parameter as follows: 
	
	   panels.jsp?file=X
	   
	where X is the name of the panel layout file that the server should read. By 
	default, the display server will attempt to read any filename on the server that 
	is specified by the URL parameter. If the file is a valid panel layout file, the 
	thin client will use it. But if the file does not exist, a "no such file" error 
	is displayed in the browser, and if the file exists but does not contain the 
	expected layout information, a "no panels found" error is displayed in the 
	browser. 
	
	The permitpanel option allows you to specify the file(s) which the display server 
	will read in response to a panels.jsp request. Requests from panels.jsp for any 
	other files are rejected with a "Permission denied" error shown in the browser, 
	regardless of whether the file exists or not, and the server will not attempt to 
	read such files. 
	
	The option may be specified multiple times to allow access to multiple panel 
	files. 
	
	Command-line example:
	
	   run_displayserver -permitpanel:PANELS.ini -permitpanel:layout.xml
	
	DISPLAYSERVER.ini example:
	
	  permitpanel PANELS.ini
	  permitpanel layout.xml
	
	In addition, the display server supports another new option to prevent attempts 
	to load remote files, as follows: 
	
	    -permitfile:LOCAL_ONLY
	
	If that option is specified any rtv or image files that are referenced by URL 
	will not be read and the server will log a message similar to the following: 
	
	  non-local file read permission denied: http://host/somefile

21912: Fixed phishing vulnerabilities in thin client
	In prior releases, it was possible to create phishing URLs which appeared to be 
	directed at the rtview thin client but would redirect the user to another site, 
	or download and possibly execute a file. These vulnerabilities have been fixed. 

Platform Support

21871: Support for Java 1.6 dropped
	RTView is now built with Java 1.7. 
	
	Java 1.6 is no longer supported.

Version 3.6.0 Release Notes

Deployment

21748: Fixed an issue where Unix data servers sometimes failed to shut down
	In previous releases, using stop_rtv on Unix platforms to stop a TIBCO solution 
	package data server process sometimes failed due to a spurious rvd process. This 
	has been fixed. 

Distribution

21846: New RTView Monitor for Solace - AMI option
	RTView Monitor for Solace is now available pre-installed on an Amazon EC2 Amazon 
	Machine Image (AMI) running Amazon Linux. It comes pre-installed with a 30-day 
	license, and is configured to start all RTView processes and supporting services 
	on restart. 
	
	The AMI includes the following application stack for convenience of quick 
	deployment. Please refer to /home/ec2-user/amibase/MANIFEST.txt for the full 
	version info: 
	
	Oracle Java 8
	Node 
	Docker
	MySQL 5.7 (via Docker) for storage of historical data
	rtvHostAgent (via Docker) for providing host metrics to RTVMGR
	cadvisor-rtview (via Docker) for providing docker metrics to RTVMGR
	
	The scripts used to create the docker containers are included in named 
	subdirectories under /home/ec2-user/amibase, to be used as templates if you wish 
	to recreate the containers with your preferred configuration. 
	
	The MySQL database data is stored external to the docker container at 
	/home/ec2-user/amibase/mysql/DATA. 
	
	Initial Setup:
	
	You may gain access to the community rtvsolmon-VERSION-YYYYMMDD-community AMI via 
	sl.com, at http://sl.com/solace-ami-free-trial/. 
	
	We recommend starting with an instance from the t2 family, sized according to the 
	number of Solace appliances you are monitoring. Depending on how much archival 
	data you wish to store in the database, you may wish to increase your disk size 
	past the default 8 GB of the AMI. 
	
	After creating an instance from the rtvsolmon-VERSION-YYYYMMDD-community AMI, you 
	will need to SSH to your instance to add the connection properties for your 
	Solace appliance(s) to 
	/home/ec2-user/RTViewSolaceMonitor/em-solmon/servers/solmon/sample.properties. 
	
	Please see the User Guide for full details.

General

21205: Thin client table objects are now rendered as HTML5
	The table objects in the EM thin client have been enhanced to provide improved 
	filtering, sorting, and other interactive features. See the release note for 
	20185 for a detailed description of the new table features. 

21813: Fixed an issue with group objects and wrapped diagrams
	In the previous release, if the first object in a wrapped diagram was defined to 
	be included in a group, it was not included in the group object. This has been 
	fixed. 

RTVMGR

21739: Enhanced the All JVMs Heatmap display with a Source drop down
	A drop down for Source has been added to the All JVMs heatmap display.

21740: Enhanced the All JVMs Table display with a Source drop down
	A drop down for Source has been added to the All JVMs Table display.

21754: Fixed an issue preventing JVM Runtime data collection
	A bug that prevented collection of JVM Runtime data from several versions of Java 
	(6, 7 and 8 versions) has been fixed. 

21792: Enhanced the All JVMs Table display with more columns
	PID, Host Name, Current Heap, and Used Heap have been added to the All JVMs Table 
	display. 

21793: Enhanced the All JVMs Heatmap display
	The All JVMs Heatmap display from RTVMGR Solution Package has been enhanced to 
	include PID, Current Heap, and Used Heap. The last two metrics are also included 
	in the Metric drop down. 

21838: Enhanced RTVMGR in SOLMON Bundle
	The RTVMGR configuration has been enhanced in RTView Monitor for Solace. It now 
	includes monitoring for a MySQL Database, as well as Host and Docker metrics. 
	
	For users of the RTView Monitor for Solace AMI version, all connection properties 
	populate these displays have been pre-configured in the standard 
	sample.properties file and do not require further configuration. 
	
	Users of the On Premise version will not see data in the Host or MySQL displays 
	unless they choose to configure these. 

RTView Core Functionality

Alerts

21795: Fixed an issue where the Cleared Reason for an alert was incorrect
	In prevous releases, the Cleared Reason was sometimes incorrect after an alert 
	was disabled and re-enabled. This has been fixed. 

Data Historian

21699: Enhanced Historian compaction to avoid long delays
	The Historian smooth compaction code no longer performs a row count. This 
	prevents long delays during smoothing by avoiding Select Count(*) calls. 

Display Server

21772: Extra-bold font in Firefox fixed
	In the previous release, objects using font index 7 (sans-serif bold) would 
	appear extra bold in some versions of Firefox if the display server was 
	configured to use the extended font feature with arimob.ttf assigned to font 7. 
	This has been fixed. 

21853: Fixed an issue with small numbers not updating to zero in the thin client
	In previous releases, the value displayed in an obj_rect_ilv object would not 
	change if the previous value was greater than zero and less than one, and a value 
	of zero was applied. This problem occurred only in the thin client and is now 
	fixed. 

Scripts

21714: Added Unix scripts to create .war files for a given solution package
	The script make_package_wars.sh has been added to the rtvapm distribution. Like 
	make_package_wars.bat, it is used to create an initial set of war files for a 
	given solution package. The war files are created in the <package>/webapps 
	directory. After they are created, update_wars.bat/sh should be run to update 
	them with the correct port numbers. 
	
	The scripts should be run from the <package>/webapps directory. They take the 
	package name as argument, e.g. "make_package_wars.sh bwmon". 

21771: Fixed an issue where ports were misidentified
	The rtvapm start/stop/status scripts, when testing the ports of a given server, 
	would incorrectly identify a port as "taken" whose number contained the server's 
	number with a leading or trailing digit. (For example finding 33675 in use and 
	saying 3675 is taken.) This has been corrected. 

Solution Package

Solace

21697: Fixed an issue preventing Tomcat from stopping cleanly
	A bug that prevented Tomcat from stopping cleanly on UNIX and Linux systems has 
	been fixed. The CATALINA_PID variable is now defined in the Tomcat setenv.sh 
	script for these systems. 
	Also, the start_tomcat.sh script requirement of JAVA_HOME being set in the 
	environment has been changed to require Java available in the PATH. This change 
	will allow starting RTView processes at startup before the user environment has 
	been set. 

21786: All Endpoints Table display enhanced with two new check boxes
	Two new check boxes to filter by Expired and Down have been added to the All 
	Endpoints Table display. 

21787: All VPNs Table display enhanced with two new check boxes
	Two new check boxes to filter by Expired and Disabled have been added to the All 
	VPNs Table display. 

21788: All Clients Table display enhanced with two new check boxes
	The All Clients Table display has been enhanced by adding two check boxes to 
	filter by Expired and Internal. By default, Expired and Disabled check boxes are 
	unchecked, meaning that only non-expired of the Primary Type Clients are shown. 
	When checked, all Clients, expired and non-expired as well as Primary and 
	Internal will be respectively shown. 

21789: All CSPF Neighbors Table display enhanced with two new check boxes
	Two new check boxes for State Ok and Expired have been added to the All CSPF 
	Neighbors Table display. By default both check boxes are unchecked, meaning that 
	all non-expired CSPF Neighbors are shown. When Ok is checked, only CSPF Neighbors 
	with State=Ok are shown. When Expired is checked all CSPF Neighbors, expired and 
	non-expired are shown in the table. 

21790: All Bridges Table display enhanced with two new check boxes
	Two new check boxes for "Disabled" and "Expired" have been added to the All 
	Bridges Table display. By default the "Expired" check box is unchecked, meaning 
	that only non-expired Bridges are shown, and the "Disabled" check box is checked, 
	which shows all Bridges regardless of their Admin State. When "Disabled" is 
	unchecked, only enabled Bridges with Admin State=Enabled are shown. When 
	"Expired" is checked, all expired Bridges are shown in the table, in addition to 
	the non-expired Bridges. 

21799: CSPF cache enhanced with Ingress/Egress metrics
	Ingress and Egress metrics for CSPF Neighbor Msg Routers have been added.
	

21800: New CSPF Ingress/Egress metrics are now available
	Ingress/Egress metrics for CSPF Neighbor Msg Routers have been stored in history 
	from the CSPH Neighbor cache. 
	The table creation SQL statement for supported platforms is located in 
	solmon/dbconfig directory. The name of the table is SOL_CSPF_NEIGHBOR. 
	By default, data is being stored in history for this table. To disable storage of 
	historical data, edit the sample.properties file and uncomment the following 
	property: 
	collector.sl.rtview.sub=$SOL_CSPF_NEIGHBOR_TABLE:''

21801: SolAppliances cache enhanced with two new metrics
	Two new metrics have been included in the SolAppliances cache. Host Address and 
	Connected. The later keeps track of the connection state of the Msg Router. 

21803: Message Router Summary display enhanced with Host Address
	The Host Address has been added to the header of the Msg Router Summary display.

21804: EM enhanced with a new alert
	A new alert,SolMsgRouterNotConnected, has been added. This alert will be executed 
	when the Msg Router is not ready for collecting monitoring data. 

21807: SOLMON tables functionality enhanced
	All tabular displays now select a row by single clicking and drill down to the 
	corresponding summary by double clicking. The enhanced displays are the 
	following: 
	- Message Routers->All Message Routers Table 
	- Neighbors-> CSPH Neigbors Table 
	- VPNs->All VPNs Table 
	- Clients->All Clients Table 
	- Bridges-> All Bridges Table 
	- Endpoints-> All Endpoints Table 
	- Capacity Analysis-> All Msg Routers Capacity

21808: All Msg Routers Heatmap display has been enhanced
	Two check boxes, "Connected" and "Expired", have been added to the All Msg 
	Routers Heatmap display. 

21809: Enhanced some displays to correctly align their contents
	The Msg Router and the Capacity displays for the corresponding menu tags have 
	been enhanced to correctly align their contents. 

21810: Enhanced EM with a new page for CSPF Neighbors
	The CSPF Neighbor Msg Router displays have been organised under a new menu tab 
	named Neighbors. 

21812: Msg Router VPN Activity display has been enhanced
	The Msg Router VPN Activity display has been enhanced to show the most active 
	VPNs sorted by Client Connections, Ingress/Egress bytes / sec and Pending Msgs. 
	The number of VPNs shown is adjusted to the height of the window. 

21814: EM enhanced with new metrics
	In Msgs /sec and Out Msgs / sec have been added to the SOLMON-MSGROUTER CI Type 
	as Key Metrics. 

21817: Trend Value precision is now one decimal value in Client Summary display
	The precision of the trend values has been changed to one decimal value in the 
	Client Summary display. 

21827: Enhanced EM by standardizing colors across multiple displays
	The following displays have been improved to follow RTView EM standards on color 
	trends: 
	- Message Router Capacity Summary
	- Message Router Capacity Trends
	- Single Message Router Summary
	- Single Bridge Summary
	- Single Client Summary
	- Single Endpoint Summary
	- Single VPN Summary