Integrating Oracle Enterprise Manager Grid Control with Ops Center

Oracle Enterprise Manager aims to help IT organizations to manage entire Oracle-based cloud stack from application to disk. While Grid Control manages Applications, Middleware and Database layers, Ops Center manages hardware, storage, network, virtualization, and operating system layers.

I tried to demonstrate how to install Oracle Enterprise Manager Grid Control 11g and Ops Center 11g in my previous blogs (Ops Center, Grid Contol). Now I’ll try to show how to integrate Grid Control with Ops Center to manage both software and hardware infrastructure.

Before we begin to set up the integration, let’s examine the following diagrams to see how the integration will work.

This is a simple diagram showing communication between a target server and OEM Grid Control. We install an agent to the target server. This agent communicates with OMS service. OMS stores the data it has collected in the repository database.

This diagram shows the connection between a target server and OEM Ops Center. Ops Center uses “proxy controllers” to communicate with its agents. Again, we have an agent installed on the target server. The proxy server acts as a bridge between the agent and Ops Center, and Ops Center stores the data it has collected in its repository database. By the way, Ops Center uses PostgreSQL.

If we want to use both Ops Center and Grid Control to manage the server, we have to install agents of both Grid Control and Ops Center. I hope next releases will use a common agent. In this environment, we have to login separately to Grid Control and Ops Center to manage the server (and other assets).

So here is the important question: What do we need to do integrate Ops Center to Grid Control? First we should define the integration between Ops Center and Grid Control. It is “exchanging information in one-way”. We have 3 options to integrate these applications:

1) We can connect Ops Center to Grid Control. When we connect Ops Center to Grid Control, Ops Center will have a new tab for the assets. This new tab will show information about targets managed by Grid Control (such as databases etc).

2) We can connect agents of Grid Control to Ops Center. We deploy a plug-in to the agents which will communicate with both Ops Center and the repository database of Grid Control. So you’ll be able to see information from Ops Center in the agent page of Grid Control. Unfortunately I do my tests on virtualboxes so we will not see any hardware information but at least I will show all settings needed.

3) We can do both – connect Grid Control to Ops Center, and Ops Center to Grid Control. It might be called as “full integration”.


It’s very easy to connect Ops Center to Grid Control. All we need is to configure the connection.

Login to Ops Center, click “grid control” under the “administration” menu, and click “configure/connect” button at the right panel.

Enter the host name and port of Grid Control. I use “” to reach the web interface of my grid control, so I enter “” as host name and 7799 as port number.

Enter the required information to access the repository database of grid control. Don’t forget that Grid Control uses SYSMAN schema and you need to enter SID (not service name) of the database.

Check the summary, click “finish” if everything is OK. If you want to re-configure you can click “configure/connect” button again at the right panel.

As you see, Ops Center is connected to Grid Control!

Now let’s check the new tab in the asset page. The new tab named “targets” has been added. Click this tab and we can see the database icon in membership graph.

In the targets tab, we can see Grid Control targets (located in this server) and alerts belonging to them. If you select a target and click “goto” button, Ops Center will forward you to Grid Control.

We landed to the page of the selected target. Of course, Grid Control will ask you login credentials. As you remember, we haven’t entered any credential to access Grid Control in configuration page. Another important point is, you have to make sure that you enabled popups! Otherwise, forwarding will not work.


Now we’ll connect our Grid Control to Ops Center. I want to remind that these connections are independent from each other, so you do not need to connect Ops Center to Grid Control, to be able to connect Grid Control to Ops Center.

Before we begin, make sure that the target server which you deployed the plug-in, can resolve the address of Ops Center. If you do not use DNS, you may add an entry to /etc/hosts file.

We’ll use a plugin (ocas_plugin-2.0.jar) to connect Grid Control to Ops Center. Let’s start with setting the preferred credentials of “agent” for the target server we’ll deploy our Ops Center plugin. Go to “Preferences” page, click to the Preferred Credentials (in the left side ), then click “set credentials button” for agents, select the agent and enter the credentials. This is the user you used to install your agent.

