Foglight 5.9.3 - Upgrade Guide

In the jre subdirectory of your Agent Manager installation directory, create a new directory named for the version number of the JRE to which you want to upgrade, with components separated by periods (for example, 1.8.0.25).

Unpack the new JRE into that directory.

Restart the Agent Manager, which will look for and use the newest JRE available to it.

•

You must use the following JRE upgrade process for the Management Server.

Stop the Management Server.

Rename <foglight_home>/jre to <foglight_home>/jre.bak.

Create a new <foglight_home>/jre directory.

Unpack the new JRE into the new <foglight_home>/jre directory.

Restart the Management Server.

•

For problem replication:

You must advise Quest technical support that you are on a non-standard JRE.

Quest will first try to reproduce problems on our bundled version of the JRE.

Quest will then try to reproduce problems on the version of the JRE to which you upgraded.

If Quest cannot replicate the problem on either the bundled version or the specific version of the JRE to which you upgraded, you may be asked to return our bundled version of the JRE.

Upgrade the Foglight Management Server

This section provides information about the following topics:

•

Migrate to Windows SSO from VSJ SSO

•

Upgrade the Management Server

•

Oracle database users

•

Database changes

Migrate to Windows SSO from VSJ SSO

If you were using the VSJ SSO implementation in earlier versions of Foglight, you must migrate to the new Windows OS-based SSO.

To migrate to Windows OS-based SSO from VSJ SSO:

Make a backup of the vsj.properties file before you upgrade Foglight. You can find this file in the following location:
<foglight_home>/server/default/deploy-foglight/console.war/WEB-INF/vsj.properties

Upgrade Foglight to the latest version.

If there is no keytab file configured in the VSJ SSO, create the keytab file first using the ktpass command, as described in “Configure Active Directory to support Windows Single Sign-on” section in the Foglight online help.

Edit the krb5-auth.config file to set the properties described in the following table.

Table 4. VSJ properties and the corresponding krb5-auth.config properties
vsj.properties	krb5-auth.config
idm.princ	Principal
idm.keytab	Keytab
idm.ad.qualifyUserPrincipal	QualifyUserPrincipal

Edit the krb5.config file. Set the realm name to the vsj.properties idm.realm value.

Upgrade the Management Server

Follow the procedures in this section to upgrade an earlier version of the Management Server to version 5.9.2.


	IMPORTANT: To upgrade from a 5.5.x Management Server to 5.7.1 or later, you must first upgrade to 5.6.2 (or a more recent 5.6.x version), and then to 5.7.1 or later. IMPORTANT: To upgrade from a 5.6.11 Management Server to 5.7.6.x, you must first upgrade to 5.7.1, and then to 5.7.6.x. IMPORTANT: To upgrade from a 5.7.6.x Management Server to 5.9.x, you must first upgrade to 5.7.5.8, and then to 5.9.x.

Ideally, you should create a backup just before performing an upgrade. For more information on creating a backup, see the Foglight Administration and Configuration Help. If you have encounter any problems during the upgrade process, contact Quest Support.

It is important that you see Upgrade a Management Server in a federated environment if you are upgrading the Management Server in a Federated environment.

It is important that you see Upgrade the Management Server in a High Availability (HA) environment if you are upgrading the Management Server in an HA environment.

It is important that you see Upgrade the Management Server with an Oracle RAC database if you are upgrading the Management Server installed with an Oracle RAC database.

To upgrade the Management Server:


	NOTE: Only support the upgrade from the Management Server 5.7.5.8. Before upgrading the Management Server to 5.9.x, make sure to upgrade your server to 5.7.5.8 first. NOTE: If there are Foglight End User agents, deactivate them before you upgrade the Management Server. Once you have upgraded all that you plan to (for example, the Management Server, the Agent Manager, any cartridges, any agent packages, and the software on the agent hosts), you can then reactivate the End User agents.

Stop the Management Server. The Management Server may take a few minutes to shut down. Verify that all Management Server processes have stopped before starting the installer.

To ensure that all processes have been stopped, perform one of the following checks:


	NOTE: The default installation folder is included in the commands. If Foglight is installed in an alternate location at your site, please substitute the appropriate folder name for the default installation folder name.

UNIX®:

ps -ef | grep Foglight


	NOTE: If Foglight is running as a daemon, this command displays that information instead of the path to the Management Server executable.

Windows®:

Use the Task Manager to verify that the fms.exe process has stopped.


	NOTE: If your Management Server uses an external database, do not stop the database. It is important that it continue to run during the upgrade.

If you have customized the Management Server configuration files (such as <foglight_home>/config/server.config or <foglight_home>/config/log.config, <foglight_home>/config/jgroups-config.properties, or <foglight_home>/config/federation.config), back up these files so that you can verify the correct ports are configured after the upgrade is completed. If you have never customized these files, proceed to the next step.

Upgrade the following cartridges before a Management Server upgrade.

•

Foglight for VMware: must be upgraded to version 5.7.3

•

Foglight for DB2 LUW: must be upgraded to version 5.7.5.50

