=======================================================================

	Solace PubSub+ Monitor - Manual Upgrade Notes

=======================================================================

 ? -> 5.3.x

        For notes on upgrading from versions older than 5.3, please
        refer to the User Guide.
				
 5.3.x -> 6.0.x

	There are no manual upgrade steps required.

 6.0.x -> 6.1.x

	- If you created custom displays, custom alerts or custom 
	caches in a version previous to 6.1.0, you will need to get a 
	new KEY from SL to license their use in the current release. 

 6.1.0 -> 6.1.1

        There are no manual upgrade steps required.

 6.1.1 -> 6.1.2

        The syntax used in a Log4j properties file was changed completely
	by Apache in version 2. The sl.log4j.properties file distributed
	with RTView has been changed to use the version 2 syntax. If, in
	previous RTView versions, you customized that file or specified
	your own custom log4j properties file (e.g. using the "log4jprops"
	option), you'll need to remake those customization using the
	version 2 syntax. However, in this release the default Log4j
	configuration is more sophisticated than the default in prior
	releases, and is more likely to be useful in production deployments.
	So customization may no longer be needed. Please see the Release
	Note for details.

 6.1.x -> 6.2.x

        There are no manual upgrade steps required.

 6.2.x -> 6.3.x

        For improved security the following displays have been moved from
        assets/packages/common to assets/packages/admin:

        Alert Administration (rtv_alerts_admin_table.html)
        Alert Overrides Admin (rtv_alerts_admin_overrides.html)
        Component Alert Configuration (rtv_alerts_admin_detail.html)
        CMDB Admin (rtv_cmdb_admin.html, rtview-central only)

        Any existing browser bookmarks to those displays should be updated or recreated.

 6.3.x -> 6.4.x

	The Solace monitor now filters out all Queues started with the #P2P/QTMP/ prefix. 
	If you need to monitor these, navigate in the Configuration Application to 
	Solace > Data Collection > Filter Out Regular Expressions. Change the value of 
	the Queue field to: !(.*)

	Data Historian

	- New database tables SOL_VPN_CAPACITY and SOL_VPN_CAPACITY_EXT have been added 
	for the Solace Solution package. The first is enabled by default. 

	Users should refer to the SQL schemas under rtvapm/solmon/dbconfig for appropriate
	table creation syntax.

	- New optional database table SOL_BRIDGE_TOTALS has been added for Oracle
	and MySQL databases. Users should refer to the SQL schemas under 
	rtvapm/solmon/dbconfig for appropriate table creation syntax.

	- It is now possible to customizate the table name SOL_VPN_TOTALS.  If you have 
	an existing table named SOL_VPN_TOTALS with historical data you wish to keep, 
	ask your DB Admin to rename SOL_VPN_TOTALS to the new customized name.

	- There have been columns added to existing tables. Reference the below syntax for 
	altering existing tables.

	Oracle:
	ALTER TABLE "SOL_APPLIANCE_CAPACITY" ADD ("egress-flow-count-per-cent" REAL)
	ALTER TABLE "SOL_MESSAGE_SPOOL" ADD ("egress-flow-count" REAL)
	ALTER TABLE "SOL_VPN" ADD ("avg-spool-msg-size-in-kb" REAL, "cur-spool-usage-in-mb" REAL, "high-water-mark-in-mb" REAL, "connections-util-percent" REAL) 

	MySQL:
	ALTER TABLE "SOL_APPLIANCE_CAPACITY" ADD "egress-flow-count-per-cent" DOUBLE;
	ALTER TABLE "SOL_MESSAGE_SPOOL" ADD "egress-flow-count" DOUBLE;
	ALTER TABLE "SOL_VPN" ADD "avg-spool-msg-size-in-kb" DOUBLE;
	ALTER TABLE "SOL_VPN" ADD "cur-spool-usage-in-mb" DOUBLE;
	ALTER TABLE "SOL_VPN" ADD "high-water-mark-in-mb" DOUBLE; 
	ALTER TABLE "SOL_VPN" ADD "connections-util-percent" DOUBLE;

	SQLServer:
	ALTER TABLE [SOL_APPLIANCE_CAPACITY] ADD [egress-flow-count-per-cent] FLOAT;
	ALTER TABLE [SOL_MESSAGE_SPOOL] ADD [egress-flow-count] FLOAT;
	ALTER TABLE [SOL_VPN] ADD [avg-spool-msg-size-in-kb] FLOAT;
	ALTER TABLE [SOL_VPN] ADD [cur-spool-usage-in-mb] FLOAT;
	ALTER TABLE [SOL_VPN] ADD [high-water-mark-in-mb] FLOAT; 
	ALTER TABLE [SOL_VPN] ADD [connections-util-percent] FLOAT; 

	DB2:
	ALTER TABLE "SOL_APPLIANCE_CAPACITY" ADD "egress-flow-count-per-cent" DOUBLE;
	ALTER TABLE "SOL_MESSAGE_SPOOL" ADD "egress-flow-count" DOUBLE; 
	ALTER TABLE "SOL_VPN" ADD "avg-spool-msg-size-in-kb" DOUBLE;
	ALTER TABLE "SOL_VPN" ADD "cur-spool-usage-in-mb" DOUBLE;
	ALTER TABLE "SOL_VPN" ADD "high-water-mark-in-mb" DOUBLE; 
	ALTER TABLE "SOL_VPN" ADD "connections-util-percent" DOUBLE;