OUD 11g: DIP High Availability Configuration With OUD 220.127.116.11 and EMAGENT HA Setup Issue
(Doc ID 2272108.1)
Last updated on FEBRUARY 02, 2019
Applies to:Oracle Unified Directory - Version 18.104.22.168.170117 and later
Oracle Internet Directory - Version 22.214.171.124.0 to 126.96.36.199.170327 [Release 11g]
Information in this document applies to any platform.
Two OUD 188.8.131.52.170117 nodes are installed and are replicated with each other. OUD versions might differ from this example.
Trying to configure DIP 11g High Availability with OUD Directory as Backend Directory when following below document for configuration.
However facing issues while configuring that, it can not create second DIP instance dip_inst2 on second node.
Followed Section 184.108.40.206, "Configuring High Availability for an OUD Backend Server in above document, and successfully configured node1 and successfully ran unpack on node2 of DIP server. After unpacking observed dip_inst2 folder is missing in node2.
It should ideally create dip_inst2 in node2. Only dip_inst1 and EMAGENT is created on Node1 DIP1 instance
So the issue is that it does not setup dip_inst2 in node2 after following the above official Document and thus EMAGENT is not configured for DIP2 Node2.
1. Following the below document for setting up DIP in High Availability with OUD (Oracle Unified Directory) as Backend Directory, and facing the issue of EMAGENT not getting created or installed on second DIP node even though all steps of the below document are followed correctly.
Oracle® Fusion Middleware High Availability Guide
8 Configuring High Availability for Identity Management Components
220.127.116.11 Oracle Directory Integration Platform High Availability Architecture (OUD Backend)
Following the above DIP HA guide DIP High Availability works fine. That is if one DIP goes down other DIP is up and running fine. But the limitation is it just creates one EMAGENT which is shared between two DIP instances. And if EMAGENT is down then both DIP instances cannot be accessible from EM console, thus no High Availability is achieved at EMAGENT level from EM console and thus no performance metrics displayed at all for DIP2 Node2.
2. So from Fusion Middleware Enterprise Manager Console, when selecting DIP1 and DIP2 instances under "Identity And Access", and on Right Frame select DIP Menu--> General Information, the DIP2 instance which is running on node2 is referring to same EMAGENT on node1. This means EMAGENT of DIP1 on node1 is shared with node2 DIP2 and thus High Availability is not achieved. This also causes Metrics of DIP2 instance not to be displayed in the FMW EM Console. If EMAGENT of DIP1 on node1 is down then DIP1 and DIP2 metrics are not at all displayed.
+.FMW EM Console DIP1 Instance screen shot for Clarification:
+.FMW EM Console DIP2 Instance Screen shot for Clarification:
This feature was identified as a Bug 25727060 and new command was developed and released to create EMAGENT on second node where DIP2 instance is running. This new command is going to be included in future OUD Document release.
For now this Article can be followed as an alternate reference until included officially in OUD Document.
New option setupEMAgent for dipconfigurator command was developed and released.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document