Try OpenEdge Now
skip to main content
Resource Monitoring
Creating Collections and Collection Views in OpenEdge Management : Collections : What is a collection
 

What is a collection

A collection is a group of resources (known also as members) that you define. You group resources into a collection based on criteria that you find valuable when grouped and viewed together.
You can include the following resources in a collection:
*All monitored resources, such as CPU, disks, databases, or WebSpeed Transaction servers. A resource can be a member of multiple collections.
*Jobs
*Reports
*Other collections
When you create a collection, you assign it a name and provide its definition. You can identify the collection members when you create the collection, and later you can add or remove members. However, when adding members to a new or an existing collection, you cannot add a private collection to a shared collection and vice-versa. You can include resources from multiple AdminServers in a collection. All collections are displayed in the Resources grid frame.
The OpenEdge Management console displays a list of collections that appear as labels in the details page of each resource. You can also associate members to other collections or create a new collection from a resource's details page.
When you select members for a collection, you can use a wildcard feature that enables you to select, for example, all resources, all resources of a particular type, or all resources on all AdminServers. Using the wildcard is a powerful way to manage the members of a collection. For example, if you select all databases on all AdminServers as members of a collection, databases added to AdminServers after the collection was created are automatically added as members of the collection. Likewise, any database that is removed from an AdminServer is also removed automatically from the collection.
When you look at the status of a collection, you see a rollup of the status of all members of the collection. For example, consider a scenario in which you host an application that is used by multiple customers. The application uses multiple databases and OpenEdge brokers, and it spans several hosts. If your customers contract for premium services that include dedicated hosts, databases, and/or brokers, you can group resources based on the customers using them. In so doing, you can quickly assess the status of the application for any of the supported customers.