지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight 6.3.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

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.

Run AIX Agent Manager clients with command-line parameter
'-Dcom.ibm.jsse2.overrideDefaultTLS=true'.
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 or higher
Foglight for DB2 LUW: must be upgraded to version 5.7.5.50 or higher
Foglight for SQL Server: must be upgraded to version 5.7.5.50 or higher
Foglight for Oracle: must be upgraded to version 5.7.5.50 or higher
Foglight for Sybase: must be upgraded to version 5.7.5.50 or higher
Foglight for Application Operations: must be upgraded to version 5.9.8.5 or higher
Foglight for Java EE Technologies: must be upgraded to version 5.9.12 or higher
Foglight for Microsoft .NET: must be upgraded to version 5.9.12 or higher
Foglight Transaction Manager: must be upgraded to version 5.9.13 or higher
Foglight APM: must be upgraded to version 5.9.11.1 or higher
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:

Host services compatibility

A new installation of, or upgrade to, version 6.3.0 of the Management Server does not automatically create HostServices for every discovered host. If you want that functionality, install and enable the Service Compatibility Cartridge (<foglight_home>/compat/cartridge/Core-HostServices-Compatibility-6_3_0car).

If you have already installed and enabled the Service Compatibility Cartridge through a previous upgrade to or after a fresh installation of version 5.5.2, 5.5.4, 5.5.5, or 5.5.8, then the cartridge continues to be active after an upgrade to version 6.3.0, and this manual step is not necessary.

Start the embedded Agent Manager

The Management Server version 6.3.0 includes an embedded Agent Manager version 6.3.0. After installing the new Management Server 6.3.0, the embedded Agent Manager starts up by default.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택