> #### More about monitoring scripted and managed databases

> You can configure Fathom to monitor both scripted and managed databases. Using the dbagent, Fathom can monitor a database that is running on the same host as Fathom or on a different host, regardless of whether the database is managed (recognized by the AdminServer and Progress Explorer) or scripted (not under AdminServer control).

> Currently Fathom can monitor:

> - A scripted database that is running through a remote-enabled AdminServer.
> - A managed database (that Fathom has autodiscovered) running under a remote-enabled AdminServer.
> - A scripted database that is running outside of the AdminServer in which Fathom Management is running. In this case, the AdminServer is not remote-enabled.

> ##### Monitoring a scripted database through a remote-enabled AdminServer

> When Fathom monitors a scripted database that is running through a remote-enabled AdminServer, the scripted database communicates directly with that remote-enabled AdminServer, which then uses the Sonic infrastructure to communicate with Fathom. The advantage to setting up monitoring in this way is that the scripted database can connect right into an AdminServer that is remote-enabled for all resources; it is not necessary for the dbagent to open a separate port into Fathom.

> You configure Fathom and the remote-enabled AdminServer by using the Fathom Remote Monitoring Configuration Utility. For details, see Chapter 6, "Configuring Remote Monitoring for Fathom."

> Note that if you upgrade from Version 2.1A and then use the remote-enabled AdminServer method of database monitoring in Version 3.0A, there is a chance that you might see a database twice in the tree in the Fathom Management console: once under the remote container and once under the local Fathom container as a scripted database. In such a situation, the database that is the first one up and running (or recognized by Fathom or by the AdminServer) is the one that Fathom monitors.

> ##### Monitoring a managed database through a remote-enabled AdminServer

> Fathom can monitor a managed database that has been autodiscovered running under a remote-enabled AdminServer.

> ##### Monitoring scripted databases outside the AdminServer running Fathom

> As was possible in Fathom Management Version 2.1A, Fathom can monitor scripted databases that are running outside of the AdminServer in which Fathom Management is running. In order to monitor a database that is scripted, you must create a remote database resource.

> To monitor a scripted database once you migrate it, Fathom uses the dbagent installed with your OpenEdge database. This deployment is shown in Figure 4–6.

> Figure 4–6: Monitoring scripted databases on another machine

> If you are using the AdminServer on Machine B to manage your databases, you can use Progress Explorer to configure those databases for monitoring by Fathom. If you are not using the AdminServer on Machine B, you will need to modify the startup parameters of each database to start the dbagent when the database is started. See the Database Management Guide for more information.

Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095