Oracle Access Manager 11g R2PS3 (OAM 11.1.2.3) OIM Integration - Upgrade to 12c Prerequisite - Requires OPSS OAM/OIM Schema to be Split (Doc ID 2423473.1)

Last updated on AUGUST 31, 2023

Applies to:

Goal

1. OAM OIM Integration 11.1.2.3 - Upgrade to 12c Prerequisite - Requires OPSS OAM/OIM Schema to be Split (Corner case were OIM and OAM share the same OPSS Schema)

• Internal Note for now
• OPSS OAM/OIM schema split, more streamlined version OAM 11.1.2.3 upgrade to 12c
• Living document
• Possible solution - tested internally and it worked. Thought is to have additional customers who run into this issue to try this approach and modify as needed.
• Once it get more vitrification and to its success we will then make the note available to the public.

2. OAM and OIM 11.1.2.x needs to be in separate domains. For this specific case they were already in separate WLS domains.

3. EDG the only examples shown have OAM and OIM in their own domain, in fact in the product docs you will see that it even states “ All IdM components, including Access Manager server (<OAM_HOSTNAME>), the Oracle Identity Governance server (<OIG_HOSTNAME>), and Oracle Internet Directory (OID) are configured in separate WebLogic domains, and each is administered by its own administration server.”

4. Oracle Access Management 12.2.1.3.0 Product documentation set

5. It has been verified that the OPSS Schema is shared

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.