> ### Sample collection scenario

> When you create a collection, consider which resources it makes sense to group. Remember that a resource can be a member of more than one collection, so you have significant flexibility in how you organize collection members.

> Consider the case of a large company that has Fathom Management monitoring multiple OpenEdge-based applications, such as Payroll, Finance, Accounts Receivable, and Shipping, that also span multiple hosts. In some instances, the applications also share resources.

> By using Fathom's collections feature, an administrator at the company could group resources based on the applications that use them, as follows:

> - Payroll Collection:
> - Finance database on Host A.
> - Payroll database on Host B.
> - WebSpeed Broker on Host B.
> - System resources on Hosts A and B.
> - Finance Collection:
> - Finance database on Host A.
> - Accounts Receivable database on Host C.
> - AppServer Broker on Host A.
> - System resources on Hosts A and C.
> - Accounts Receivable Collection:
> - Accounts Receivable database on Host C.
> - AppServer Broker on Host C.
> - System resource on Host C.
> - Shipping Collection:
> - Shipping database on Host D.
> - Accounts Receivable database on Host C.
> - WebSpeed Broker on Host D.
> - System resources on Hosts C and D.

> By looking at a particular collection, an administrator could easily determine the status of any application. Each application collection contains the set of resources that the application depends on, and a failure in a resource is reflected in the status of the collections that use that resource.

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