Managing Oracle Fusion Middleware using OEM12c : Lessons Learned

I covered installation of OEM 12c here and here,  Monitoring of Fusion Middleware Component (WebLogic, OID, OVD) here and here. In this post I am going to discuss lessons learned and key points you must know when configuring Oracle Fusion Middleware monitoring using OEM 12c

1. In order to monitor Fusion Middleware components (Identity Management, SOA, OHS, WebCenter, OBIEE etc) using OEM 12c, Fusion Middleware application must be configured with Fusion Middleware control (Fusion Middleware Control is J2EE application “em” deployed on Admin Server of WebLogic Domain for Fusion Middleware)

Note: Fusion Middleware Control EM is different from OEM 12c and for each WebLogic Domain (where Fusion Middleware application is deployed) there is separate Fusion Middleware Control. For OEM 12c to discover all targets in Fusion Middleware (SOA, WebLogic, OBIEE, OID, OVD, OIM, OAM, WebCenter etc), Fusion Middleware Control should be configured to monitor Fusion Middleware component. (This is configured by default during Fusion Middleware configuration)

2. If Fusion Middleware WebLogic domain doesn’t contain Fusion Middleware Control Application (/em) then extend WebLogic Domain to include Fusion Middleware Control.

WebLogic Console -> Deployments

 

3. If your fusion middleware component includes SYSTEM component (like OHS, OID, OVD, OBIEE) and are not registered with Fusion Middleware Control then use OPMNCTL REGISTERINSTANCE to register OPMN with WebLogic Domain

4. Ensure that Fusion Middleware Control (/em) is working fine (on starting/stopping services, correct status of component is displayed in Fusion Middleware Control) before you start configuring Fusion Middleware with OEM 12c.

5. If Fusion Middleware Application is deployed on more than one host (For Highly Available Fusion Middleware Application there is always more than one Host) then deploy OEM Agent on all hosts where Fusion Middleware components are installed.

6. If there is firewall between OMS Server (server side of OEM 12c) and Fusion Middleware Host (where OEM Agents are deployed) then

a) OEM Agent  port (default value 3872) should be allowed from OMS Servers (innowave21) to OEM Agent (innowave12) in firewall.
b) Repository URL port (default value 4900) must be allowed from OEM Agent (innowave12) to OMS server (innowave21) in fireall.

emctl status agent  (Look for Agent URL and Repository URL)

____

[oem@innowave12 bin]$ ./emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
—————————————————————
Agent Version : 12.1.0.2.0
OMS Version : 12.1.0.2.0
Protocol Version : 12.1.0.1.0
Agent Home : /oracle/apps/oem/oemserver/agent/agent_inst
Agent Binaries : /oracle/apps/oem/oemserver/agent/core/12.1.0.2.0
Agent Process ID : 5601
Parent Process ID : 5533
Agent URL : https://innowave12:3872/emd/main/
Repository URL : https://innowave21:4900/empbs/upload
Started at : 2013-06-21 17:54:57
Started by user : oem
Last Reload : (none)
Last successful upload : 2013-07-16 08:04:40
Last attempted upload : 2013-07-16 08:04:40
Total Megabytes of XML files uploaded so far : 78.5
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0
Available disk space on upload filesystem : 18.84%
Collection Status : Collections enabled
Heartbeat Status : Ok
Last attempted heartbeat to OMS : 2013-07-16 08:03:58
Last successful heartbeat to OMS : 2013-07-16 08:03:58
Next scheduled heartbeat to OMS : 2013-07-16 08:04:58

—————————————————————
Agent is Running and Ready

_________

7. If OMS server is running on two or more WebLogic Managed Servers then ensure that there is load balancer (or HTTP Proxy) in front of two or more OMS servers. In such cases, Repository URL should use Load Balancer URL (and not point to individual OMS server )

8. If your fusion middleware component includes SYSTEM component (like OHS, OID, OVD, OBIEE) 11.1.1.6 or lower and Service Status in OEM 12c is not displayed correct (showing service available where as in actual service is down) then ensure that following patches are applied to Fusion Middleware Control

a) 13490778 applied to oracle_common in middleware home (MW_HOME) where Fusion Middleware is deployed
b) 13055259 applied to ORACLE_HOME where fusion middleware component is installed

9. If status of fusion middleware target is PENDING in OEM 12c (but displayed correctly on Fusion Middleware Control) then set blackout for target and unset it after 5 minutes. (This is workaround for BUG where sometime status of target is shown as PENDING. For permanent fix ensure that latest patches are applied on OMS Server and OEM Agent)

