Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight 7.1.0 - Upgrade Guide

Understand product versions Best practices Upgrade the Foglight Management Server Upgrade the Foglight Agent Manager Upgrade the Database 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

Prepare for an upgrade

Preparing for a Foglight upgrade is straightforward, but may be time-consuming. Before upgrading you should consider the following:

1
If you are upgrading the Management Server, back up your Performance Investigator (PI) repository.
2
Support recommends restarting the Foglight Agent Managers (FglAM) prior to the upgrade. This can be accomplished through Windows services or the Linux/Windows command line, or by utilizing the restart functionality in the Agent Managers panel. Doing so can help ensure that there are no issues with specific agents that could later impede the efficient shutdown of the Agent Manager in the background during cartridge upgrades.
If the Agent Manager does not shut down and restart promptly, please contact Support for assistance in reviewing the FglAM log file for potential shutdown issues caused by stuck process threads.
3
It is also recommended to stop the Foglight service in order to shut down the Foglight application. The wizard performs this task automatically, but manually shutting it down is considered a better practice.
4
Create a support bundle from your Management Server. For information on how to do this, see the “Managing Support Bundles” section in Foglight Administration and Configuration Guide.
5
If you are upgrading the Management Server, back up the file system in which Foglight is installed. For information on how to do this, see the “Backing up Foglight” section in the Foglight Administration and Configuration Help.
6
If you are upgrading the Management Server, back up your database. For information on how to do this, see the “Backing up Foglight” section in the Foglight Administration and Configuration Help.

Upgrade order

 
* 
IMPORTANT: Consult the sections above to decide which components, if any, you will be upgrading.

Foglight components should be upgraded in the following order:

1
Some cartridges must be upgraded prior to upgrading the Management Server. For more information, see Components compatibility.
2
Management Server, if necessary
3
Cartridges, if necessary
4
Agent Manager, if necessary
5
New agents, if necessary

Step 2 may require some time, because agents may need time to reconnect.

In some cases, a successful step 2 may require one or more cartridge upgrades. Where special instructions are required, they are documented in this guide.

Only perform steps 4 and 5 after the system has stabilized.

Where to find upgrade information

For information on how to upgrade the Management Server, see Upgrade the Foglight Management Server.

For information on how to upgrade the Agent Manager, see Upgrade the Foglight Agent Manager.

For information on how to upgrade Foglight cartridges, see:

•
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

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.

Starting with Foglight 7.1, the JRE needs to be Java 17. If you want to 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:

•
The new JRE must be on the same major release branch, and the upgrade must update no more than the 4th set of digits in the version number (for example, 17.0.x).
•
You must use the following JRE upgrade process for the Agent Manager:
a
Stop the Agent Manager.
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, 17.0.8).
c
Unpack the new JRE into that directory.
d
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.
a
Stop the Management Server.
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.
e
Restart the Management Server.
•
For problem replication:
a
You must advise Quest technical support that you are on a non-standard JRE.
b
Quest will first try to reproduce problems on our bundled version of the JRE.
c
Quest will then try to reproduce problems on the version of the JRE to which you upgraded.
d
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.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation