Extending WebLogic Domain to include JRF Changes from Custom Realm to Default Realm (Doc ID 2280270.1)

Last updated on MARCH 27, 2024

Applies to:

Symptoms

If weblogic domain default realm is changed from myRealm to custom Realm and it is extended to include Enterprise Manager, jrf and coherence extensions; the default realm is changed back to "myRealm" from custom Realm.

Steps to Reproduce:

1. Download fmw_12.1.3.0.0_infrastructure.jar

2. Install it using the command

java -jar fmw_12.1.3.0.0_infrastructure.jar

3. Run config.sh from ORACLE_HOME/oracle_common/common/bin

4. Create weblogic domain with Admin and managed server

5. Create new Test Relam relam by adding this to config.xml

6. From console ---domain name ---security change the new TestRelam as default relam

7. Restart services and confirm everything is fine.

8. Apply <Patch 20952475> - CUSTOM SECURITY DISAPPEARED AFTER EXTENDING THE WLS DOMAIN

9. Run rcu from ORACLE_HOME/oracle_common/common/bin and loaded schemas.

10. Run config.sh again from ORACLE_HOME/oracle_common/common/bin

11. Extend domain to include Enterprise Manager, jrf and coherence extensions.

12. Extend domain completes successfully.

13. Now start Admin Server and we see that default relam is changed back to myRelam

<default-realm>myrealm</default-realm

Changes

Cause

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