7 Implementing Java Web Start(JWS) in EBS R12.2.14

 

Implementing Java Web Start in Oracle E-Business Suite Release 12.2

Overview

Java Web Start provides a browser-independent architecture for deploying Java technology-based applications to client desktops. Users can launch Java applications by clicking a link in a web page, which points to a Java Network Launch Protocol (JNLP) file. This file instructs Java Web Start software to download, cache, and run the application, eliminating the need for separate installation procedures.

The Java Web Start software is included as part of the Java Runtime Environment (JRE), so users do not need to perform any additional installation tasks.

Background and Business Need

Oracle E-Business Suite's Java-based content traditionally required browsers that support the Netscape Plug-in Application Programming Interface (NPAPI) plug-ins. However, many modern browsers have either phased out NPAPI support or were released without it, preventing the Java plug-in from functioning properly.

With Java Web Start, E-Business Suite 12.1 and 12.2 users can launch Java-based content (such as Oracle Forms) from browsers that do not support Java plug-ins via NPAPI. Java Web Start in EBS works with:

• Microsoft Internet Explorer

• Microsoft Edge

• Firefox Rapid Release (32-bit and 64-bit)

• Firefox Extended Support Release (32-bit and 64-bit)

• Google Chrome

Important Considerations

Only one instance per Java applet can run on the client PC at a time. Multiple instances of a specific Java applet cannot be launched, even when launched from different sessions or browsers. Attempting to open a second instance will display an appropriate warning message.

Implementation Steps

1. Client-Side Prerequisites

Install JRE 8 Update 181 or later on the client/desktop for end-users.

2. Minimum System Requirements

The following minimum code levels are required to install Java Web Start on Oracle E-Business Suite Release 12.2:

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

Environment Details for This Implementation:

• EBS Release: R12.2.14

• Database Version: 12.1.0.2

3. Verify Current JRE Version

Before proceeding, verify the current Java version in your EBS environment:

bash

[applmgr@fbsebs ~]$ java -version
java version "1.7.0_85"
Java(TM) SE Runtime Environment (build 1.7.0_85-b15)
Java HotSpot(TM) Server VM (build 24.85-b06, mixed mode)

Note: All patches used in this implementation are stored in the Patch Top of EBS. Familiarity with applying patches using adop and opatch utilities is assumed, as is knowledge of editing context files and running AutoConfig. Always review the README of all patches for detailed action plans.

4. Apply Oracle Forms 10g Technology Patch

Patch 25441839 - Merge Request On Top Of 10.1.2.3.2PSU For Bugs 24946444, 24620875, 25355211 is the minimum required Oracle Forms 10g overlay patch that adds Java Web Start support to Oracle Forms as part of the EBS technology stack.

Procedure:

Step 4.1: Source the RUN file system environment and start a new patching cycle:

bash

[applmgr@fbsebs ~]$ . EBSapps.env run

Expected output:

text

E-Business Suite Environment Information
----------------------------------------
RUN File System           : /u01/app/FBS/fs1/EBSapps/appl
PATCH File System         : /u01/app/FBS/fs2/EBSapps/appl
Non-Editioned File System : /u01/app/FBS/fs_ne
DB Host: fbstest.finsys.co.ke Service/SID: FBS
Sourcing the RUN File System ...

bash

[applmgr@fbsebs ~]$ adop phase=prepare

Step 4.2: Source the PATCH environment:

bash

[applmgr@fbsebs ~]$ . EBSapps.env patch

Step 4.3: Set the path to OPatch:

bash

[applmgr@fbsebs ~]$ export PATH=$ORACLE_HOME/OPatch:$PATH

Step 4.4: Navigate to the patch directory and unzip the patches:

bash

[applmgr@fbsebs ~]$ cd $PATCH_TOP
[applmgr@fbsebs patch]$ ls -l *.zip
-rw-r--r--. 1 applmgr oinstall 5500038 Feb  4 17:35 p32922089_101232_LINUX.zip
-rw-r--r--. 1 applmgr oinstall 5482278 Feb  4 17:35 p25441839_101232_LINUX.zip
[applmgr@fbsebs patch]$ unzip p25441839_101232_LINUX.zip
[applmgr@fbsebs patch]$ unzip p32922089_101232_LINUX.zip

Step 4.5: Apply the first patch (25441839):

bash

[applmgr@fbsebs patch]$ cd 25441839
[applmgr@fbsebs 25441839]$ opatch apply

Important outputs during patch application:

• The patch will automatically roll back subset patches (8557019, 18620223, 19434967)

• You will be prompted to provide an email address (press Enter to skip)

• You will be prompted to confirm security notifications (enter Y)

• You must confirm the system is ready for updating (enter Y)

