OpenEdge Management Remote Monitoring upgrade - summary of changes
What are the changes to Remote Monitoring in OpenEdge Management
How to do a Rolling upgrade of OpenEdge Management

OpenEdge Management internal upgrade to embedded Sonic 6.1

OpenEdge Management has the ability to monitor remote databases (containers). The initial implementations of this product rely on Sonic 5.0.1 for connectivity to remote sites, and the monitoring paradigm relies on continuous connectivity, i.e. loss of connectivity is an error condition that is generally interpreted as the remote database (container) being down. Sonic 5.0.1 had known problems in connectivity, and had not been stable in the OE Management context.

1.   This upgrade to the embedded Sonic 6.1 infrastructure requires that all containers to be monitored must also be using the Sonic 6.1 embedded product. Remote Containers that are not using Sonic 6.1 cannot be monitored. If you attempt to monitor a container that is not using Sonic 6.1, fmconfig will raise the following error message:
 
This upgrade is available for OpenEdge 10.1B01 and later (i.e. Service Pack 1), as well as in Hotfix form for Progress 9.1E04, OpenEdge 10.0B05, and OpenEdge 10.1A02. The hot fixes are available on the ESD download pages for OpenEdge Management 3.1B01, OpenEdge 10.1B01, and OpenEdge Replication 10.1B01 or by contacting Technical Support.

For Remote Containers, this upgrade means:

• 10.1B01/3.1B01 will no longer be able to monitor 10.0A or 10.1B FCS remote installations. The solution for that case is to upgrade to 10.1B01.
• Remote monitoring of 9.1E04, 10.0B05, or 10.1A02 remote installations will only be possible with 10.1B01/3.1B01 and hotfixes on the top of 9.1E04, 10.0B05, or 10.1A02 respectively.

2.  Since Hotfixes are cumulative for each platform and release, all future hotfixes for 9.1E04, 10.0B05, and 10.1A02 will therefore include the Sonic 6.1 upgrade for OpenEdge Management. If a later hotfix is applied to a remote system in the future, it can only be remotely monitored with OpenEdge Management 3.1B01/10.1B01 (see the error message above). A rolling upgrade white paper for OpenEdge Management is available which walks through the steps in transitioning remote monitoring to the new 3.1B01/10.1B01 release. The paper outlines how to do an incremental transition, i.e. all remote monitored systems do not need to be upgraded at the same time.

Summary of Changes:

• In order to improve connectivity, this service pack includes a replacement of the Sonic 5.01 embedded product with the newer Sonic 6.1 embedded product
• There are no UI or install changes
• There are no functional changes in OE Management or the AdminServer
• There is no dump and load needed

Completing the Upgrade after Service Pack (or hotfix) Installation:

After the service pack (or hotfix) is installed, the fmconfig utility must be run prior to use of OpenEdge Management.

Before running fmconfig -update:

1. Delete the vpd.properties file, if it exists. fmconfig will fail if there is a pre-existing vpd.properties file.
2. fmconfig -update must be executed as user root on Unix systems and as a user with Administrator permissions in Windows systems.

Managing the Upgrade Process (Unix and Linux Consoles)

For some installations, it is not practical to upgrade all OpenEdge Management managed systems at the same time. 
On Unix and Linux systems, it is possible to have multiple OpenEdge Management consoles on the same system.
On Windows, an additional PC will be needed for the additional console instead of 2 consoles on the same box (due to registry constraints).
With the ability to support several consoles, maintain one as the current console that monitors and manages prior remote containers that rely on Sonic 5. Establish a second console with the upgrade to Sonic 6.1 (i.e. this service pack or hotfix release). Use this second console to monitor containers that are upgraded to the corresponding Sonic 6 infrastructure.  With 2 consoles, all containers do not need to be upgraded at the same time.  Configure the new console first, then add remote containers as opportunity permits; moving containers to the new console after upgrades.

The rolling upgrade whitepaper (see below) is also available in the OpenEdge Management Library on PSDN and is included on the top level of the 3.1B Service Pack install media.

How to do a Rolling Upgrade of OpenEdge Management

This document shows how to set up and use the multiple consoles to upgrade installations of OpenEdge Management. It is possible to run several instances of OE Management 3.0A/3.1B remote monitoring console on a single Linux or Unix system (the Windows registry prevents this on Microsoft systems), and this technique can be used to support a phased set of updates to remote OpenEdge Management locations.