We’ll import the Ops Center plugin (ocas_plugin-2.0.jar) to the Grid Control. This file comes with Ops Center setup files. You can find it in “ocasmp” folder. When I was installing Ops Center, I extracted the setup files into /setup folder. xvmoc_full_bundle folder is created by tar while extracting the files. So the path of the file is:


I copy this file to my desktop:

It’s not required to copy this file to my desktop. We could run firefox or another browser to reach Grid Control from Ops Center server to upload this file.

Go to “setup” page, click “management plugins”, and then click “import”.

Click “choose file”, select the ocas_plugin-2.0.jar in your computer and click “list archive”. You’ll see that oracle_asset_stack is listed. Mark its checkbox and click OK to import this plugin.

Our plug-in is ready to deploy. Click deploy button.

Select the agents and click next.

Click finish to deploy agent.

As you see, “deploy operation completed”. Now we need to configure our agent.

Select the agent (click over its name).

Select “infrastructure stack” as monitoring target and click “add” button.

Give a meaningful name for the target, and fill the required information. I used “root” account, but it’s recommended to use a new account in Ops Center for integration. It doesn’t need any special privileges. The plug-in needs to communicate with the repository database so you need to enter the connection information. Click OK to finish the configuration. Well, in fact the configuration is not yet completed.

A new monitored target is listed.

We have to enter password of “sysman” user in the preferred credentials, so plugin can connect to repository database. Go to”preferences”, then “preferred credentials” and click “set credentials button” for infrastructure stack.

Enter the credentials for EM repository, Ops Center, Host and Job. The host and job username is the username you used to install the Grid Control agent. We’ll use host and job credentials for creating a job to import Ops Center policies. Click apply to set the credentials.

Let’s test our plug-in (and connection to Ops Center). Click the targets tab, go to the hosts, select the host you installed the plugin, click to the targets, and then click to the “infrastructure target”.

Don’t get disappointed! This is not a Sun server. As I said, I used virtualboxes. So there’s no hardware to manage, but you can be sure that plug-in works perfect (because there’s no errors in the page). If you implement with real hardware, you’ll surely get results.

When you connect a GC agent to Ops Center, It’s recommended to import Ops Center policies, so I’ll do it. Click “jobs” tab, and select “import Ops Center policies” as job type and create the job.

Give a name for the job, select the target “plug-ins” and submit the job. You do not need to enter any credentials because we already set it (while entering credentials for the repository database). When the job completes, the alerts defined in Ops Center will be shown in Grid Control.

As you see, we have completely integrated our Grid Control with Ops Center. It’s easier than I expected and I can say that it works very stable.

Please share

AWS Big Data Specialist. Oracle Certified Professional (OCP) for EBS R12, Oracle 10g and 11g. Co-author of "Expert Oracle Enterprise Manager 12c" book published by Apress. Awarded as Oracle ACE (in 2011) and Oracle ACE Director (in 2016) for the continuous contributions to the Oracle users community. Founding member, and vice president of Turkish Oracle User Group (TROUG). Presented at various international conferences including Oracle Open World.


  1. Douglas Adams

    Attempted to connect OPS-Center to OEM and got the following :   reconfiguring to another EMRrepository is not supported 101055.



  2. Same error here. It worked the first time (using IP number instead of hostname) but when I tried to reconfigure to hostname I also got “reconfiguring to another EMRrepository is not supported 101055.”. SR on this has been open for months now.

    I am trying to tie my Exalogic Control (=Ops Center 12c) to Cloud Control… Gokhan would you know how to resolve this ? Is the problem on the Ops Center side or the Cloud Control side ? I would be interested to have your opinion/input on this

    my blog :


  3. Javier Ruiz

    How does OpsCenter pull the target data from OEM? several of are assets have the targets but others don’t. We are using version

Leave Comment

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.