Adding Non-Host Targets Using the Guided Discovery Process

To add non-host targets using the guided process, follow these steps:

Note:

When you add a target using the guided process, some scripts and automated processes are run that are particular for the target type that you select. You may have to input credentials in order to run the guided process.

  1. From the Setup menu, select Add Target, then select Add Targets Manually. Enterprise Manager displays the Add Targets Manually page.

  2. On the Add Targets Manually page, select Add Using Guided Process.

  3. In the Add Using Guided Process dialog box, select the target type such as Exalogic Elastic Cloud, Oracle Cluster and High Availability Service, System Infrastructure server ILOM, or Oracle WebLogic Domain. Click Add...

  4. After you select the target type, a wizard specific to the target type guides you through the process of manually adding the target.

    Upon confirmation, the target becomes a managed target in Enterprise Manager. Enterprise Manager simply accepts the information, performs validation of the supplied data where possible and starts monitoring the target.

Note:

When you manually add a non-host target to Enterprise Manager, the plug-in required for the target is automatically deployed to the Management Agent, which monitors the host where the non-host target exists. For the plug-in to be deployed, the Management Agent must be secure. Therefore, before manually adding a non-host target to Enterprise Manager, ensure that the Management Agent is secure. You can always unsecure it after the target is added to Enterprise Manager, that is, after the required plug-in is deployed.

To verify the secure status of a Management Agent, and to secure it if required, use any one of the following methods:

  • From the Setup menu, select Manage the Manager and then, click Agents. Click the required Management Agent. Verify whether the Management Agent is secure. If it is not secure, from the Agent menu, click Secure to secure it.

  • Run the following command to verify if the Management Agent is secure:

    <EMSTATE>/bin/emctl status agent

    If the Management Agent is secure, the Management Agent URL displayed in the output of the previous command is an HTTPS URL. However, if the Management Agent URL displayed is an HTTP URL, secure the Management Agent by running the following command:

    <EMSTATE>/bin/emctl secure agent