Kbase P147208: Can Fathom Management 3.1C be migrated to OpenEdge Management 10.2A or 10.2B?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/05/2010 |
|
Status: Verified
GOAL:
Can Fathom Management 3.1C be migrated to OpenEdge Management 10.2A?
GOAL:
Can Fathom Management 3.1C be migrated to OpenEdge Management 10.2B?
GOAL:
How to upgrade Fathom Management 3.1C to OpenEdge Management 10.2A.
GOAL:
How to upgrade Fathom Management 3.1C to OpenEdge Management 10.2B.
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge Management
FIX:
There is no update option on the installation of OpenEdge Management 10.2A or 10.2B.
The trended information and the Script Managed (Remote) Databases may be migrated from 3.1C to 10.2A following the two procedures below.
== Upgrading Fathom Management from 3.1C to OpenEdge Management 10.2A or 10.2B ====
When transitioning from Fathom Management 3.1C to OpenEdge Management 10.2X, the following must hold true for this process to work.
1. Fathom 10.2X is to be installed into a different directory than the Fathom 3.1C install and the Fathom 3.1C install must still available.
2. Any needed 10.1C to 10.2X transitions such as copying and updating conmgr.properties has been done.
==== Upgrading Fathom Management 3.1C to OpenEdge Management 10.2A or 10.2B (referred to as 10.2X in the following =======
After installing OpenEdge Management 10.2A or 10.2B (Fathom) against 10.2X version and doing the initial configuration for OpenEdge Management 10.2X, replace the default 10.2X database with the working 3.1C database.
Example:
1. Make a backup of the OpenEdge Management configuration by running fathom -dump from the OpenEdge Management Environment.
This must be done online in Release 3.1C, while OpenEdge Management is running.
fathom -dump $OE-FATHOM102X/config/fathom.xml
2. Stop all resource running under the 10.1C Adminservice using the tool that is managing the resource or via the command line.
ie: appServers, database, name server etc.
10.1C proenv> dbman -stop -all
3. Shutdown the 10.1C and 10.2x AdminServer
proadsv -stop
4. Disable OpenEdge Management 3.1C remote monitoring by running fmconfig disable from the OpenEdge 10.1C proenv environment.
fmconfig -disable
5. Change to the OpenEdge Management db directory.
cd $FATHOM31C/db
6. Truncate the bi file of the 3.1C fathom database. (It should be shutdown at this time, if it is not issue a "proshut fathom -by" first.)
From the 10.1C proenv> proutil fathom -C truncate BI -G 0
7. Backup the Fathom 3.1C database in the $FATHOM31C/db directory.
probkup fathom $OE-FATHOM102X/db/fathom31c.bk
8. Delete the $OE-FATHOM102X/db database that was created when initially configuring the OpenEdge Management 10.2X(Fathom) installation by issuing a prodel command.
From the $OE-FATHOM102X/db directory issue the following command:
prodel fathom
9. Restore the fathom database using the backup created in step 7 above in Fathom 3.1C.
- cd $OE-FATHOM102X/db directory
prorest fathom fathom31c.bk
10. Copy the smdatabase.properties file from 10.1C. $DLC/properties to the 10.2X $DLC/properties folder to move all local scripted databases to the new installation for OpenEdge
Management 10.2X.
11. The configured resources in the OpenEdge Management 3.1C database need to be made available or known to OpenEdge Management 10.2X. Since the installation path is different the
$OE-FATHOM102X/config/fathom.xml file that was created in step 1 above, must be edited to reflect the correct paths for OpenEdge 10.2x and OpenEdge Management 10.2X installation and working directory paths.
Do a global search/replace on the directory specifications from the Fathom 3.1C install and working paths to the corresponding path in the new OpenEdge and OpenEdge Management 10.2X installations.
12. Copy the newly edited 3.1C fathom.xml file to the $OE-FATHOM102X/config/ directory, overwriting the existing fathom.xml file.
13. Delete the existing $OE-FATHOM102X\wrk_oemgmt\cachedata\fathomdatacache.o* files, new ones will be regenerated from the edited $FATHOM102X/config/fathom.xml file when the 10.2X
AdminServer is next started.
14. The Fathom 3.1C graph cache database can be ignored and left behind.
15. If the Fathom working directory is to be copied over to have easy access to the previous logs and reports, the graphcache, cachedata and MFConfigurationElements.xsd fileswill need to be omitted.
16. Any remote systems will need to perform fmconfig -update to the newly installed Fathom. From the proenv environment on the remote system run the following command:
fmconfig -update -host <host-name-where-OE-Mgt-10.2x-is-installed>
17. Any custom Perl jobs or report scripts that had been created in Fathom 3.1C will need to be accounted for individually and moved over.
18. Start 10.2B Adminserver and OE Management 10.2B.
This completes the process of upgrading Fathom Management 3.1C to OpenEdge Management 10.2X
.