Updating Oracle Configuration Manager Windows Only

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. Applying the Latest Oracle Fusion Middleware Patch Set 3-19 11.1.1.5.0 configurations and stores using a system-jazn-data file in Release 11.1.1.5.0. Before running this command, start WLST as shown below: On UNIX operating systems: cd MW_HOME oracle_commoncommonbin .wlst.sh On Windows operating systems: cd MW_HOME \oracle_common\common\bin wlst.cmd After WLST is started, run the upgradeOpss command. The syntax for the command is below: upgradeOpssjpsConfig= existing_jps_config_file , jaznData= system_jazn_data_ file ■ existing_jps_config_file Full path to the location of the existing jps-config.xml file, usually DOMAIN_ HOME configfmwconfigjps-config.xml on UNIX operating systems or DOMAIN_HOME \config\fmwconfig\jps-config.xml on Windows operating systems. ■ system_jazn_data_file Full path to the location of the Release 11.1.1.5.0 system-jazn-data.xml file, usually MW_HOME oracle_commonmodulesoracle.jps_11.1.1domain_ configsystem-jazn-data.xml on UNIX operating systems or MW_ HOME \oracle_common\modules\oracle.jps_11.1.1\domain_ config\system-jazn-data.xml on Windows operating systems. For more information, see Upgrading Policies with upgradeOpss in Oracle Fusion Middleware Security Guide.

3.8.5.3 Enabling WS-AtomicTransaction

WS-AtomicTransaction is a web services feature which was introduced in Oracle Fusion Middleware Release 11.1.1.3.0 release. If you are upgrading a domain which is at the 11.1.1.2.0 release, then you need to perform the following steps to ensure that WS-AtomicTransactions are enabled: 1. Edit the following file. On UNIX operating systems: DOMAIN_HOME configfmwconfigpolicy-accessor-config.xml On Windows operating systems: DOMAIN_HOME \config\fmwconfig\policy-accessor-config.xml 2. In the Interceptors section, add the following XML code: Note: If you are patching Oracle WebCenter, you do not need to run this script if you follow the directions in Chapter 5, Patching Oracle WebCenter.