|Oracle® Enterprise Manager Cloud Control Extensibility Programmer's Guide
12c Release 3 (220.127.116.11)
|PDF · Mobi · ePub|
Automatic Discovery is part of Configuration Management in Enterprise Manager. It forms the foundation for configuration management and Enterprise Manager by identifying IT components and allowing you to manage these components using Enterprise Manager.
This chapter contains the following sections:
To enable auto discovery, Management Agent-side discovery scripts are packaged with the plug-in. When auto discovery is configured on a host, the discovery part of the plug-in (discovery scripts) is deployed on the host.
After auto discovery is configured to run on the managed host, discovery takes place periodically and sends potential targets to the Management repository.
Users can view the targets from the discovery results UI and then take various actions such as promoting the target to be managed by Enterprise Manager.
The following are the key benefits of adding automatic discovery:
Easier to add targets to Enterprise Manager. Otherwise, the user must manually add each target to Enterprise Manager individually. This is a cumbersome and time-consuming task.
Easier to manage multiple objects on a single host. Otherwise, the user must manually add each object on the host as a target and then repeat the process on all other hosts.
This section describes the new features of discovery:
You can configure automatic discovery for targets in a plug-in to be run at the Management Agent-side. Currently, automatic discovery is scheduled to run every day.
After automatic discovery is configured and run, the Management Agent sends the targets back to the Oracle Management Service to be reviewed by the user.
The user can configure targets that are not yet managed and promote them so that they can by managed by Enterprise Manager.
This section provides an overview of the components of automatic discovery:
The plug-in contains the components required to discover and promote targets of a particular target type. The plug-in includes discovery metadata to register with the discovery framework, discovery scripts, and monitoring scripts.
Note:Only the discovery part of the plug-in (discovery scripts and any content required to run discovery) is deployed when scheduling discovery.
The complete plug-in (monitoring and discovery) is deployed only when the discovered target is promoted or when a target is manually added.
The discovery module defines a set of target types to discover on the hosts to which the plug-in is deployed.
Discovery metadata enables you to register automatic discovery with the discovery framework. The Extensibility Development Kit (EDK) provides a discovery XML schema definition (XSD) for registering automatic discovery. For information about defining discovery metadata and a description of the elements, see the Enterprise Manager Programmer's Reference.
Discovery content includes all the Perl scripts and JAR files that are required to discover targets of a particular type.
A discovery parameter passes input entered from the UI to the discovery script. These discovery parameters are available as environment variables in the discovery script running at the Management Agent. The discovery script uses this information when performing discovery.
Define discovery parameters in the discovery metadata XML file. For information about the discovery metadata XML file, see the Enterprise Manager Cloud Control Programmer's Reference.
For plug-ins that are deployed already when Management Agents are installed or deployed to new hosts, and if discovery does not require any user inputs, then discovery is configured automatically and runs every 24 hours.