To migrate the OpenEdge Management configuration database settings (alerts, monitoring plans etc) from one version of OEM to another version of OEM, do the following:
- Under old OEM: proenv -> fathom -dump settings.xml
- In new version of OEM: proenv -> fathom -load settings.xml (may need to add -httpport -user -password)
To preserve the existing
Trend database and convert it to OpenEdge 11:
- Under old OE: Truncate BI of the trend database (fathom.db) using the command: proutil fathom -C truncate bi
- In new OE: Convert the trend database (fathom.db) to OpenEdge 11 using the command: proutil fathom -C conv1011
- Apply the appropriate delta to the database from the oemgmt\db folder.
For example:
- Use fathom110.df to upgrade to the 11.0 version of the schema
- Use fathom116.df to upgrade to the 11.6 version of the schema
- Use fathom1161.df to upgrade to the 11.6.1 version of the schema
Note: All .df files are deltas and should be applied in order. So if upgrading from 10.2B to 11.6.3, first apply fathom110.df, then fathom116.df then apply fathom1161.df.
This is necessary in order to be able to use much of the trending and reporting functionality of the product.
- Take a backup of the trend database and then restore it to a new location (for OpenEdge Management version 11)
To create a new trend database and import the OpenEdge Management configuration database from the previous OpenEdge Management release:
- Install new OEM, and access it for the first time and then shut it down completely.
- Do the fathom -dump and -load as outlined above, the goal being to migrate the OpenEdge Management configuration database settings to this new trend database. See Article How to backup Fathom Management configuration? for additional information.
- Backup the new trend database with the current configuration database settings for future reference.
- Start the new OEM.
To migrate the conmgr.properties and ubroker.properties from the previous version refer to Article P11592,
Migrating Progress versions, is it possible to use conmgr.properties and ubroker.properties from the previous version with the new version of Progress? In light of OEM migration, it is important the the original properties files are in place when running the above 'fathom -load'.
