Kbase P115816: Can Fathom Management 3.0A be migrated to OpenEdge Management 3.1A?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/05/2009 |
|
Status: Verified
GOAL:
Can Fathom Management 3.0A be migrated to OpenEdge Management 3.1A?
GOAL:
How to upgrade Fathom Management 3.0A to OpenEdge Management 3.1A.
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge Management
FIX:
There is no update option on the installation of OpenEdge Management 3.1A. OpenEdge Management 3.1A is the only version supported on OpenEdge 10.1A and 3.1A can only work with 10.1A.
The trended information and the Script Managed (Remote) Databases may be migrated from 3.0A to 3.1A following the two procedures below. If the Fathom Tend database is not at version 3.0A04 already apply service pack 3.0A04 to the Fathom Management installation and follow the instructions in the release notes for changes that must be made to the database.
== Upgrading Fathom Management from 3.0A to OpenEdge Management 3.1A ====
When transitioning from Fathom Management 3.0A to OpenEdge Management 3.1A, the following must hold true for this process to work.
1. Fathom 3.1A is to be installed into a different directory than the Fathom 3.0A install and the Fathom 3.0A install must still available.
2. Any needed 10.0B to 10.1A transitions such as copying and updating conmgr.properties has been done.
3. It will be easier if Fathom 3.0A is first brought up to SP version 3.0A04, including the updating of the Fathom database as outlined in the 3.0A04 release notes. Otherwise the
updating of the database will have to be done as part of moving it to 3.1A. If the trend database has not been upgraded to 3.0A04 already, it may be done following the instructions
below, under the title line == Updating of the database 3.0A trend database that has not been upgraded to 3.0A04 level ==
Once the trend database is at the proper level the upgrade may proceed.
==== Upgrading Fathom Management 3.0A to OpenEdge Management 3.1A =======
After installing OpenEdge Management 3.1A (Fathom) against 10.1A and doing the initial configuration for OpenEdge Management 3.1A, replace the default 3.1A database with the working 3.0A database.
Example:
1. 10.0B proenv> dbman -stop -all
2. 10.1A proenv> dbman -stop -all
3. Shutdown the 10.1A AdminServer
4. $FATHOM30A/bin/fmconfig -disable
5. cd $FATHOM30A/db
6. 10.0B proenv> proutil fathom -C truncate BI -G 0
7. Backup the Fathom 3.0A database
probkup fathom30a fathom30a.bk
8. Delete the $OEFATHOM31A/db database that was created when initially configuring the OpenEdge Management 3.1A (Fathom) installation.
9. Replace it with the one from Fathom 3.0A.
- cd $OEFATHOM31A/db
prorest fathom fathom30a.bk
10. Copy the smdatabase.properties file from 10.0B $DLC/properties to the 10.1A $DLC/properties folder to move all local scripted databases to the new installation for OpenEdge
Management 3.1A.
11. The defined resources in the Fathom 3.0A resource database need to be made available in the Fathom 3.1A area. Since the Fathom installation path is assumed to be different a
fathom -dump will have to be done and the paths edited for the existing database rather than just copying it over.
$FATHOM30A/bin/fathom -dump $FATHOM31A/config/fathom.xml
12. Edit the resulting fathom.xml file .to do a global search/replace on the directory specifications from the Fathom 3.0A install path. Make the changes to correspond to where
OpenEdge Management 3.1A is installed.
13. Delete the existing $FATHOM31A/config/fathom.o* database files, new ones will be regenerated from the edited $FATHOM31A/config/fathom.xml file when the 10.1A
AdminServer is next started.
14. The Fathom 3.0A graph cache database can be ignored and left behind.
15. Any Fathom 3.0A remote container management settings will be left behind and the fmconfig command reused in Fathom 3.1A to enable remote monitoring.
16. The vpd.properties file will probably need removing if Sonic is not uninstalled from 3.0A.
17. If the Fathom working directory is to be copied, the graphcache, cachedata and MFConfigurationElements.xsd will need to be omitted.
18. Any remote systems will need to perform fmconfig -update to the newly installed Fathom.
19. Any Fathom 3.0A custom perl, job or report scripts will need to be accounted for individually and moved over.
This completes the process of upgrading Fathom Management 3.0A to OpenEdge Management 3.1A
====== Updating of the database 3.0A trend database that has not been upgraded to 3.0A04 level ==================
If the Fathom trend database being moved to to Fathom 3.1A was originally created before Fathom 3.0A04, it needs to be updated. This is to make it compatible with the Fathom 3.1A code base. The update involves adding and activating indexes to improve database compaction performance and a corrections to the datatype of the Db_TabAnalysis.TAB_Bytes field.
1. Modify the Fathom trend database entry in conmgr.properties if the existing settings are less than the following.
This can be done using Progress Explorer:
Add an additional proapw writer
Increase -bibufs to 100
Increase -B to 32000
Increase -spin to 8000
[configuration.fathomtrenddatabase.defaultconfiguration]
asynchronouspagewriters=2
beforeimagebuffers=100
blocksindatabasebuffers=32000
spinlockretries=8000
2. Set default to Fathom 3.1A $WRKDIR and add indexes to the Fathom trend database:
101A proenv>
3. Use the data dictionary to connect to the fathom database and load the $FATHOM31A/src/fathom30a_index.df file.
4. Increase block size and cluster size for the BI file:
10.1A proenv> proutil $FATHOM31A/db/fathom -C truncate BI -bi 32768 -biblocksize 16
5. Activate the indexes:
If fathom.idx is available, deploy fathom.idx to $FATHOM31A/db
101A proenv> proutil $FATHOM31A/db/fathom.db -C idxbuild -cpinternal UTF-8 < $FATHOM31A/db/fathom.idx
Else
101A proenv> proutil $FATHOM31A/db/fathom.db -C all -cpinternal UTF-8
. 6. To correct datatype for Db_TabAnalysis field's a temporary field must be added to the table:
101A proenv>
7. Use the data dictionary to connect to the fathom database and load the $FATHOM31A/src/fathom30a_new.df file.
8. Define the fathomInstallDir environment variable.
fathomInstallDir=$FATHOM31A; export fathomInstallDir
9. Run .p program to change fields:
101A proenv> pro -b -p $FATHOM31A/src/30achangefield.p
10. When this last procedure completes it will change the Fathom database Cr_Control.c1 field from "2.1A" to "3.0A" to indicate that the above changes have been made..