Post-Patching Tasks for Your WebLogic Server Domain

)

4. Restart the Portal Managed Server.

3.9.5.7 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.6.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 Administrator's Guide for Oracle Portal before your Oracle Portal instance will be functional again.

3.9.6 Post-Patching Tasks for Your WebLogic Server Domain

Your existing WebLogic Server Domain must be updated by performing the following tasks:

■ Section 3.9.6.1, "Updating Fusion Middleware Shared Libraries"

■ Section 3.9.6.2, "Updating Configurations and Stores"

■ Section 3.9.6.3, "Enabling WS-AtomicTransaction"

■ Section 3.9.6.4, "Optimizing Performance for WebLogic Server Domains on 64-Bit Platforms"

3.9.6.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:

Note: If you are patching Oracle WebCenter Portal, you do not need to run this command if you follow the directions in Chapter 5,

"Patching Oracle WebCenter".

Post-Patching Tasks

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 Administrator's Guide for more information.

2. Start WLST.

On UNIX operating systems:

cd oracle_common/common/bin ./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.9.6.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 11.1.1.6.0 configurations and stores using a system-jazn-data file in Release 11.1.1.6.0.

Before running this command, start WLST as shown below:

On UNIX operating systems:

cd MW_HOME/oracle_common/common/bin ./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:

Note: After you run this command, any custom changes that you have made to your setDomainEnv script will be lost. Oracle recommends that you keep your custom modifications in a separate script that is called by setDomainEnv in order to minimize the disruption that is caused when other domain templates are applied and the setDomainEnv script is regenerated.

If you have set IPv6 to false in your setDomainEnv script, this change will be overwritten when you run the upgradeJRF() command. Make sure you reset IPv6 to false in the setDomainEnv script after you run the upgradeJRF() command.

Note: If you are patching Oracle WebCenter Portal, you do not need to run this script if you follow the directions in Chapter 5, "Patching Oracle WebCenter".

Post-Patching Tasks

upgradeOpss(jpsConfig="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/config/fmwconfig/jps-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.6.0 system-jazn-data.xml file, usually MW_HOME/oracle_common/modules/oracle.jps_11.1.1/domain_

config/system-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.9.6.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/config/fmwconfig/policy-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:

<interceptor name="ClientWSATInterceptor"

3. In the Interceptor Chains section:

■ <interceptor-ref name="ServerWSATInterceptor"/> should be added in the existing entry of SOAPServiceBindingInterceptorChain between the Context and RM interceptors. For example:

<interceptor-chain name="SOAPServiceBindingInterceptorChain"

@ class="oracle.integration.platform.common.SOAPBindingInterceptorChain">

<interceptor-ref name="MTOMInterceptor"/>

<interceptor-ref name="BindingSecurityInterceptor"/>

<interceptor-ref name="ServerAddressingInterceptor"/>

<interceptor-ref name="MEXInterceptor"/>

<interceptor-ref name="WSRMServerInterceptor"/>

<interceptor-ref name="ServerWSATInterceptor"/>

<interceptor-ref name="ContextInterceptor"/>

Post-Patching Tasks

<interceptor-ref name="BindingManagementInterceptor"/>

</interceptor-chain>

■ <interceptor-ref name="ClientWSATInterceptor"/> should be added in the existing entry of

SOAPReferenceBindingInterceptorChain between the Context and RM interceptors. For example:

<interceptor-chain name="SOAPReferenceBindingInterceptorChain"

@ class="oracle.integration.platform.common.SOAPBindingInterceptorChain">

<interceptor-ref name="BindingManagementInterceptor"/>

<interceptor-ref name="ContextInterceptor"/>

<interceptor-ref name="ClientWSATInterceptor"/>

<interceptor-ref name="WSRMClientInterceptor"/>

<interceptor-ref name="ClientAddressingInterceptor"/>

<interceptor-ref name="BindingSecurityInterceptor"/>

<interceptor-ref name="MTOMInterceptor"/>

</interceptor-chain>

3.9.6.4 Optimizing Performance for WebLogic Server Domains on 64-Bit Platforms

If you are upgrading any existing 11g Oracle WebLogic Domain to Release 11.1.1.6.0, it is recommended to make the changes in the setDomainEnv file as described below to optimize performance:

if [ "${JAVA_USE_64BIT}" = "true" ] ; then if [ "${JAVA_VENDOR}" = "Oracle" ] ; then

if [ "${JAVA_VENDOR}" = "Oracle" ] ; then

EXTRA_JAVA_PROPERTIES="-XX:+UseLargePagesForHeap

${EXTRA_JAVA_PROPERTIES}"

export EXTRA_JAVA_PROPERTIES fi

EXTRA_JAVA_PROPERTIES="-Djps.auth.debug=false ${EXTRA_JAVA_PROPERTIES}"

export EXTRA_JAVA_PROPERTIES

The applicable EXTRA_JAVA_PROPERTIES are described in

Table 3–8 Description of Parameters for EXTRA_JAVA_PROPERTIES

Property Description

-XXcompressedRefs This option governs the use of compressed references, limiting all pointers stored on the heap to 32 bits.

Compressed references use fewer Java heap resources and transport less data on the memory bus, thereby improving the performance. This option also frees space on the heap.

-XXcompressedRefs:enable=TRUE is applicable for the JRockit JVM running on a 64-bit operating system.

Post-Patching Tasks

In document Oracle Fusion Middleware (Page 62-66)