Try OpenEdge Now
skip to main content
Getting Started
Setting up Remote Resource Monitoring and Configuration : Preparing to enable remote monitoring and configuration
 

Preparing to enable remote monitoring and configuration

Before you enable remote monitoring or configuration, you identify one host machine and one or more non-host machines. Each non-host machine is known as a remote AdminServer.
At a minimum, the host machine must have OpenEdge installed on it along with OpenEdge Management or OpenEdge Explorer. As described in OpenEdge Explorer overview. OpenEdge Explorer is installed automatically with OpenEdge Management. OpenEdge Explorer is also installed with a number of OpenEdge components.
The remote AdminServer must have an AdminServer installed on it but must not have an enabled installation of either OpenEdge Management or OpenEdge Explorer. If either one is enabled, we recommend that you run the unglue script to "unglue" OpenEdge Management or OpenEdge Explorer from OpenEdge before you enable the machine as a remote AdminServer.
When you run the unglue script on a remote AdminServer, you disable (but not uninstall) OpenEdge Management or OpenEdge Explorer. The ability to unglue OEE and OEM is useful when you want to set up one or several remote AdminServers for one host machine.
As shown in the scenario illustrated in the following figure, Machine A and Machine B have an installation of OpenEdge and OpenEdge Management. (OpenEdge Explorer is also installed.) Machine C has OpenEdge and OpenEdge Explorer installed.
Figure 9. Setting up remote monitoring or configuration
In this scenario, each install of OpenEdge Management (on Machine A and Machine B) can monitor and configure only those resources local to the host on which it is installed (and each install of OpenEdge Management uses its own OpenEdge Management Trend Database). OpenEdge Explorer, on Machine C, configures only its local resources. No monitoring takes place on Machine C because OpenEdge Management is not installed.
An alternative to this scenario is to set up Machine A, for example, as a host machine and Machines B and C as remote AdminServers. To effect this setup, we recommend you run the unglue script on both Machines B and C before you enable either machine as a remote AdminServer. When you run unglue on Machine B, OpenEdge Management and OpenEdge Explorer are disabled. When you run unglue on Machine C, OpenEdge Explorer is disabled.
Should you later decide to discontinue using Machine B or Machine C as a remote AdminServer, you can run reglue, which re-enables OpenEdge Management or OpenEdge Explorer in the OpenEdge product. For details about reglue, see Regluing OpenEdge Management or OpenEdge Explorer to OpenEdge.
* Ungluing OpenEdge Management or OpenEdge Explorer from OpenEdge
* Regluing OpenEdge Management or OpenEdge Explorer to OpenEdge