Java web start(JWS) in R12

In this post, we will be discussing Java web start implementation in R12/R12.1 and R12.2 versions of EBS. we will see why it is important to implement it

Table of Contents

What is Java Web start?

Java Web Start provides a browser-independent architecture for deploying Java technology-based applications to the client desktop. With Java Web Start, users can launch a Java application by clicking a link on a web page. The link points to a Java Network Launch Protocol (JNLP) file, which instructs Java Web Start software to download, cache, and run the application. This way, users can download and launch applications without going through additional installation procedures.

Why this is required in R12

All the modern-day browsers are ending support for Netscape Plug-in Application Programming Interface (NPAPI), which is used by the Java Plug-in. So basically you will not be able to use the Java applet technology we are using in EBS

Architecture difference between JWS and Java Plug-in

How to implement in R12/R12.1

(1) First, we need to apply all the patches mentioned in the Metalink doc

Using Java Web Start with Oracle E-Business Suite (Doc ID 2188898.1)

Minimum Prerequisites
The following lists the minimum code levels required to install Java Web Start on Oracle E-Business Suite Release 12.1.

Oracle E-Business Suite Release 12.1.3
R12.AD.B.Delta.8
R12.TXK.B.Delta.3
R12.ATG_PF.B.Delta.3

Oracle Forms 10g Technology Patch for Oracle E-Business Suite Release 12.2
Patch 25441839 – Merge Request On Top Of 10.1.2.3.2PSU For Bugs 24946444, 24620875, 25355211

Patches required to Implement JWS

24498616 AD: Add Java Web Start support to Oracle E-Business Suite
24319156:R12.TXK.B TXK: Add Java Web Start support to Oracle E-Business SuitePatch
25380324:R12.FND.B Oracle E-Business Suite Java Applets launching with Java Web StartPatch

(2) Once the patches are applied, Regenerate JAR files with the force option.

ADADMIN

(3) Update context file value for parameter s_forms_launch_method to jws from the browser on all the nodes

$ vi $CONTEXT_FILE
from browser
to jws

(4) Run autoconfig on all the nodes

This will set JWS for all the users by default.

(5) Start the application and Validate

How to implement in R12.2

(1) First, we need to apply all the patches mentioned in the Metalink doc

Using Java Web Start with Oracle E-Business Suite (Doc ID 2188898.1)

Minimum Prerequisites
The following lists the minimum code levels required to install Java Web Start on Oracle E-Business Suite Release 12.2

Oracle E-Business Suite Release 12.2.3
R12.AD.C.Delta.8
R12.TXK.C.Delta.8
R12.ATG_PF.C.Delta.6

Oracle Forms 10g Technology Patch for Oracle E-Business Suite Release 12.2
Patch 25441839 – Merge Request On Top Of 10.1.2.3.2PSU For Bugs 24946444, 24620875, 25355211

Patches required to Implement JWS

AD: Add Java Web Start support to Oracle E-Business Suite Patch 24498616:R12.AD.C
TXK: Add Java Web Start support to Oracle E-Business Suite Patch 25449925:R12.TXK.C
Oracle E-Business Suite Java Applets launching with Java Web Start Patch 25380324:R12.FND.C

(2)

Once the patches are applied, Regenerate JAR files with the force option.

ADADMIN

You can do both of the above using the Online patching cycle below to reduce the downtime

$ source /EBSapps.env run
$ adop phase=prepare
$ source /EBSapps.env patch
$ adop phase=apply patches=24498616,25449925,25380324 merge=yes
Use the AD Administration tool (adadmin) to regenerate JAR files with the force option.
$ source /EBSapps.env patch
$ adadmin
$adop phase=finalize,cutover
$ source /EBSapps.env run
Perform a cleanup of the online patch cycle.
$ adop phase=cleanup

(3) Update context file value for parameter s_forms_launch_method to jws from the browser on all the nodes in the run filesystem

$ vi $CONTEXT_FILE
from browser
to jws

(4) Run autoconfig on all the nodes

This will set JWS for all the users by default.

(5) Start the application and Validate

Important points for JWS implementation

We do have product-specific patches to enable support for JWS, if you are using the products please apply those patches as well
We do have browser-specific patches, please apply them accordingly
Please do check the Metalink note for all the latest patches before implementing JWS, as the patches mentioned in this post will get obsoleted with time

How to Implement old Java Plug-in for a few users when JWS is the default

To enable the Java Plug-in for one or more application users, set the following two profile options at the user level:

'Enable Java Web Start' is set to No
'ICX: Forms Launcher' set to <s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_webport>/forms/frmservlet?config=browserMode

How to Implement JWS for a few users when Java plug-in is the default

To enable Java Web Start for one or more application users, set the following two profile options at the user level:

Enable Java Web Start is set to Yes
ICX: Forms Launcher set to <s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_webport>/forms/frmservlet?config=jws

Hope you like this post on Java web start in R12