Consultor Eletrônico

Status: Verified

GOAL:

OpenEdge Management remote monitoring upgrade - summary of changes

GOAL:

What are the changes to remote monitoring in OpenEdge Management

GOAL:

How to do a Rolling upgrade of OpenEdge Management

FACT(s) (Environment):

All Supported Operating Systems
OpenEdge Management 3.1B

FIX:

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.
NOTE 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. You can not monitor containers that are not using Sonic 6.1. If you attempt to monitor a container that is not using Sonic 6.1, the error message in fmconfig
you will see is:

com.sonicsw.ma.mgmtapi.config.MgmtException: Failed to create configuration for
/containers/ferrari1 - Failed to create config bean
/containers/AC10070B-1170195456213-0
This upgrade is available for OpenEdge 10.1B01 and later (i.e. Service Pack 1), as well as in hotfix form for Progress V9.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.
This means that 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.

NOTE 2: Since hotfixes are cumulative for each platform and release, please remember that all future hotfixes for 9.1E04, 10.0B05, and 10.1A02 will therefore include the Sonic 6.1 upgrade for OpenEdge Management. If you apply a hotfix to a remote system in the future, you can only monitor it with OpenEdge Management 3.1B01/10.1B01 (see the error message above). There is a rolling upgrade white paper for OpenEdge Management available and it walks you through the steps in transitioning remote monitoring to the new 3.1B01/10.1B01 release. The paper tells you how to do an incremental transition, i.e. you will not need
to upgrade all remote systems at the same time if you do not want to.

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, be sure to:

* Delete the vpd.properties file, if it exists. fmconfig will fail if there is a pre-existing vpd.properties file.
* 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. In Windows, you will need to use an additional PC 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 your present console that monitors and