Chatee ahora con Soporte
Chat con el soporte

Foglight 5.9.3 - Upgrade Guide

Understand product versions Best practices Upgrade the Foglight Management Server Upgrade the Foglight Agent Manager Upgrade the Application Monitoring cartridges Upgrade the Database cartridges Upgrade the End User Management cartridges Upgrading the Infrastructure Management cartridges Upgrade the Integration cartridges Upgrade the cartridges in a federated or High Availability (HA) environment Appendix: Deploying an agent package using the browser interface

Update the Java Runtime Environment

Both the Management Server and the Agent Manager require a Java® Runtime Environment. Quest Software Inc. tests and bundles each Foglight release with versions of the JRE that are compatible with the Management Server and the Agent Manager. Quest audits the security bulletins from Oracle® that are related to those versions of the JRE. If Quest determines that any of the bulletins are applicable to the Management Server or Agent Manager code, Quest releases a security update with the necessary fixes incorporated.

Quest recommends that you use the JRE versions bundled with the Foglight release, because Quest cannot guarantee that other versions of the JRE will perform correctly. However, Quest recognizes that you may have particularly stringent security requirements that require you to use a different version of the JRE.

If you must upgrade a version of the JRE, Quest will make the effort, in good faith, to support the upgrade, as long as it meets the following guidelines:

b
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).
b
Rename <foglight_home>/jre to <foglight_home>/jre.bak.
c
Create a new <foglight_home>/jre directory.
d
Unpack the new JRE into the new <foglight_home>/jre directory.

Upgrade the Foglight Management Server

This section provides information about the following topics:

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.

1
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
3
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.
4
Edit the krb5-auth.config file to set the properties described in the following table.

Principal

Keytab

QualifyUserPrincipal

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

Upgrade the Management Server

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.

Use the Task Manager to verify that the fms.exe process has stopped.
2
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.
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
4
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.
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:
<foglight_home>\bin\foglight_db_upgrade.[bat|sh]
7
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.
8
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>\bin\fms.exe
11
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).
12
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.

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

For more information, see these topics:

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación