Foglight 7.1.0 - Upgrade Guide

Upgrade the Management Server in a High Availability (HA) environment

The procedure for upgrading the servers in an HA environment is the same as described in Upgrade the Management Server. There are a few items in particular that should be noted when working in an HA environment. These are:

All HA members should be stopped before any of them is upgraded. Each HA member should then be upgraded individually and sequentially.

If you are going to upgrade the Management Server to 7.1.0 from version 5.7.5.8 and have enabled TCP in the configuration file ($fmshome/server/jboss/deploy/cluster-service.xml), after the upgrade, the $fmshome/config/jgroups-config.xml file will enable TCP and only merge the previous initial_host of TCPPING. If you change other TCP configurations before, manually merge your configuration. For more information about this configuration, refer to the To tune the Management Server procedure in the Foglight High Availability Field Guide.


	NOTE: After the upgrade, the Management Server backs up the previous $fmshome/server/jboss/deploy/cluster-service.xml file to $fmshome/state/backup/<fms_previous_version>/server/jboss/deploy/cluster-service.xml.

All HA-related communications have been encrypted after upgrading your server to 7.1.0 . For more information about the HA encryption, refer to the Security considerations for HA configuration section in the Foglight High Availability Field Guide.

Foglight for Automation is not supported when Foglight is configured to use the Federation Master or High Availability features.This limitation will be addressed in a future release. For more information, see the Foglight Release Notes.


	NOTE: If you are upgrading cartridges in an HA environment, see Upgrade cartridges in a High Availability environment.

Upgrade the Management Server with an Oracle RAC database

This section provides instructions for upgrading Oracle® RAC-based installations and any other environments where the Management Server oracle-ds.xml files were customized. The oracle-ds.xml file was replaced by the datasource-oracle.properites file in the Management Server 5.9.x, so the Management Sever merges the connection URL and connection properties during the upgrade.

If you encounter the warning message “A special configuration has been found in <backup_oracle_datasource>, please manually merge your configuration from this file to <new_oracle_datasource> and then click Next to continue with the upgrade.” during the upgrade, open the backup of $fmshome/state/backup/<version>/server/jboss/conf/oracle-ds.xml where lists the configured connection properties, and then add these connection properties manually to the $fmshome/config/datasource/datasource-oracle.properties file. For example, you see the following line in the oracle-ds.xml file, <connection-property name="oracle.jdbc.implicitStatementCacheSize">${oracle.jdbc.implicitStatementCacheSize:50}</connection-property>”, open the datasource-oracle.properties file and add this line “db.oracle.jdbc.implicitStatementCacheSize=50”.


	NOTE: Make sure to add the db. prefix before the original connection-property name, when you add the connection properties in the new datasource-oracle.properties file.

To upgrade the Management Server with an Oracle RAC database:

Shut down the Management Server.

Save the oracle-ds.xml and server.config files.


	TIP: The Management Server backs up the previous oracle-ds.xml and server.config files after the upgrade. You may find the backup files under $fmshome/state/backup/<version>/server/jboss/conf/oracle-ds.xml and $fmshome/state/backup/<version>/config/server.config.

Run the upgrade installer.

Check the Management Server logs for upgrade-related errors.

If successful, restart the Management Server with the usual options.

Oracle database users

A Management Server 7.1.0 using an Oracle® database makes use of stored procedures in the Oracle database. When upgrading from a version earlier than 5.6.2 to version 5.6.2 or later, the procedures are created during the upgrade process. To allow the upgrade process to create the stored procedures, a DBA user must first assign the CREATE PROCEDURE privilege to the database user used by Foglight.

To assign the CREATE PROCEDURE privilege to the database user:

•

Execute the following command:

GRANT CREATE PROCEDURE TO <foglight>

where <foglight> is the name of the database user used by the Foglight application

If the upgrade process is run without assigning the CREATE PROCEDURE privilege to the Oracle database user, the database upgrade will fail with the following error:

The Oracle database user has not been assigned the CREATE PROCEDURE privilege.

Once the CREATE PROCEDURE privilege is assigned to the database user, the database upgrade process can be run manually by invoking the foglight_db_upgrade script.