•

Foglight for SQL Server: must be upgraded to version 5.7.5.50

•

Foglight for Oracle: must be upgraded to version 5.7.5.50

•

Foglight for Sybase: must be upgraded to version 5.7.5.50

•

Foglight for Application Operations: must be upgraded to version 5.9.8.5

•

Foglight for Java EE Technologies: must be upgraded to version 5.9.12

•

Foglight for Microsoft .NET: must be upgraded to version 5.9.12

•

Foglight Transaction Manager: must be upgraded to version 5.9.13

•

Foglight APM: must be upgraded to version 5.9.11.1

Optional: The JRE on disk is replaced completely during a Management Server upgrade. Any existing certificates are retained in $fmshome/state/backup/<previous-fms-version>/jre/lib/security/cacerts.

Your custom settings are restored automatically after upgrade of the Management Server.

Upgrade the Management Server using the appropriate installer. The installer detects the earlier version of the Management Server. Ensure that your Management Server has been upgraded


	NOTE: It is possible to upgrade a 32-bit installation to a 64-bit installation by simply using the 64-bit version of the installer, provided that the OS is 64-bit.

Follow the on-screen upgrade instructions. As mentioned previously, the installer detects the earlier version of the Management Server.

For step-by-step assistance, see the appropriate Foglight Installation and Setup Guide for the database and platform you are running.


	NOTE: The database upgrade may be time-consuming if you have a large topology.


	IMPORTANT: The upgrade checks the permissions on the database’s dbms_lob package. If the check fails, run GRANT EXECUTE ON dbms_lob TO public using the sysdba user ‘sys’ to resolve the issue and then continue with the upgrade.

Known Issue: If you are running an external database, the database upgrade portion of the Management Server upgrade may fail for one of the following reasons:

•

The database connection parameters are incorrect.

•

The database is not running.

The installer explains any problems encountered while upgrading an external database. This step can be canceled by clicking Ignore and continuing.

If, for any reason, the database upgrade cannot be successfully performed within the installer itself, you can perform the database upgrade afterwards by running the following command:

<foglight_home>\bin\foglight_db_upgrade.[bat|sh]


	NOTE: The database upgrade must be performed before you start the Management Server.

Optional: You can upgrade the currently installed cartridges (except for the cartridges listed in Step 3) in one easy step before starting the Management Server. To do this, place the new versions of the cartridges into the folder <foglight_home>/upgrade/cartridge. The cartridges are then installed automatically when the Management Server starts up.


	IMPORTANT: This method of upgrading cartridges is only available in Foglight 5.2.4 and later.


	NOTE: This method of upgrading cartridges does not apply to Foglight for Oracle, Foglight for SQL Server, Cartridge for DB2, or Cartridge for Sybase.

The newly installed cartridges replace their respective older versions and previous versions are deleted, which means you cannot revert back to them.

If you backed up the configuration files mentioned in Step 2, compare the customizations to determine if they are still necessary, especially for the following customization files. If required, reapply these files before starting the Management Server.

•

<foglight_home>/config/server.config

•

<foglight_home>/config/jgroups-config.properties

•

<foglight_home>/config/federation.config

•

<foglight_home>/config/datasource/datasource-oracle.properties

Start the new Management Server by typing the following command:

UNIX®:

./bin/fms --start

Windows®:

<foglight_home>\bin\fms.exe

The ability to send all generated reports to declared email recipients is enabled by default. If you do not want reports to be sent out by default, manually disable the Email Reports Sample rule. For more information on rules, see “Using Foglight Rules to Report on Bottlenecks” in the Foglight Administration and Configuration Guide.

Log into Foglight through the browser interface by entering http://<yourserver>:<port> in your web browser, where <port> is the applicable port at your location (the default is 8080).

After you have logged into Foglight, the Management Server and the Agent Manager both attempt to reach a steady state. Be patient as it will take some time for this to complete. It may also take some time if you have a large topology.


	IMPORTANT: If, after upgrading, you experience unusual or unexpected browser interface behavior (for example, unusual page layout), try logging out of Foglight, clearing the browser’s cache, restarting the browser, and then logging back into Foglight. In most cases, this will correct the problem. In rare cases, proxies and firewalls inappropriately cache JavaScript, and therefore you may need to clear their caches as well.

Look at the Agent Status page (Dashboards > Administration > Agents > Agent Status) to see the number of agents that are connected. Wait until this count reaches a steady state before proceeding. You may need to refresh the page to see the complete list.

Do not stop/start/activate/deactivate any of the agents manually from the Agent Status page while waiting for the count to reach a steady state. If you do, it will increase the time required for the agent connection state to stabilize and, consequently, increase your wait time.

The estimated time for this activity to complete is one hour, depending on the complexity (number of agents) in the environment.

If you encounter any problems while upgrading your Management Server, contact Quest Support for assistance.

For more information, see these topics:

•

Host services compatibility

•

Start the embedded Agent Manager

•

Upgrade a Management Server in a federated environment

•

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