• The patch will shut down Oracle instances, apply changes, and restart automatically

Step 4.6: Apply the second patch (32922089):

bash

[applmgr@fbsebs patch]$ cd 32922089
[applmgr@fbsebs 32922089]$ opatch apply

Step 4.7: Apply additional required patches:

bash

[applmgr@fbsebs patch]$ cd 25342269
[applmgr@fbsebs 25342269]$ opatch apply

[applmgr@fbsebs patch]$ cd 27491934
[applmgr@fbsebs 27491934]$ opatch apply

5. Apply Application Technology Patches

The following application technology patches are required:

Patch Description	Patch Number
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
JWS and JRE (8u291 and later) Compatibility Patch	Patch 32902510:R12.FND.C

Procedure:

Step 5.1: Source the RUN file system and navigate to the patch directory:

bash

[applmgr@fbsebs ~]$ . EBSapps.env run
[applmgr@fbsebs ~]$ cd $PATCH_TOP

Step 5.2: Unzip the application technology patches:

bash

[applmgr@fbsebs patch]$ unzip p32902510_R12.FND.C_R12_GENERIC.zip
[applmgr@fbsebs patch]$ unzip p25380324_R12.FND.C_R12_GENERIC.zip
[applmgr@fbsebs patch]$ unzip p25449925_R12.TXK.C_R12_GENERIC.zip
[applmgr@fbsebs patch]$ unzip p24498616_R12.AD.C_R12_GENERIC.zip

Step 5.3: Apply the patches using the adop utility:

bash

[applmgr@fbsebs patch]$ adop phase=apply patches=24498616,25449925,25380324,32902510,28713780,23475123,23280764,23645622,23575933,22221603,23586286,24833534,28700057,29058008,29024389 merge=yes

You will be prompted for:

• APPS password

• SYSTEM password

• WLSADMIN password

Step 5.4: Run adadmin to regenerate JAR files with the force option:

bash

[applmgr@fbsebs ~]$ . EBSapps.env patch
[applmgr@fbsebs ~]$ adadmin

Navigate through the menu:

1. Generate Applications Files

2. Generate product JAR files

3. Regenerate JAR files with FORCE option set to Yes

Step 5.5: Complete the online patching cycle:

bash

[applmgr@fbsebs ~]$ . EBSapps.env run
[applmgr@fbsebs ~]$ adop phase=finalize,cutover mtrestart=no
[applmgr@fbsebs ~]$ adop phase=cleanup

6. Apply Product-Specific Patches

The following product-specific patches may be required depending on your EBS configuration:

Product	Feature	Patch Number
Oracle Workflow	Status Diagram; Notification signing with Digital Signature	Patch 28713780:R12.OWF.C
Oracle Scripting	Script Author	Patch 23475123:R12.IES.C
Oracle Customers Online	Party Relationships	Patch 23280764:R12.IMC.C
Oracle General Ledger	Account Hierarchy Manager	Patch 23645622:R12.GL.C
Oracle Sourcing	Auction Monitor	Patch 23575933:R12.PON.D
Oracle Installed Base	Visualizer Applet	Patch 22221603:R12.CSI.C
Oracle Advanced Supply Chain Planning	Plan Editor (PS/SNO)	Patch 23586286:R12.MSC.C
Oracle Process Manufacturing	Recipe Designer	Patch 24833534:R12.GMD.C

7. Enable Java Web Start

Available Launch Methods

1. Java Plug-in: Runs within the web browser memory space. Browsers need to support NPAPI protocol. Remains the default configuration after applying Java Web Start patches.

2. Java Web Start: Java applets launch as applications running in their own restricted environment (sandbox). Launched from a browser but runs independently once started.

Configuration Parameters

Context File Variable:

Variable	Description	Default Value
s_forms_launch_method	Enable Java Web Start or Java Plug-in. Values: browser (Java Plug-in) or jws (Java Web Start)	browser

Profile Options:

Profile Option/Internal Name	Description	Default Value
Enable Java Web Start / FND_ENABLE_JAVA_WEB_START	Use Java Web Start to launch Forms and Java applets. Values: Yes or No	No
ICX: Forms Launcher / ICX_FORMS_LAUNCHER	Site level default: <s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_webport>/forms/frmservlet Java Plug-in: ...?config=browserMode Java Web Start: ...?config=jws	<s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_webport>/forms/frmservlet

Update Profile Options from Backend

sql