OpenEdge 10.1B01 and OpenEdge Management 3.1B01 needs to be installed on the Monitoring Container (OEM), in addition to the present install used to monitor existing remote containers.

When installing / configuring the new installation:

1. An appropriate OpenEdge license (at least single user) for the service pack or hotfix installed
2. Memory available on the management machine and its CPU power
3. TCP/IP port conflicts due to multiple versions of OpenEdge/OE Management

1.  Installation:

• OE 10.1B including SP1 to a new directory
• OE Mgmt 3.1B including SP1 to a new directory

2.   Memory considerations:

• Tne AdminServer (with NS running) requires about 30 MB of memory.
• One OE Management requires an additional 120 MB of memory.
• Each new resource will take up additional 1-2 MB of memory.

3.  Port Conflicts

The following ports are used by OE 10.1B01/OE Mgmt 3.1B01:

• AdminServer port (default 20931)
• Adminport (default 7839)
• NameServer and Unified broker ports
• Database Agent port (default 8839)
• Fathom (jetty) web server port (default 9090)
• Fathom remote monitoring port (default 6835)

To change the ports for the new OEM install:

• AdminServer port and adminport are changeable in DLC/properties/AdminServerPlugins.properties under the [PluginPolicy.Progress.AdminServer] Section by adding following 2 lines

• NameServer and Unified broker ports are changeable in DLC/properties/ubroker.properties or under the Configuration Section of the OE Console
• Database Agent port is changeable in DLC/properties/agent.properties by adding following line

• Fathom (jetty) web server port is changeable in FATHOM/config/fathom.properties by adding/changing the [webserver] Section and adding following line

• Fathom remote monitoring port is changeable when enable remote monitoring: fmconfig –enable -port <value>

New Console Installation steps:
 

1. Let the existing installation use the present (default) values
2. Install OE 10.1B to a new directory including SP1
3. Install OE Management 3.1B to a new directory including SP1
4. Create a fathom.properties file in the new fathom/config directories and define httpport (with different values than the prior install (see above).
5. Copy the $FATHOM/db/fathom.o* files from the old console to the new console (same location)
6. Start the new AdminServer and configure OE Management
7. When configuring “Trend database location”, choose “Store trend data in a remote Fathom database” and fill “Remote database hostname” and “Remote Fathom web server port” accordingly = pointing to the existing OE Management installation
8. Stop the new AdminServer and enable remote monitoring (“fmconfig -enable -port 6836”)

 
Remote Servers can now be bound to the new 3.1B01/10.1B01 installation
 
Remote Container Upgrade Steps:
 

1. Ensure the new Console AdminServer is running and has been enabled for remote monitoring (with fmconfig) and that OE Management has been configured.
2. Stop the (old) AdminServer
3. Run fmconfig -disable on the Remote AdminServer to disable remote monitoring on the Remote AdminServer
4. Apply the service pack (or hotfix) to the remote environment
5. Re-configure remote monitoring with fmconfig -enable -port <portnumber> -host <hostname> matching the port number and hostname specified for the new console
6. Restart the new AdminServer – it will now connect into the new OE Management instead of the old OE Management.  The old OE Management container will remain in the old installation, but will be offline.

Upgraded Containers can now be monitored from the new 3.1B01/10.1B01 installation

As remaining containers are migrated, all you have to do is execute fmconfig-update -port <portnumber> -host  <hostname> where port number and hostname represent the new AdminServer console. Then restart the remote AdminServer.

OpenEdge 11.3 and later:

Starting from 11.3 OEM uses ActiveMQ instead of Sonic for remote monitoring.  The migration from Sonic to ActiveMQ has been made easier, without the need for a lot of manual re-configuration.

• Running fmconfig is no longer required, and
• A 11.3 OEM instance cannot monitor pre 11.3 containers.

References to Other Documentation:

How to do a Rolling Upgrade of OpenEdge Management:
 https://community.progress.com/community_groups/openedge_general/w/openedgegeneral/1490.how-to-do-a-rolling-upgrade-of-openedge-management

Progress Articles:

P123420, What are the mandatory HotFix / Service Pack updates to maintain remote monitoring functionality using OpenEdge Management   
P123427, How to upgrade to the 3.1B01+ version of remote monitoring ?