Step 2. Rename the JRE Plug-in and Place it on Webserver

Step 2.1. Rename the JRE 6 Native Plug-in

If you are upgrading on the JRE 5.0 family, skip this step and proceed to Step 2.2.

Rename the downloaded JRE Native plug-in file from jre-6_uX-windows-i586-p.exe to j2se160X.exe

(Where X = the version number. (For single digit version numbers, please prefix the version number with a zero). Using jre-6u7 as an example X would be 07, so the file would be renamed j2se16007.exe).

Step 2.1.1. Place the JRE 6 Plug-in on the Web Application Tier

Move the j2se160X.exe file to the web application tier and place it in $[COMMON_TOP]/util/jinitiator.

[COMMON_TOP] refers to the top level directory where the common utilities are installed. By default, this is the parent directory of $JAVA_TOP. See the 'Installing Oracle Applications' manual for more details on the Oracle E-Business Suite file system.

Proceed to Step 3.

Step 2.2. Rename the JRE Native Plug-in

Rename the downloaded JRE Native plug-in file from jre-1_5_0_X-windows-i586-p.exe to j2se150X.exe

(Where X = the version number. For example; jre-1_5_0_13-windows -i586-p.exe would be renamed j2se15013.exe).

Step 2.2.1. Place the JRE Plug-in on Web Application Tier

Move the j2se150X.exe file to the web application tier and place it in $[COMMON_TOP]/util/jinitiator.

[COMMON_TOP] refers to the top level directory where the common utilities are installed. By default, this is the parent directory of $JAVA_TOP. See the 'Installing Oracle Applications' manual for more details on the Oracle E-Business Suite file system.

Step 3. Apply Prerequisite Patches (Conditional)

If you are using Developer 6i Patchset 17 (6.0.8.26.x) or earlier, you must upgrade to Developer 6i Patchset 18 (6.0.8.27.x) or later.

(For information on upgrading the 6i Developer patchset, please see note 125767.1 titled, 'Upgrading Developer 6i with Oracle Applications 11i').

Developer 6i Patchset 19 Users

Developer 6i Patchset 19 (6.0.8.28.x) users must apply the forms focus fix patch 8402746.

Developer 6i Patchset 18 Users

Developer 6i Patchset 18 (6.0.8.27.x) users must apply the forms focus fix patches 7362389 and 5884875.

Step 4. Apply the Interoperability Patch

Apply the JRE plug-in Interoperability patch 6863618 by following the steps below.

(Users must be AutoConfig enabled to upgrade to the Sun JRE Native plug-in. For more information about AutoConfig, please refer to note 165195.1 titled, 'Using AutoConfig to Manage System Configurations with Oracle Applications 11i'). 

Step 4.1. Enable Maintenance Mode

If you are using Oracle Applications Release 11.5.10 or Minipack 11i.AD.I or later, you must enable 'Maintenance Mode' before applying the patch driver from the JRE Interoperability Patch, as follows;

Step 4.1.1. Shutdown Apache

Shutdown Apache (on normal mode) by running;

adapcctl.sh stop
or
adstpall.sh <apps_user>/<apps_pwd>

Step 4.1.2. Enable 'Maintenance Mode'

Enable 'Maintenance Mode' by running adadmin, and selecting the following options;

Select menu option 5, 'Change Maintenance Mode'
Select menu option 1, 'Enable Maintenance Mode'

(For further information on Maintenance Mode please review note 291901.1 titled, 'Maintenance Mode - A New Feature in 11.5.10')

Step 4.2. Apply the JRE Interoperability Patch (UNIX Users only)

If your application-tier server nodes are running Microsoft Windows, skip this step and proceed to Step 4.3.

Applying the JRE Interoperability Patch for the first time is a two stage process:

Step 4.2.1. Apply the Patch Driver

If you are upgrading to the JRE native plug-in for the first time, please apply the interop patch using AutoPatch.

Note:If you wish to alter the JRE version you are currently running and have previously applied the interop patch on your environment, there is no need to apply it again. Please skip this step and continue to step 4.2.2 below.

Step 4.2.2. Run the txkSetPlugin.sh Script

Run the txkSetPlugin.sh script from the <patch_top>/<interop_patch_number>/fnd/bin/ directory, against the web node of your middle tier, where <patch_top> is the directory in which you unzipped this patch.

The txkSetPlugin.sh script will update the new JRE version information into your AutoConfig context file, update the version used by Workflow and run AutoConfig to incorporate the new values throughout your application. This script must be run using the following command:

txkSetPlugin.sh <jversion>

Where: <jversion> represents the JRE version you wish to install, without decimal points or underscores. (e.g. 16003)
This value is listed in the '<jversion> Parameter' column of appendix JRE Parameter Settings.

For example; the command to install JRE 1.6.0_03 is:

txkSetPlugin.sh 16003

The script will prompt you for the following values, if it does not find them automatically:

·                          Location of APPSORA.env file, if not present in the default location $APPL_TOP.

·                          Location of the AutoConfig Context File.

·                          Password for the APPS user in the database (If the correct value is returned by the script you may press the return key at the prompt).

Step 4.2.3. Multiple Application-Tier Web Server Nodes

If you have multiple web application tier server nodes, repeat the steps above to apply the patch driver in the JRE Interoperability Patch against all other web application tier server nodes.

Step 4.3. Apply the JRE Interoperability Patch (Windows Users only)

If your application-tier server nodes are running UNIX, skip this step and proceed to Step 4.4.

Applying the interop patch for the first time is a two stage process;

Step 4.3.1. Apply the patch driver in the interop patch using AutoPatch.

If you are upgrading to the JRE native plug-in for the first time, please apply the interop patch using AutoPatch.

Note: If you wish to alter the JRE version you are currently running and have applied this patch previously, there is no need to apply it again. Please skip this step and continue to Step 4.3.2. below.