Kbase P123427: How to upgrade to the 3.1B01+ version of remote monitoring ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2009 |
|
Status: Verified
GOAL:
How to upgrade to the 3.1B01+ version of remote monitoring ?
GOAL:
How to perform an installation of Service pack or TFix for OpenEdge Management remote monitoring ?
GOAL:
What steps are necessary to upgrade to the latest version of OpenEdge Management remote monitoring?
FACT(s) (Environment):
OpenEdge Management 3.1B
OpenEdge 10.1B
OpenEdge 10.1A
OpenEdge 10.0B
Progress 9.1E
FIX:
3.1B01 and 10.1B01 Service Packs contain an upgrade of OE Management remote monitoring from SonicMQ 5.0.1 to SonicMQ 6.1.
Hot-fixes: 10.1A02 TFIX 21, 10.0B05 TFIX 34 and 9.1E04 TFIX 20 provide same functionality.
[ Steps to follow when installing 10.1B01/3.1B01 on the OpenEdge Management machine ]
1) stop AdminServer and all 10.1B/3.1B processes
2) proenv -> "fmconfig -disable"
3) delete MFConfigurationElements.xsd from WRKDIR (working directory)
4) delete DLC/properties/management.propeperties
5) run "FATHOM/SonicMQ/uninstall.bat" or "FATHOM/SonicMQ/uninstall.sh -console" (based on Windows/Unix platform)
6) delete FATHOM/SonicMQ and FATHOM/sonic_setup directories + delete FATHOM/SonicMQ.ini
7) install 10.1B01
8) install 3.1B01
9) proenv -> "fmconfig -enable"
10) start AdminServer
Note: For the preceding steps, if the installation has never (not even once) been previously enabled for a remote monitoring, ignore steps 2-6.
[ Steps to follow when installing 10.1B01/10.1A0221/10.0B0534/9.1E0420 on the remote machines ]
1) stop all Progress/OpenEdge processes related to the installation
2) proenv -> "fmconfig -disable"
3) delete following files in WRKDIR: Fathom1.*.cache folder, MFConfigurationElements.xsd, *.import
4) delete following files in DLC: MFConfigurationElements.xsd, container.xml
5) delete DLC/properties/management.properties
6) install the appropriate SP or TFix on the top of your installation (10.1A02, 10.0B05 or 9.1E04 are mandatory to install first, if not yet installed)
7) fmconfig -update -host <oemhost>
8) start the remote AdminServer.
Note: For the preceding steps, if the installation has never (not even once) been previously enabled for a remote monitoring, ignore steps 2-5.