10. Finally review My Oracle Support Note 1458357.1  EM12c Troubleshooting: Discovery and Monitoring FMW (Fusion Middleware) Targets
Stay tuned to know more about diagnosing performance issues on Fusion Middleware components using OEM 12c (including JVMD/ADP).
What errors did you encounter during configuration of Fusion Middleware monitoring using Oracle Enterprise Manager 12c ?

Share This Post with Your Friends over Social Media!

About the Author Atul Kumar

Oracle ACE, Author, Speaker and Founder of K21 Technologies & K21 Academy : Specialising in Design, Implement, and Trainings.

follow me on:

Leave a Comment:

11 comments
Rahul says July 18, 2013

Hi Atul,

In your 9th point you mentioned below:

If status of fusion middleware target is PENDING in OEM 12c (but displayed

Can you please let me know what exact issue/bug did you face with Targets in pending status.

Thanks
Rahul

Reply
    Atul Kumar says July 18, 2013

    @ Rahul,
    After OID/OVD discovery, status of both the components was PENDING (even after restart of OID/OVD and Agent). Support analyst suggested to set blackout for 1 hour and then unset it aftre 5 minutes (that did the trick)

    In this particular case, Fusion Middlware target was refreshed (or re-synced) as we changed name of host where Admin Server was running.

    Reply
» OEM 12c Integration with Fusion Middleware WebLogic : Compliance Score xx% is below critical threshold : Troubleshooting Online Apps DBA: One Stop Shop for Apps DBA’s says August 28, 2013

[…] Posted in August 28th, 2013 byAtul Kumar in fmw, oem If you have integrated your Oracle Fusion Middleware including WebLogic or Identity Management with OEM 12c then OEM 12c comes with pre-defined events & compliance […]

Reply
autoconfig says September 5, 2013

is it possible to monitor AIA/PIP’s using 12C..?, if yes can you provide my documents for that.

Reply
    Atul Kumar says September 7, 2013

    @ autoconfig,
    Yes you can monitor AIA/PIP using 12c using below

    If you select fusion middleware monitor it will

    a) Monitor WebLogic on which AIA/PIP is deployed use WebLogic monitoring using OEM 12c
    b) You can configure SOA/Services monitoring using OEM 12c (that AIA and PIP consists of)

    If you want to monitor anything more within AIA then let me know

    Reply
autoconfig says October 17, 2013

Thanks Autul,

can you share me documents to enable the monitoring AIA PIP’s using 12c, I want to setup 12C EM and to get alerts when ever any PIP’s are not running or down due to reasons, i want to get alerts for that,to achieve this do i need anything additional setups in 12c EM..?

Thanks

Reply
Paul says March 27, 2014

Hi Atul,

We have started to monitor a SOA Suite domain (including AIA PIP) using OEM, but we are experiencing very high CPU usage by the java processes of the admin server and the (three) managed servers in the SOA cluster, even when it’s in idle state. The CPU usage by the OEM agent process itself is low. When the OEM agents are stopped, the CPU usage on the java processes of the admin and managed servers is low, so the high CPU usage is defenately being caused by the checks that are performed by the OEM agent.

In total we have about 350 composites that are being monitored. It’s a lot of composites, but it should not generate such high CPU loads in my opinion. I have already tuned the agent according to support note 1349887.1, but this did not help.

Do you have any ideas?

Thanks

Reply
ateh says June 4, 2014

Hi Atul,

In point no 2, you mention:-
“2. If Fusion Middleware WebLogic domain doesn’t contain Fusion Middleware Control Application (/em) then extend WebLogic Domain to include Fusion Middleware Control.”

Question, how do you extend the FMW control? Where to get/download this FMW control? I still couldn’t find a way to do it..

Thanks

Reply
    Atul Kumar says June 4, 2014

    It comes with fusion middleware products like SOA, Webcenter, OIM, OAM, OID etc . Install any one of these products in same middleware home (different ORACLE_HOME) and then run config.sh and extend domain

    Reply
ankumar1974 says August 13, 2014

Hi Atul,

Could you please provide the steps to configure Disc Space Alert when the threshold reaches 90% using OEM 12c.

Thanks
Anil

Reply
ankumar1974 says August 18, 2014

Hi Atul,

I didnt get any response for my query .

Could you please provide the steps to configure Disc Space Alert when the threshold reaches 90% using OEM 12c.

Thanks
Anil

Reply
Add Your Reply