Kbase P103247: Fathom Management and monitoring different Database versions
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/08/2009 |
|
Status: Verified
GOAL:
Can Fathom Management 10.1B monitor a 10.1A database locally?
GOAL:
Can OpenEdge Management 3.1B monitor a 9.1E database locally?
GOAL:
Fathom Management and monitoring different Database versions
GOAL:
Can I monitor the version 9.1x Progress Databases as scripted databases under OpenEdge 10 AdminServer?
GOAL:
Can I monitor the version 9.1x Progress Databases as managed databases under OpenEdge 10 AdminServer?
GOAL:
Can I remote monitor version 9.1x Progress Database?
GOAL:
Can I monitor and trend "unmanaged Progress databases" WITHOUT migrating them to AdminServer ?
FACT(s) (Environment):
OpenEdge Management 3.x
All Supported Operating Systems
FIX:
Although the Fathom Management Product can only be "bound" to one supported version of Progress, this does not limit the fact that a previous version of Progress can still be monitored, as a scripted database OR as a remote adminserver even though the adminserver of the different version is local.
Let's assume that Fathom Management 3.0A02 is bound to OpenEdge 10.0B02; there are four possible permeations under which a Progress 9.1E database could be setup for monitoring:
1) Monitor the database as a scripted database directly to the 10.0B AdminServer.
2) If the database is managed by the 9.1E AdminServer, the 9.1E AdminServer can automatically start the dbagent and monitor as in #1 above
3) Configure the 9.1E AdminServer as a remote container and then monitor the database, WebSpeed, AppServer and NameServer for that install (if the database is managed by the AdminServer)
4) If the database is not managed by the AdminServer, configure the 9.1E AdminServer as a remote container and monitor the database as a scripted database through the 9.1E AdminServer (instead of directly to the Fathom 10.0B AdminServer)
Other permutations:
For OpenEdge Management 3.1B, please refer to the Readme packaged with this release. Unlike OpenEdge Management 3.0A, which can be bound to Progress 9.1D09, 9.1E or OpenEdge 10.0B, then remotely monitor other versions, OpenEdge Management 3.1x releases can only be bound to the associated OpenEdge 10.1x install. For example:
- OpenEdge Management 3.1A can only be installed on the top of OpenEdge 10.1A, but it can remotely monitor Progress 9.1D09, 9.1E, OpenEdge 10.0B and 10.1A databases and installations
- OpenEdge Management 3.1B can only be installed on the top of OpenEdge 10.1B, and it can remotely monitor Progress 9.1E, OpenEdge 10.0B, 10.1A and 10.1B databases and installations
- OpenEdge Management 3.1B01+ can only be installed on the top of OpenEdge 10.1B01+, and it can remotely monitor Progress 9.1E0420, OpenEdge 10.0B0534, 10.1A0221 and 10.1B01+ databases and installations. If SP 3.1B01 has been applied then a special tfix needs to be applied for example on the remote OpenEdge 10.1A install first, as this SP changes the Sonic installation from version 5 to 6 for the remote containers. Please refer to Progress Solutions P123427 and P123420 referenced below. Again, further information is in the Readme.