Monitoring database, OpenEdge, and system resources on a remote machine

You can deploy OpenEdge Management to monitor the following remote resources:

A deployment in which OpenEdge Management is monitoring database, OpenEdge server, and system resources on a remote machine is shown in Figure 5–4.

Figure 5–4: Remote monitoring of resources on one machine

The illustration shown in Figure 5–4 presents a single installation of OpenEdge Management on Machine A, which is monitoring the following resources on Machine B:

You can extend this deployment model to multiple hosts, as shown in Figure 5–5.

Figure 5–5: Remote monitoring of resources on two machines

The illustration shown in Figure 5–5 presents a single install of OpenEdge Management on Machine A, which is monitoring databases (scripted and managed), OpenEdge servers, and system resources on Machine B and Machine C.

The number of remote hosts you monitor from the OpenEdge Management install on Machine A is limited only by the power of Machine A, the number of remote resources monitored, and the frequency with which they are polled.

This deployment model is very effective in that it allows you to install OpenEdge Management on a non-production machine—that is, a machine other than one where your OpenEdge or other critical application resources run. The benefit of this deployment model is that it minimizes the impact of using OpenEdge Management to monitor your production machines.


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