This content has been marked as final. Show 7 replies
Hi1 person found this helpful
Have a look at the OEM documentation for plugins.
Oracle® Enterprise Manager System Monitoring Plug-in for Oracle Enterprise Manager Ops Center Guide 12c Release 1 (126.96.36.199.0)
It describes the method for OEM 12c and Ops Center 11g upd3, but in theory it should work for 12c on 12c.
It appears this "integration" is one monitoring the status of the other... or am I missing something in the documentation?
Rob, you are correct
If I remember correctly, only the critical events from each will be sent through to the other. (even though you have agents from both on the server being monitored)
Edited by: 3sth3r_m on 07-Aug-2012 21:58
Oracle sure did miss the mark, didn't they?
It's more than just one monitoring the other, but I do remember something about critical alerts only which is concerning.
But there's more value than that even, most of which I think it discussed in the above document.
Personally I feel that it's a bit overkill, having both products. I've been asked this question and I honestly didn't know what to answer
"What does ops center give me extra that I don't already have with OEM?"
For this customer they already use OEM. With OEM you can do provisioning, monitoring, see trends, monitor the hardware and run reports. There is no real world examples of how it's better/different/more complete to have both products running.
There's a ton of things in OC that you can't do in OEM, at least not that I know of. Such as:
OVM Server for Sparc (LDOM) management
S10/S11 zone management
updating Solaris 11
provisioning Solaris (9, 10, 11)
If you are an all-Linux shop then you may have an argument but Solaris wise I don't think OEM scratches the surface of OC.
At an even higher level, OEM is more geared for the App layer while OC is more geared for the OS/system/virtualization layer.