Setup Menus in Admin Panel


Managing Enterprise Manager 12c Cloud control

Knowledge Base > EM Cloud Control > Managing Enterprise Manager 12c Cloud control

in EM Cloud Control

This article demonstrates how to start and shutdown cloud control, add targets manually or automatically, removing targets and also how to add administrators, hosts and manage plugins.


(i) Starting and shutting down EM:

This section explains how to use the Enterprise Manager command line utility (emctl) to start and stop the Management Service, the Management Agent, and Cloud Control.

  • Start the listener and then the database



  • Export following paths to OMS_HOME, AGENT_HOME, as shown below

$ export OMS_HOME=/u01/app/oracle/middleware/oms

$export AGENT_HOME=/u01/app/oracle/agent12c

  • Change directory to the AGENT_HOME/bin directory and execute the commands as


$ $OMS_HOME/bin/emctl start oms

$ $AGENT_HOME/core/ start agent




This will start the enterprise manager.

You can access Oracle Enterprise Manager 12c cloud control from the web browser using the same URL. The URL can also be found in “/u01/app/oracle/middleware/oms/install/setupinfo.txt” file. The status can also be checked using following command.

$ $OMS_HOME/bin/emctl status oms

Similarly you can stop the Enterprise Manager and its services using below commands, executed in the order specified,

$ $ORACLE_HOME/bin/emctl stop oms -all

$ $AGENT_HOME/core/ stop agent

(ii) Adding targets:

Oracle components that are managed and monitored by Cloud Control, such as an Oracle Database or an Oracle Web Logic Server domain, are known as “managed targets”. If the desired target is on other machine, before it can be managed, a Management Agent must first be installed on the machine the target is running on. The target itself must then be assigned to a Management Agent, thereby promoting it to managed target status. For the time being, let us assume our desired target is on the same host machine.

Cloud Control offers two modes for adding targets. Let us see each one of them in detail,

1. Manually adding targets:

Cloud Control allows you to manually add hosts as well as a wide variety of Oracle software and components as managed targets. When you add a target manually, you do not need to go through the process of discovery by adding the target directly. Discovering targets in this way eliminates the need to consume resources on the agent to perform discovery when it is not needed.

  • Login to Cloud control, and From the Setup menu located on top, select Add Target, then select Add Targets Manually.


  • On the Add Targets Manually page, select “Add Targets Using Guided process, select preferred selection from “Target Types” drop down menu and click “Add Using Guided Process”.



  • In the “Database Discovery” screen click the search button to view host machine.



  • Select the host machine name and click “select”.



  • If the selection was successful, the host name should show up under search criteria. Then click “next”.




  • Cloud control automatically performs a search for all the targets on the host machine. You can select multiple targets on this screen. Enter “Monitor Password” for selected targets and click “next”.



  • Finally, a review page shows up displaying your targets. Click “save”.



  • Once the targets are successfully added, following screen is displayed.



2. Configuring Automatic Discovery of Targets:

Automatic target discovery is the most efficient way to discover potential targets on managed hosts, as Cloud Control can search one or more hosts for multiple types of targets at the same time. The automatic discovery configuration is defined within a “discovery module”, which you can modify to suit your requirements. You can schedule discovery to run on all hosts in the discovery module at the same interval, or can configure separate schedules for each host.

  • Login to Cloud control, and From the Setup menu located on top, select Add Target, then select “Configure Auto Discovery”.



  • Click “Add” to add IP range to scan and host name on which the scan should be performed.



  • Choose the desired “Target Name” and click select or you can search for target name using the search box provided.




  • Now add IP ranges under “IP Ranges to Scan” for auto scanning. Here we are specifying single IP address to list targets only on that host and click next.



  • Configuration is now complete and auto scanning will be performed at scheduled time.



(iii) Removing Targets:

  • Click on “Targets” tab as shown and from drop down menu select “Databases



  • All the target databases will be listed and click and on the one you want to remove.



  • From the “Oracle Database” tab located on top as shown in the picture below, select “Target Setup” and click on “Remove Target”.



  • A warning screen with confirmation dialog will be displayed. Click “Yes” to permanently remove target database from cloud control.



  • Now, if you select “Databases” from “Target” drop down menu, you won’t see the listed anymore.



