A slightly more complex way to deploy OpenEdge Management is to install it on each host where resources are to be monitored. In this scenario, each install of OpenEdge Management monitors only those resources local to the host on which it is installed. Each install of OpenEdge Management uses its own OpenEdge Management Trend Database, as illustrated below.
The above figure illustrates three separate installs of OpenEdge Management, one each on Machine A, B, and C. Each install uses its own OpenEdge Management Trend Database, and each install is monitoring only local resources. A possible negative aspect of this deployment is that you have multiple OpenEdge Management Trend Databases.
As an alternative, you could configure each install of OpenEdge Management to use a shared OpenEdge Management Trend Database, as shown below.
Figure 3. Multiple-host installation with shared OpenEdge Management Trend Database
The above figure illustrates three separate installs of OpenEdge Management, one each on Machine A, B, and C. Each install is sharing a single OpenEdge Management Trend Database on Machine B, and each install is monitoring only local resources.
In the deployments shown in Figure 2 and Figure 3, there is a separate install of OpenEdge Management on each host where resources are to be monitored. Neither takes advantage of OpenEdge Management's remote resource monitoring.
