Chat now with support
Chat with Support

Foglight 5.9.5 - 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

Federation compatibility

A version 5.9.x Federation Master requires that all Federated Children be upgraded to version 5.9.x as well.

Upgrade sequence

To upgrade your Federation servers to 5.9.x, follow the appropriate procedure below.

 
* 
IMPORTANT: You must upgrade your Federation Master before the Federated Children. Otherwise, the Federation Master may fail to start after an upgrade.

 

* 
NOTE: Configuration of SecurityToken through the federation.config file (adopted in Foglight 5.7.5.8 and before) has been removed in Foglight 5.9.x. Therefore, configuring an SSL for Federation is required when you upgrade the Federation environment to version 5.9.x, if your Federation environment configures SecurityToken before.
When upgrading the Management Server:
1
Shut down and upgrade the Federation Master.
2
Shut down and upgrade each Federated Child, one by one.
3
Restart the Federation Master.
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.
5
Restart the each Federated Child, one by one.

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:

1
All HA members should be stopped before any of them is upgraded. Each HA member should then be upgraded individually and sequentially.
2
If you are going to upgrade the Management Server to 5.9.x 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 5.9.x.For more information about the HA encryption, refer to the Security considerations for HA configuration section in the Foglight High Availability Field Guide.
4
Foglight for Automation is not supported when Foglight is configured to use the Federation Master or High Availability features.This limitation will be addressed in a future release. For more information, see the Foglight Release Notes.
 
* 
NOTE: If you are upgrading cartridges in an HA environment, see Upgrade cartridges in a High Availability environment.

Upgrade the Management Server with an Oracle RAC database

This section provides instructions for upgrading Oracle® RAC-based installations and any other environments where the Management Server oracle-ds.xml files were customized. The oracle-ds.xml file is replaced by the datasource-oracle.properites file in the Management Server 5.9.x, so the Management Sever merges the connection URL and connection properties during the upgrade.

If you encounter the warning message “A special configuration has been found in <backup_oracle_datasource>, please manually merge your configuration from this file to <new_oracle_datasource> and then click Next to continue with the upgrade.” during the upgrade, open the backup of $fmshome/state/backup/<version>/server/jboss/conf/oracle-ds.xml where lists the configured connection properties, and then add these connection properties manually to the $fmshome/config/datasource/datasource-oracle.properties file. For example, you see the following line in the oracle-ds.xml file, <connection-property name="oracle.jdbc.implicitStatementCacheSize">${oracle.jdbc.implicitStatementCacheSize:50}</connection-property>”, open the datasource-oracle.properties file and add this line “db.oracle.jdbc.implicitStatementCacheSize=50”.

* 
NOTE: Make sure to add the db. prefix before the original connection-property name, when you add the connection properties in the new datasource-oracle.properties file.
To upgrade the Management Server with an Oracle RAC database:
1
Shut down the Management Server.
2
Save the oracle-ds.xml and server.config files.
* 
TIP: The Management Server backs up the previous oracle-ds.xml and server.config files after the upgrade. You may find the backup files under $fmshome/state/backup/<version>/server/jboss/conf/oracle-ds.xml and $fmshome/state/backup/<version>/config/server.config.
3
Run the upgrade installer.
4
Check the Management Server logs for upgrade-related errors.
5
If successful, restart the Management Server with the usual options.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating