Try OpenEdge Now
skip to main content
Servers, DataServers, Messengers, and Adapters
Supporting OpenEdge Servers, Messengers, DataServers, and Adapters : OpenEdge Management monitoring prerequisites : Discovering and enabling local resources
 

Discovering and enabling local resources

Once you complete the installation and configuration steps, OpenEdge Management automatically creates an OpenEdge Management resource monitor for each AppServer Internet Adapter, AppServer broker, NameServer instance, WebSpeed broker, DataServer broker, Messenger, SonicMQ Adapter, and Web Services Adapter (for OpenEdge SOAP Web Services) that it detects.
This discovery process occurs any time OpenEdge Management detects new OpenEdge resource instances. This process will initially take place after you install and configure OpenEdge Management, and any time new OpenEdge resources are introduced.
As part of this discovery process, OpenEdge Management enables each locally defined broker or instance and begins monitoring them immediately. You can elect to disable any resources, implement data collection (for brokers only), and modify the default monitoring plan and rules as needed.
Note: OpenEdge Management runs as a managed service in the AdminServer. Therefore, a local resource is defined as a resource recognized by OpenEdge Management and running in the AdminServer on the same machine where OpenEdge Management is installed.