> #### Deploying Fathom on multiple hosts

> A slightly more complex way to deploy Fathom is to install it on each host where resources are to be monitored. In this scenario, each install of Fathom will monitor only those resources local to the host on which it is installed. Each install of Fathom uses its own FathomTrendDatabase, as illustrated in Figure 4–2.

> Figure 4–2: Multiple-host Fathom installation

> Figure 4–2 illustrates three separate installs of Fathom, one each on Machine A, B, and C. Each install uses its own FathomTrendDatabase, and each install is monitoring only local resources.

> A possible negative aspect of the deployment shown in Figure 4–2 is that you have multiple FathomTrendDatabases.

> As an alternative, you could configure each install of Fathom to use a shared FathomTrendDatabase, as shown in Figure 4–3.

> Figure 4–3: Multiple-host installation with shared FathomTrendDatabase

> Figure 4–3 illustrates three separate installs of Fathom, one each on Machine A, B, and C. Each install is sharing a single FathomTrendDatabase on Machine B, and each install is monitoring only local resources.

> In the deployments shown in Figure 4–2 and Figure 4–3, there is a separate install of Fathom on each host where resources are to be monitored. Neither takes advantage of Fathom's remote resource monitoring.

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