12 November 2017

WLS domain extension to include JRF template

Extend a domain (/wls_domains/base_domain ) by including JRF restricted template & it works fine
without the use of any database. (in order to have JRF features in plain WLS domain)

Template to use:(/MW_HOME/oracle_common/common/template/wls/Oracle_jrf_restricted.jar)

Alternatively, you can use the following JAVA_argument to include in config.sh which allows you to create a compact domain and will use Embedded Database (JAVADB)
CONFIG_JVM_ARGS  to -Dcom.oracle.cie.config.showProfile=true
But when OIM 11.1.1.9 is being configured on top of it, it is overwriting the configuration files from MW_HOME and not allowing the domain to come up
(compatibility challenge here)

**
Exception in thread "main" java.lang.NoSuchMethodError: weblogic.i18n.logging.CatalogMessage.(Ljava/lang/String;I[Ljava/lang/Object;Lweblogic/i18n/Localizer;)V
        at weblogic.security.SecurityLogger.logDisallowingCryptoJDefaultJCEVerification(SecurityLogger.java:15099)
        at weblogic.security.utils.SecurityUtils.turnOffCryptoJDefaultJCEVerification(SecurityUtils.java:98)
**

Also when we try to set up OVD using 11g installer it is expecting to have wlserver10.3, but we have /12.2.1.2/wlserver, so not allowed to proceed further.

The only possible way is to have 2 WLS domains running on 11g & 12c to serve their functionality respectively.

What Oracle has to say on this - 

There is no exception from the certification matrix. OVD is not (and I do not have information that will be in the future) certified with Weblogic 12c.
However, please note that you can have Weblogic 12c and Weblogic 11g (10.3.6) on the same server running on different ports.
So you may create a OVD domain in Weblogic 11g (10.3.6) and keep weblogic 12c for your current purposes.