Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12

In This Document

• Section 1: Overview
• Section 2: Pre-installation Steps
• Section 3: Upgrade and Configuration
• Section 4: Post-installation Steps

This document covers the procedure to upgrade the version of the JRE Native Client being used in Oracle E-Business Suite R12.
Note 1: Oracle strongly recommends that Oracle E-Business Suite R12 customers move to the latest and therefore most secure certified version of the JRE Native Plug-in on either the JRE 7 stream, JRE 1.7.0_45 (7u45), or the JRE 6 stream, JRE 1.6.0_65 (6u65). For further information about new functionality and other changes in these Limited Update (LU) releases, see the associated release notes:

Update Release Notes for Java 1.7.0
Update Release Notes for Java 1.6.0

Section 1: Overview

The Oracle E-Business Suite R12 has two interfaces: a web-based model for modules like iProcurement and iStore, and an Oracle Forms-based model for our professional services modules like Oracle Financials.
This document will explain the steps needed to upgrade to the latest certified version of JRE Native Client for supporting forms-based modules used with Oracle E-Business Suite R12. It is important that you read and follow this document in its entirety before starting an upgrade or applying any patch.

JRE 7 Minimum Patch Requirements

Oracle E-Business Suite 12.2.x

Currently, Oracle E-Business Suite 12.2 users do not require any prerequisite patches to run JRE 7.

Oracle E-Business Suite 12.0.x and 12.1.x

The JRE 7 Plug-in is certified for Oracle E-Business Suite R12.0.x and 12.1.x with the following minimum patch requirements:

Windows XP SP3, Windows Vista SP1 & SP2, Windows 7 & Windows 7 SP1 (32-bit & 64-bit) and Windows 8 (32-bit & 64-bit)

• Oracle forms 10.1.2.3 or higher with Patch 14614795 or later

Section 2: Pre-installation Steps

Step 1. Source the Environment

Source your environment as appropriate to your Oracle E-Business Suite release.

Oracle E-Business Suite 12.2.x Users

Upgrading the JRE Plugin can be done outside of a patch cycle against the RUN file system.

On the Application tier as the file system owner source your RUN file system.

Oracle E-Business Suite 11i, 12.0.x and 12.1.x Users

On the Application tier as the file system owner source your APPS env file.

Step 2. Download the Interoperability Patch and the JRE Plugin

Oracle E-Business Suite 12.2.x Users

Patch 14614795
Follow the below steps to upgrade the sun JRE:

First of all, follow the above mention note ID ( 393931.1) as well as follow the patch redme file.

1. ) Upgrade the Oracle form server, down load patch p6640838_10106_LINUX.zip

this patch apply through rapid wizard, login through application user [applmgr] and follow the patch redme

before installing this patch, pls take the back of ORACLE_HOME (10.1.2)

$ mv $ORACLE_HOME/OPatch $ORACLE_HOME/OPatch.pre_6640838

unzip the patch p6649838.zip

$ unzip p6640838.zip

$chmod 755 cd/Disk1/install/runInstaller

$chmod 755 cd/Disk1/install/unzip

$cd cd/Disk1/install/

$./runIstaller -ignoreSysPrereqs

click on below snap_shot to follow the instraction

 

click on "Next"

select "ORACLE_HOME"

click on "Custom"

                                                               DE-SELECT THE OPTION 2^ND

                                                               AND SELECT THE OPTION 3^RD

click on "OK"

 

                                              Click on “Expand all”

                                             And follow the above snapshot.

                                             Click on NEXT

click on "Install"

Click on "Yes"

 

2.) after apply the above patch the upgrade the opatch version as per oracle recommendation (Doc ID 437878.1)

download patch 6880880 and select the release Oracle 10.1.0.0.0

p6880880_101000_LINUX.zip

copy the patch in ORACLE_HOME (10.1.2)

$ cp p6880880_101000_LINUX.zip $ORACLE_HOME

$unzip p6880880_101000_LINUX.zip

3.) Now we will apply forms Bundle patch 9593176.

first of all, before ally this patch need to set the OPatch

$ export PATH=$ORACLE_HOME/OPatch:$PATH

$ unzip p9593176.zip

$ cd 9593176/

$ opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc

4.) Now we will apply Forms Over lay patch 14614795

$ unzip p14614795.zip

$ cd 14614795/

$ opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc

we have done with all installs which are needed to install Forms Bundle patch and overlay patches.

Note:- Before apply the above patch, check in "opatch lsinventry"

Step 4. Apply the Interoperability Patch

If not applied previously apply the JRE Plug-in interoperability Patch 4377566 by following the steps below:Step 4.1. Enable Maintenance Mode

To enable maintenance mode please follow the steps below:

Step 4.1.1. Shutdown Apache

Shutdown Apache (on normal mode) by running adapcctl.sh stop or by running adstpall.sh apps_user/apps_password

Step 4.1.2. Enable 'Maintenance Mode' from adadmin

Enable 'Maintenance Mode' from adadmin, (Select menu option 5 - Change Maintenance Mode - Select menu option 1 - Enable Maintenance Mode)

 

Step 4.2. Apply the JRE Interoperability Patch (UNIX Users only) (If Required)
If your application-tier server nodes are running on Microsoft Windows Server, 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 in the interop patch using AutoPatch.
If you are upgrading to 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. Skip this step and continue to

step 4.2.2.

Run the $FND_TOP/bin/txkSetPlugin.sh script against the web node of the application tier.The txkSetPlugin.sh script update's the JRE version information in your AutoConfig context file and run's 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. 16026). This value is listed in the 'jversion Parameter' column in the appendices section under JRE Parameter Settings.

For example; the command to install JRE 1.7.0_10 is:

Rename the downloaded JRE Native Plugin file to j2se.exe
For example:

jre-7u21-windows-i586.exe or jre-7u21-windows-x64.exe would be renamed j2se17021.exe
jre-6u45-windows-i586.exe or jre-6u45-windows-x64.exe would be renamed j2se16045.exe
jre-6u7-windows-i586.exe would be renamed j2se16007.exe

Oracle E-Business Suite 12.2.x Users

Move the j2se1700X.exe file to the web application tier and place it in the following directory in the RUN File System:

$[COMMON_TOP]/webapps/oacore/util/javaplugin

Oracle E-Business Suite 12.0.x and 12.1.x Users

Move the j2se1700X.exe file to the web application tier and place it in the following directory:

$[COMMON_TOP]/webapps/oacore/util/jinitiator

Step 4.2.2. Run the txkSetPlugin.sh Script

 

Run the $FND_TOP/bin/txkSetPlugin.sh script against the web node of the application tier.The txkSetPlugin.sh script update's the JRE version information in your AutoConfig context file and run's 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. 16026). This value is listed in the 'jversion Parameter' column in the appendices section under JRE Parameter Settings.For example; the command to install JRE 1.7.0_10 is:

txkSetPlugin.sh 17010

Step 5: Compile the jar file through adadmin utility.

step 6: Disable the maintenance mode and start the application.

:)