Updating Configuration Properties in Oracle Identity Federation

Applying the Latest Oracle Fusion Middleware Patch Set 3-17 3. Run the following emCCR commands: emccr stop emccr start emccr status

3.8.4.4 Resolving JDBC Errors in Oracle Reports and Oracle Portal

If you have Oracle Reports or Oracle Portal configured in a domain and you apply the latest patch set, you will see the following error if you try to change the invalidation password: Error. Check logs for details. [OK]. The following errors are seen in the portal_wls.log and wls_portal.out log files: Date and time Warning RMI BEA-080003 RuntimeException thrown by rmi server: javax.management.remote.rmi.RMIConnectionImpl.invoke Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava. lang.String;Ljavax.security.auth.Subject; javax.management.RuntimeErrorException: oracle.jdbc.driver.T2CConnection.getLibraryVersionNumberI.javax.management.Runti meErrorException: oracle.jdbc.driver.T2CConnection.getLibraryVersionNumberI at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvokeOra cleStandardEmitterMBean.java:991 at oracle.adf.mbean.share.AdfMBeanInterceptor.internalInvokeAdfMBeanInterceptor.java :104 at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke AbstractMBeanInterceptor.java:252 .... Caused By: java.lang.UnsatisfiedLinkError: oracle.jdbc.driver.T2CConnection.getLibraryVersionNumberI at oracle.jdbc.driver.T2CConnection.getLibraryVersionNumberNative Method at oracle.jdbc.driver.T2CConnection1.runT2CConnection.java:3537 at java.security.AccessController.doPrivilegedNative Method at oracle.jdbc.driver.T2CConnection.loadNativeLibrary T2CConnection.java:3532 .... You must perform the following in order to avoid these JDBC error messages: 1. Go to the bin directory inside your DOMAIN_HOME . 2. Edit the setDomainEnv.sh on UNIX operating systems or setDomainEnv.cmd on Windows operating systems file and search for EXT_ PRE_CLASSPATH. 3. Change the definition to match the following: On UNIX operating systems: EXT_PRE_CLASSPATH=ORACLE_HOMEjdbclibojdbc6.jar export EXT_PRE_CLASSPATH On Windows operating systems: 3-18 Oracle Fusion Middleware Patching Guide EXT_PRE_CLASSPATH=ORACLE_HOME\jdbc\lib\ojdbc6.jar 4. Restart the Portal Managed Server.

3.8.4.5 Updating the Configuration in SSL-Enabled Oracle Portal Instances

Due to security changes in WebLogic Server, if you were running an SSL-enabled 11g version of Oracle Portal and patched it to Release 11.1.1.5.0, you will need to perform the steps mentioned in the Enable the WebLogic Plug-In, and WLProxySSL and WLProxySSLPassThrough Parameters section of the Oracle Fusion Middleware Administrators Guide for Oracle Portal before your Oracle Portal instance will be functional again.

3.8.5 Post-Patching Tasks for Your WebLogic Server Domain

Your existing WebLogic Server Domain must be upgraded by performing the following tasks: ■ Section 3.8.5.1, Updating Fusion Middleware Shared Libraries ■ Section 3.8.5.2, Updating Configurations and Stores ■ Section 3.8.5.3, Enabling WS-AtomicTransaction

3.8.5.1 Updating Fusion Middleware Shared Libraries

For each WebLogic Server domain, you must run the updateJRF WLST command to update the shared libraries in your domain: 1. Stop all running instances, Managed Servers, Administration Server, and Node Manager in the domain. See Starting and Stopping Oracle Fusion Middleware in Oracle Fusion Middleware Administrators Guide for more information. 2. Start WLST. On UNIX operating systems: cd oracle_commoncommonbin .wlst.sh On Windows operating systems: cd oracle_common\common\bin wlst.cmd 3. Run the upgradeJRF command on the node or system where the Administration Server is located for each domain you want to update. Your domain location is passed as a parameter: wlst upgradeJRF DOMAIN_HOME

3.8.5.2 Updating Configurations and Stores

For each WebLogic Server domain, you must run the upgradeOpss WLST command to update your configurations and stores from previous releases to Release Note: If you are patching Oracle WebCenter, you do not need to run this command if you follow the directions in Chapter 5, Patching Oracle WebCenter.