Try OpenEdge Now
skip to main content
Resource Monitoring
Creating Collections and Collection Views in OpenEdge Management : Sample collection scenario
 

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 OpenEdge Management monitoring multiple OpenEdge-based applications, such as Payroll, Finance, Accounts Receivable, and Shipping. These applications also span multiple hosts, and in some instances, the applications also share resources.
By using OpenEdge Management's collections feature, an administrator at the company can 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 can easily determine the status of any application. Each application collection contains the set of resources that the application depends on. A failure in a resource is reflected in the status of the collections that use that resource.