(iv) Adding Administrator User:

  • Click “setup” and select “security”. From “security”, click on “Administrators” as shown.



  • Click on “create” menu as shown.



  • In the following screen, fields marked with asterisk are mandatory. Enter username in the “name” field and other required details. Make sure “Super Administrator” box at the bottom of the screen is checked and click “next”.



  • In this screen, you can manage privileges granted to the user. After making desired selections, click next.



  • A review will be shown as below listing details of the user account. Review the details provided and click “Finish”.



  • Now you should see the administrator account listed as shown below



(v) Deploying Agent on remote host machine:

Before proceeding with deployment, make sure entry of host names of both machines are added to “/etc/hosts” files in both machines, ensure owner of the directory in which agent is going to be deployed should be the user performing deployment and this user should be added to sudoers and and “visiblepw” must be set in sudoers file.

  • Create required directories for placing agent installation files


  • From “Setup” tab, select “Add Target” and click on “Add Targets Manually”.



  • Choose “Add Host Targets” and click  “Add Host” below.



  • You can give session name of your choice. And also give Host name of the other machine and the platform on which it is running and click “next”. In our case host machine is running on 64-bit Linux machine.



  • Give installation base directory path on remote server. Also add “Named Credential” by clicking on plus sign and give other machines Linux username and password. Then click “next”.



  • In the following review screen recheck all the entries and click “Deploy Agent” to start deploying the agent to remote host machine.



  • Before deployment starts, prerequisites checks will be performed and the process continues only if all the requirements are met.



  • Once you see “Agent Deployment Successful” screen as shown below, click “done”.



  • Now, if you try to add targets manually are mentioned above, you will see both the host machine and remote host machine listed.



  • You can add targets from remote host the same way you add from local machine. The following picture shows available targets on remote machine.





  • A confirmation dialog will be displayed at the end.


Thus agent is deployed on a remote host machine and targets on that machine are added.

(vi) Deploying and undeploying plugins:

A plug-in is an additional component which can be plugged into an existing 12c Cloud Control installation in order to extend the default out-of-the-box management and monitoring capabilities. Each plug-in defines a new type or types of target that can be monitored by Enterprise Manager. A target, or more specifically, a target instance, can be defined as any entity that can be monitored within an enterprise. This entity can be an application running on a server, the server itself, the network, or any of its constituent parts.

  •  From “setup” go to “Extensibility” and then select “Self Update”.



  • Following screen shows available plugin groups and information about applies, downloaded and available updates including description. Scroll down and click “Plug-in”.



  • All the available plugins are listed and they can be updated here too.



  • A non-zero revision number means an update is available and from actions select “Apply” to update the plugin. Click “Plugin” to list individual plugins as shown below.





  • Click on any plugin to see more details about its version and agents on which it is deployed.




  • Let us now deploy “Oracle Fusion Applications” plugin. Select the plugin and click “Management Servers” under “Deploy on”.



  • The updated plugin will now be deployed on the management servers. Click “Next”.



  • Prerequisite checks will be performed now. After completion, click “Next”



  • Specify “SYS credentials” for deploying plugins on Management servers repository.



  • A final review screen is presented which lists plugins that are going to be deployed. Downtime if any is required will be shown like in the picture with a tick. Click on “Deploy”.



  • You can check status by clicking “Show status” but since this plugin requires downtime, you won’t be able to access Enterprise Manager for some time.


During the downtime, targets cannot be managed using Enterprise manager and users cannot connect too. Trying to access Enterprise manager will result in error as shown below.


  • Once the downtime is complete and EM is online, login with your credentials and select “Management agent” after selecting “Deploy on” from plugins screen and click “Continue”. You can also customize plugin version from drop down menu.



  • Select the agents on which you want to deploy and click “Continue” at the bottom.



  • Prerequisite checks will be performed and click “Next” once the check is complete successfully which is indicated by green mark. Error if any will be displayed.



  • Final review screen appears showing running status and if restart is required after deployment.



  • We can monitor the progress of the plug-in deployment on the Management Server – click on the Show Status button.



  • Similarly, a plugin can be un deployed from the plugin screen (Setup > Extensibility > Plugins) by selecting “Management server” from “Un deploy from” sub menu. The process is described in the pictures below.







You can now click close or see status of un deployment.