> ### Working with collection views and viewlets

> Each collection view contains one or more viewlets. There are three types of viewlets: resource, standard, and view panel.

> ##### Resource viewlets

> A resource viewlet is specific to a single instance of a resource. In Figure 3–2, for example, each viewlet shows information about the FathomTrendDatabase resource.

> Figure 3–2: Sample resource viewlets

> ##### Standard viewlets

> A standard viewlet is predefined by Fathom for displaying content about multiple resources or other aspects of Fathom.

> For example, as shown in Figure 3–3, you can set up a viewlet of active monitoring plans.

> Figure 3–3: Sample Standard viewlet

> The viewlet displays the currently active monitoring plans (or schedules).

> Other standard viewlets that Fathom provides are as follows:

> - Collection members — A list of all members of the collection, including other collections. A description of the member also appears, if available.
> - Active monitoring plans — A list of all active resource monitoring plans.
> - Running reports — The currently running reports, shown in tabular format. You can customize the view by selecting the fields to display for each report.
> - Alert severity legend — An explanation of the different icons used to indicate the severity of an alert.
> - Resources with alerts — A list of resources with open alerts as well as summary information, such as the date and the time of the last occurrence. Each resource name is preceded by its container name.
> You can customize the view by selecting the fields to display for each resource.

> - Running jobs — The currently running jobs, shown in tabular format. You might want to customize the view by selecting fields to display for each job, or by limiting the display to jobs running greater than some period of time.
> - Resource status legend — An explanation of what certain data in the viewlet represents.

> ##### View panel viewlets

> A view panel viewlet displays a view for any other collection being referenced by the active collection. Your ability to define views in one collection that you can display in another collection contributes to centralized, streamlined maintenance while also eliminating the need to create duplicate viewlets of the same data.

> Figure 3–4 shows the sample view in the My Collections.Home.DBs collection. The sample view contains viewlets showing the View left panel and the View right panel of the Default view in the DBs.OEserver collection.

> Figure 3–4: View panel viewlets

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