Understand product versions
Best practices
Foglight Management Server
Foglight Agent Manager
Database cartridges
Upgrade the Foglight Management Server
Foglight for Azure SQL Database
Foglight for DB2 LUW
Foglight for Oracle
Foglight for SQL Server
Foglight for SAP ASE
Foglight for MySQL PI
Foglight for PostgreSQL PI
Infrastructure Management cartridges
Integration cartridges
Virtualization cartridges
Upgrade use cases
Scenario 1 — New release
Scenario 2 — New Management Server features or defect fixes
Scenario 3 — Agent Manager client-side feature dependency or defect fix
Dependency and compatibility matrix
Prepare for an upgrade
Upgrade order
Where to find upgrade information
Update the Java Runtime Environment
Migrate to Windows SSO from VSJ SSO
Upgrade the Management Server
Upgrade the Foglight Agent Manager
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
Upgrade the Management Server with an Oracle RAC database
Oracle database users
Database changes
Upgrade the Agent Manager
Upgrade concentrators
Upgrade installations with multiple state instances
Upgrade a 32-bit FglAM installation on a 64-bit operating system
Agent Manager upgrade issues
Upgrade the Database cartridges
Upgrade Foglight for DB2 LUW
Upgrade Foglight for Oracle
Upgrade Foglight for SQL Server
Upgrade Foglight for SAP ASE
Upgrade Foglight for Azure SQL Database
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
Upgrade a Management Server in a federated environment
The procedure for upgrading a Federation Master and Federated Child(ren) is the same as described in Upgrade the Management Server. There are a few items in particular that should be noted when working in a Federated environment.
Federation compatibility
Upgrade sequence
To upgrade your Federation servers to 7.3.0, follow the appropriate procedure below.
|
NOTE: Configuration of SecurityToken through the federation.config file (adopted in Foglight 5.7.5.8 and before) was removed in Foglight 5.9.x. Therefore, configuring an SSL for Federation is required when you upgrade the Federation environment to version 7.3.0, if your Federation environment configures SecurityToken before. |
|
4 |
(Optional) If you have enabled SecurityToken in the configuration file ($fmshome/config/federation.config), you must configure an SSL for communication on Federation Master and Children. For more information, see the Security settings section in the Foglight Federation Field 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:
|
2 |
If you are going to upgrade the Management Server to 7.3.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. |
|
3 |
All HA-related communications have been encrypted after upgrading your server to 7.3.0 . For more information about the HA encryption, refer to the Security considerations for HA configuration section in the Foglight High Availability Field Guide. |