DECLARE
stat boolean;
BEGIN
    dbms_output.disable;
    dbms_output.enable(100000);
    
    stat := FND_PROFILE.SAVE('FND_ENABLE_JAVA_WEB_START', 'YES', 'SITE');
    IF stat THEN
        dbms_output.put_line('Stat = TRUE - profile updated');
    ELSE
        dbms_output.put_line('Stat = FALSE - profile NOT updated');
    END IF;
    
    stat := FND_PROFILE.SAVE('ICX_FORMS_LAUNCHER', 'http://foaerp.training:8000/forms/frmservlet?config=jws', 'SITE');
    IF stat THEN
        dbms_output.put_line('Stat = TRUE - profile updated');
    ELSE
        dbms_output.put_line('Stat = FALSE - profile NOT updated');
    END IF;
    
    COMMIT;
END;
/

Important: The profile options 'Enable Java Web Start' and 'ICX: Forms Launcher' are automatically set by AutoConfig at the site level. They should only be set at the user level when overriding the default configuration.

Configuration Options

Option 1: Set Java Web Start as the default for all application users (selected for this implementation)

Option 2: Set Java Plug-in as the default and Java Web Start for specific users

Option 3: Set Java Web Start as the default and Java Plug-in for specific users

Enable Java Web Start (Option 1)

Step 7.1: Update the context file:

• Locate s_forms_launch_method in the context file

• Change the value from browser to jws

• Save the context file

Step 7.2: Stop all application tier services:

bash

$ sh $ADMIN_SCRIPTS_HOME/adstpall.sh

Step 7.3: Run AutoConfig on the application tier:

bash

cd $ADMIN_SCRIPTS_HOME
[applmgr@fbsebs ~]$ adautocfg.sh

Step 7.4: Start all application tier services:

bash

$ sh $ADMIN_SCRIPTS_HOME/adstrtal.sh

Step 7.5: Validate the profiles updated automatically related to JWS.

Step 7.6: Synchronize the patch file system with the new run file system:

bash

$ adop phase=fs_clone

8. Browser Configuration - JRE Plugin Setup

JRE Version Recommendation

JRE 1.8.0_401 (8u431) CPU is the recommended version for running Java content within Oracle E-Business Suite.

Rename the JRE Plugin File

Rename the downloaded JRE Native Plugin file to j2se<jversion>.exe format. The jversion parameter is the Java family (18, 17, or 16) concatenated with the point release version in a five-digit format.

Example: jre-8u431-windows-i586.exe or jre-8u431-windows-x64.exe → j2se18431.exe

Place the Renamed JRE Plugin

Place the renamed JRE Plugin file on the web application tier in the following directory (run file system):

text

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

Example:

bash

[applmgr@fbsebs ~]$ cd /u01/app/FBS/fs1/EBSapps/comn/webapps/oacore/util/javaplugin
[applmgr@fbsebs javaplugin]$ ls
j2se16027_bak.exe  j2se18421_bak.exe  j2se18461.exe  readme.html

Run the JRE Upgrade Script

Run the txkSetPlugin.sh script against the web node of the application tier:

bash

[applmgr@fbsebs javaplugin]$ txkSetPlugin.sh 18461

This script will:

1. Copy the JRE plugin to the appropriate HTML directory

2. Update the application context file

3. Run AutoConfig

4. Update the appsweb.cfg file

Sample output:

text

Starting interoperability upgrade script...
Sending logfile output to: /u01/app/FBS/fs1/inst/apps/FBS_ebstest/logs/txkSetPlugin.log
Using the context file: /u01/app/FBS/fs1/inst/apps/FBS_ebstest/appl/admin/FBS_ebstest.xml
Using APPLSYS file: /u01/app/FBS/fs1/EBSapps/appl/APPSFBS_ebstest.env
Installing j2se18461 with Version clsid CAFEEFAC-0018-0000-0461-ABCDEFFEDCBA
Updated J2SE plugin to jdk
Updated J2SE mimetype to 1.8.0_461
Updated J2SE Classid to CAFEEFAC-0018-0000-0461-ABCDEFFEDCBA
AutoConfig completed successfully.
Done

9. Client-Side Configuration

Enable Java Console

Enable the Java Console on your desktop client through the Java Control Panel:

text

Control Panel > Java (icon) > Advanced > Java Console > Show Console

Browser Security Settings

Configure your browser to mark JNLP files as safe.

Validate EBS Forms

Test the configuration by launching Oracle Forms from your EBS environment. The application should launch using Java Web Start successfully.

Important Notes

• MacOS Users: Additional patches are required for MacOS environments. Refer to Oracle documentation for specific instructions.

• Multiple Sessions: Only one instance per Java applet can run on the client PC. Multiple instances of a specific applet cannot be launched, even from different sessions or browsers.

• Always Refer to Latest Documentation: Oracle continuously releases new patches and updates. Always check the latest Oracle documents for the most current patch numbers and implementation procedures.

References

1. Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12 (Doc ID 393931.1)

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

---

This completes the lab exercise for Java Web Start implementation in Oracle E-Business Suite Release 12.2.