You can deploy OpenEdge Management to monitor the following remote resources:
Databases — OpenEdge Releases 11.3 and greater.
OpenEdge servers — AppServer, WebSpeed, OE Web Server and NameServer.
System resources — CPU, memory, disk, and file system.
The following figure shows a deployment in which OpenEdge Management is monitoring resources on a remote machine.
Figure 4. Remote monitoring of resources on one machine
The illustration shown in Figure 4 presents a single installation of OpenEdge Management on Machine A, which is monitoring the following resources on Machine B:
Scripted and managed databases — A scripted database is a database whose broker cannot be managed by the AdminServer in any way. A managed database is a database that the AdminServer recognizes and manages.
Supported OpenEdge servers — A supported OpenEdge server can be an AppServer, a NameServer, or a WebSpeed Transaction Server.
System resources — System resources are CPU, disk, memory, and file system.
You can extend the deployment model shown in Figure 4 to multiple hosts, as shown in Figure 5.
Figure 5. Monitoring of resources on two machines
The illustration shown in Figure 5 presents a single install of OpenEdge Management on Machine A, which is monitoring databases (scripted and managed), supported 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.
Databases — OpenEdge Releases 11.3 and greater.
