Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i

Introduction
 
This document describes the steps needed to replace the use of Oracle JInitiator with the Sun JRE Native Client in Oracle E-Business Suite 11i. This document also covers the procedure to upgrade the version of the Sun JRE Native Client being used in Oracle E-Business Suite 11i.

 
Prerequisites
 
JRE native plug-in is certified with the Oracle E-Business Suite 11i, with the following minimum requirements:
Windows XP SP2, SP3 or Microsoft Windows 2000Oracle Applications 11.5.9 or later Oracle Developer 6i Patchset 18 (6.0.8.27.x) or later Windows Vista & Vista SP1 *                       Oracle Applications 11.5.9 CU2 with ATG.RUP4 or later                        Oracle Applications 11.5.10 CU2 with ATG.RUP4 or later                        Oracle Developer 6i Patchset 18 (6.0.8.27.x) or later The table below outlines the certified Browser and Operating System for both the JRE 6 and JRE 5.0 streams and shows the minimum required version as applicable:

Browser Version Windows Vista & Vista SP1 Windows XP SP2 & SP3 Windows 2000
MSIE 7
JRE 1.6.0_03 or later JRE 1.6.0_03 or later Not Certified
JRE 1.5.0_12 or later JRE 1.5.0_12 or later
MSIE 6
Not Certified JRE 1.6.0_03 or later JRE 1.6.0_03 or later
JRE 1.5.0_12 or later JRE 1.5.0_12 or later
Firefox 2.0.x
Not Certified JRE 1.6.0_03 or later Not Certified
JRE 1.5.0_12 or later
Firefox 1.5.x
Not Certified JRE 1.5.0_12 or later Not Certified

 Installation & Configuration  

1. Download the JRE Plug-in Oracle E-Business Suite interoperability patch

Download the JRE plug-in Oracle E-Business Suite interoperability Patch 6863618 from Metalink.

.

2. Download the Sun JRE Plug-in
 Download Sun Jre 5 or 6
it can be downloaded from the Sun archive site at, http://java.sun.com/products/archive/
 . Select the required release from the drop down menu under, Java 2 Platform Standard Edition (J2SE) -> JDK/JRE – 6 . Select the Download JRE. Download the Windows Offline Installation, Multi-language version of the plug-in.
.

3. Rename the JRE Plug-in and Place it on Webserver
Transfer the file from your windows client to your server  and Copy it in $COMMON_TOP/util/ jinitiator.The download file name will look like :-
-rw-r–r–   1 oarm dba      15951256 Oct  2 15:31 j2se1600X.exe
Rename this file to
-rw-r–r–   1 oarm dba      15951256 Oct  2 17:19 j2se16003.exe

.
4.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 follow metalink note 125767.1

.
5.Apply the Interoperability Patch
(Users must be AutoConfig enabled to upgrade to the Sun JRE Native plug-in.)

.
6.Check The patch Pre-req
Read patch readme doc and check for the patch pre-req .
The list of pre-req patches are :- 2625845, 3817226 and 2565888
SQL> select * from ad_bugs where BUG_NUMBER=’&no’
  2SQL> /
Enter value for no: 2625845
old   1: select * from ad_bugs where BUG_NUMBER=’&no’
new   1: select * from ad_bugs where BUG_NUMBER=’2625845′
    BUG_ID APPLICATION_SHORT_NAME
———- ————————————————–
BUG_NUMBER                     CREATION_DATE   ARU_RELEASE_NAME
—————————— ————— ——————————
CREATED_BY LAST_UPDATE_DAT LAST_UPDATED_BY
———- ————— —————
     81287
2625845                        26-JUN-03       11i
         5 26-JUN-03                     5
 
Make sure that above all the patches and his pre-reqs are applied successfully.

.
Enable Maintenance Mode

Set up your application enviournment and run Adadmin utility to change the system in maintenance mode
Enter your choice [6] : 5
            Change Maintenance Mode
   —————————————-
Maintenance Mode is currently: [Disabled].
Maintenance mode should normally be enabled when patching
Oracle Applications and disabled when users are logged on
to the system.  See the Oracle Applications Maintenance
Utilities manual for more information about maintenance mode.
Please select an option:
   1.    Enable Maintenance Mode
   2.    Disable Maintenance Mode
   3.    Return to Main Menu
