OID/OVD WebLogic 11g monitoring using OEM 12c ( : High Level Steps

Oracle Enterprise Manager (OEM) Cloud Control is recommended monitoring tool for Oracle Identity Management components like Oracle Internet Directory (OID),  Oracle Virtual Directory (OVD), Oracle Access Manager (OAM), and Oracle Identity Manager (OIM).

I recently configured OEM 12c (more on OEM 12c here and here ) to monitor  OID/OVD service status i.e. if OID/OVD goes down display status in OEM Cloud Control Dashboard and also send email notification to team managing IAM (OID/OVD).

This post covers high steps to configure OID/OVD monitoring using OEM Cloud Control (12c).

Here are high level steps to monitor OID/OVD/ODSM/

1. Install OEM Cloud Control 12c

2. Install OEM CC Agent on all machines hosting OID/OVD and WebLogic Server  (assumption is that OID/OVD is WebLogic Server with em – fusion middleware control).

Note: If you do not want to register OID/OVD with WebLogic 11g then you must configure OID/OVD as standard LDAP server in OEM 12c (steps not covered in this post)

3. Discover Host/Agent running OID/OVD service (This can be done using auto discovery or manual discovery) : OEM CC -> Setup -> Add Target ->  Add Target Manually (or Auto Discover)


4. Once Target Host and OEM Agent (hosting OID/OVD/WebLogic with EM) are discovered then add Middleware Target: OEM CC -> Targets -> Middleware -> Add -> Oracle Fusion Middleware/WebLogic Domain


5. Provide WebLogic Server detail that is configured to manage OID/OVD (Fusion Middleware Control EM deployed on WebLogic Admin Server is used to monitor OID/OVD)

6. Configure Email Notification in OEM 12c Server

7. Create Incident Rules to send eMail notification for OID/OVD Service Staus. From OEM 12c onwards, Service Up and Down events (OID/OVD availability) are grouped in to Incidents and any action on incident is done via Incident Rules. Configure your Account in OEM 12c to “Subscribe to receive emails for Incident Rules”  OEM CC -> Setup -> Incidents -> Incident Rules

In Ruleset , look for Rule “Incident creation rule for target unreachable” or you can create your own ruleset (collection of rule to send eMail notification for OID/OVD target unreachable)




8. Finally test by restarting OID/OVD that OEM notifies service status change on OEM console or Email Notification or SNMP trap (depending on Incident Rule)


9. Check status of IAM components in “Identity & Access Management Dashboard” on OEM 12C Cloud Control Console : OEM 12 CC -> -> Targets-> Middleware -> Middleware Features -> Identity & Access



In next post I am going to cover issues encountered during Oracle Identity Management monitoring setup using OEM 12c (cloud control)

Hitting any issues on Oracle Identity & Access Management Monitoring setup ??  Drop a comment with issue (and fix if resolved)




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: