How to Configure Multicast on a Secondary NIC in OIM Servers
(Doc ID 1929573.1)
Last updated on SEPTEMBER 26, 2016
Applies to:Identity Manager - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Scenario: In your environment you have a clustered configuration with OIM servers on different physical machines and each machine has a pair of Network Interface Cards (NIC). The primary NIC provides a TCP interface that is routed though load balancers, routers, and/or other network devices. To make configuration simpler, you have joined all the machines requiring multicast to a second NIC which interconnects the machines on a single LAN or VLAN.
The problem is that OIM uses jgroups for cache coordination between machines. This multicast is necessary even if you have not enabled caching for the configurable cache categories. The version of jgroups being used only allows for the configuration of a NIC address for binding and the configuration file (oim-config.xml) is shared by all of the OIM servers in the domain.
If the bind_addr is not configured, jgroups will bind to the first non-loopdack NIC which would be the primary NIC. How, with a shared configuration file, is it possible to configure the OIM cache provider to bind to the secondary NIC in each physical machine?
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