Enter your choice [3] : 1
sqlplus -s &un_apps/***** @/h10/RP1/oraapps/11iApp/ad/11.5.0/patch/115/sql/adsetmmd.sql ENABLE
Successfully enabled Maintenance Mode.

.
7.Shutdown Apache
It is a good practice to shut down all the application services , so better to stop all the services
Go to $COMMON_TOP/admin/scripts/$CONTEXT_NAME execute the below script
$ adapcctl.sh stop (Only Apache )
$adstpall.sh <apps_user>/<apps_pwd> (All the services)
.
8.Apply the Patch Driver
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
For example :-
/home/oarm/6863618/fnd/bin
[oarm uss01 RP1] $ ls -l
total 74
-rw-r–r–   1 oarm dba          649 Oct  3 10:42 L375026.log
-rwxr-xr-x   1 oarm dba        15843 Jan  1  2002 txkSetPlugin.cmd
-rwxr-xr-x   1 oarm dba        20409 Jan  1  2002 txkSetPlugin.sh
Run the script
txkSetPlugin.sh <jversion>
For example , In my case the J2E version was
j2se1600X.exe
So it should be $
txkSetPlugin.sh  16003
[oarm uss01 RP1] $ txkSetPlugin.sh 16003
/home/oarm/6863618/fnd/bin
   Starting interoperability upgrade script...
 Sending logfile output to:
        /h10/RP1/oraapps/11iApp/admin/log/txkSetPlugin.log
Using the context file:
        /h10/RP1/oraapps/11iApp/admin/RP1_uss01.xml
Using APPLSYS file:
        /h10/RP1/oraapps/11iApp/APPSRP1_uss01.env
Enter the password for the Oracle database APPS user [APPS] :
Configuring IMT_TOP.......COMPLETED
        Configuring FTE_TOP.......COMPLETED
        Configuring ONT_TOP.......COMPLETED
        Configuring AR_TOP........COMPLETED
        Configuring AHL_TOP.......COMPLETED
        Configuring OZF_TOP.......COMPLETED
        Configuring IES_TOP.......COMPLETED
        Configuring CSD_TOP.......COMPLETED
        Configuring IGC_TOP.......COMPLETED
AutoConfig completed successfully.
Upgrading j2se16003 for Oracle Workflow...
  Oracle Workflow upgraded successfully...
Done
(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.)9.Post-Installation Steps
Once the JRE plug-in has been installed on your client, follow these steps to verify that you have successfully upgraded JRE.

.

10 Enable Java Console

Enable the Java Console on your PC through the ‘Java Control Panel’ by clicking on the ‘Java’ icon within your desktop clients ‘Control Panel’. Select the ‘Advanced’ Tab and expand the ‘Java Console’ field. Make sure the ‘Show Console’ option is selected.

11. Close Browser Windows

Close all browser windows. Wait a minute or so after the windows are closed until the processes have finished saving their data to disk.

12 Sign into Oracle E-Business Suite

Sign into Oracle E-Business Suite, and choose a Forms-based (Professional user interface) responsibility.

You need admin rights to in your PC/Laptop to install the aboveClick install to proceed .

2.4Check the Console Window

A window titled Java Console will appear, and should display lines describing the version.

Reference :-Metalink Note 290807.1 

About the Author Rajat

I am Rajat Dey and I have more than decade of Oracle experience from all major regions throughout the globe. I am well versed in most facets of Oracle, supporting database, fusion middleware and the eBusiness suite across many operating system platforms.Currently I am located in Sydney  Oracle Financials 11i and Release 12,12.2  Oracle RDBMS 7x,8i , 9i,10g and 11g  Amazon cloud .  Oracle RAC 10g and 11g  Oracle Applications Server  Oracle Web logic Server  OBIEE  Hyperion  SSO  Oracle Portal  PL/SQL  UNIX  SQL  MS-SQL 2008.  OEM 12c .  Data Guard .  Essbase .  Database backup and recovery.  Performance Tunning.  TimeSten

Leave a Comment:

8 comments
Add Your Reply