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

28/7/22, 14:43 Document 2188898.
1
Copyright (c) 2022, Oracle. All rights reserved. Oracle Confidential.
Using Java Web Start with Oracle E-Business Suite (Doc ID 2188898.1)
This knowledge document describes how to use Java Web Start with Oracle E-Business Suite (EBS) Releases 12.2 and 12.1.
The most current version of this document can be obtained in My Oracle Support Knowledge Document 2188898.1.
There is a change log at the end of this document.
Note: To receive automatic notifications of updates, subscribe to the Hot Topics Notification feature in My Oracle Support,
as described in Document 793436.2, Subscribing to Hot Topic E-Mails.
In This Document
This document is divided into the following sections:
Section 1: About Java Web Start

Section 2: Impact of Java Web Start on Oracle E-Business Suite
Section 3: Recommended Browsers
Section 4: Applying Required Patches
Section 5: Enabling Java Web Start
Section 6: Browser User Experience and Configuration
Section 7: Known Issues
Section 8: References
Section 1: About Java Web Start

1.1 What is Java Web Start?
1.2 Architectural Comparison
of Java Plug-in and Java Web Start
1.3 Why is Oracle E-Business Suite Implementing Java Web Start?
1.1 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 in 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.
Java Web Start software is installed as part of the Java Runtime Environment (JRE) software. Users do not have to install Java
Web Start software separately or perform additional tasks to use Java Web Start applications.
1.2 Architectural Comparison of Java Plug-in and Java Web Start
The following architectural diagrams illustrate the differences between the Java Plug-in and Java Web Start on the client
(desktop) tier:
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=8b7ihnx2f_4&id=2188898.1 1/31
28/7/22, 14:43 Document 2188898.1
Figure 1: Java Plug-in architecture Figure 2: Java Web Start architecture
1.3 Why is Oracle E-Business Suite Implementing Java Web Start?
The Oracle E-Business Suite migration to Java Web Start is primarily driven by modern web browsers ending support for the
Netscape Plug-in Application Programming Interface (NPAPI), which is used by the Java Plug-in. At the same time, Oracle
plans to deprecate the Java Plug-in for web browsers starting with the release of Java SE 9. Java Web Start applications can be
launched independently of a browser since they do not rely on a browser plug-in, it provides a migration path from Java
applets.
Section 2: Impact of Java Web Start on Oracle E-Business Suite

2.1 How Does Java Web Start Impact the Oracle E-Business Suite Architecture?
2.2 Are There Any Changes in the User Experience When Migrating to Java Web
Start?
2.3 Performance Comparison Between Java Web Start and Java Plug-in
2.1 How Does Java Web Start Impact the Oracle E-Business Suite Architecture?
Java Web Start is included in the Java Runtime Environment (JRE). The following table lists the minimum JRE release required
on the client tier to use Java Web Start with Oracle E-Business Suite.
Oracle E-Business
Minimum JRE Release
Suite Release
12.2
JRE 8 Update 301 or later (for macOS Big Sur
and earlier clients) 1
JRE 8 Update 181 or later (for multiple Forms
session support) 2
JRE 8 Update 171 or later (for macOS
Catalina and earlier clients) 3
JRE 8 Update 144 b01 Patch 26512977 or
later 4
JRE 8 Update 141 b15 Patch 25951321 5
JRE 8 Update 131 b31 Patch 25767257
12.1.3
JRE 8 Update 301 or later (for macOS Big Sur
or earlier) 1
JRE 8 Update 181 or later (for multiple Forms
session support) 2
JRE 8 Update 171 or later (for macOS
Catalina and earlier clients) 3
28/7/22, 14:43 Document 2188898.1
JRE 8 Update 144 b01 Patch 26512977 or

later 4
JRE 8 Update 141 b15 Patch 25951321 5
1 JRE 8 Update 301 is the minimum requirement for macOS clients accessing EBS environments with the patches listed
in 4.7 Required Patches for Supporting Firefox ESR on macOS (Big Sur and Earlier) Using Java Web Start applied.
2 JRE 8 Update 181 is the minimum requirement for multiple Forms session support using Java Web Start. For further
information, see 4.5 Required Patches for Multiple Forms Session Support Using Java Web Start and 6.8 Using Multiple
Forms Sessions with Java Web Start.
3 JRE 8 Update 171 is the minimum requirement for macOS clients accessing EBS environments with only the patches
listed in 4.6 Required Patches for Supporting Firefox ESR on macOS (Catalina and Earlier) Using Java Web Start applied.
4JRE 8 Update 144 b01 includes the fix for a regression issue introduced in JDK 8u141, which under specific conditions
may cause Java Web Start applications to fail to launch. For further information, see the Java 8u144 Release Notes.
5JRE 8 Update 141 b15 is the standard public July 2017 CPU release which is also available for download through the
Oracle Technology Network (OTN) and Java.com public sites.
The above table lists the minimum JRE release to run the Forms application in EBS using Java Web Start. Oracle strongly
recommends that you use the latest JRE 8 Update certified with EBS on the client tier, and stay current with future Java Critical
Patch Updates (CPUs). See My Oracle Support Knowledge Document 2484000.1, Oracle E-Business Suite Release 12.2.3
Readme, Section 1: Identifying Latest CPU For Oracle E-Business Suite for further information.
The same web browsers used in the current architecture will continue to be supported (Microsoft Internet Explorer, Mozilla
Firefox ESR, and Apple Safari). Browsers which formerly did not support the Java Plug-in and only supported HTML/OA
Framework modules (such as Google Chrome and Microsoft Edge) will be able to launch Forms and Java applets in Oracle E-
Business Suite using Java Web Start.
2.2 Are There Any Changes in the User Experience When Migrating to Java Web Start?
In general, Java Web Start provides a similar user experience as the Java Plug-in.
With Java Web Start, Java applications are still launched from the browser, but now all Java applets in Oracle E-Business Suite
will run outside of the web browser. The following screenshot illustrates the new behavior of the Workflow Status Diagram
Java applet. It opens in a new and separate Java window, instead of displaying the Java applet directly within the web browser
using the Java Plug-in.
Only one instance per Java applet can be running on the client PC. Multiple instances of a specific Java applet cannot be
launched, even when launched from different sessions or browsers. The following message will be displayed when opening a
second Java applet instance:
28/7/22, 14:43 Document 2188898.1
2.3 Performance Comparison Between Java Web Start and Java Plug-in
Stress tests have been conducted on Oracle E-Business Release 12.2 and 12.1.3 to compare both the new Java Web Start and
current Java Plug-in launch method for the Forms application. The results of both tests were comparable on all key
performance indicators:
Client (desktop) tier: The time taken to open the Forms application in Oracle E-Business Suite with Java Web Start is
comparable to that seen with the Java Plug-in. There is no significant variation observed in CPU utilization and memory
consumption.
Application tier: There is no significant variation observed in CPU utilization and memory consumption for the oacore
and forms services.
Database tier: A slight increase in the number of database connections is seen with Java Web Start on Oracle E-
Business Suite Release 12.1.3. This is due to architectural changes where the Forms server also creates its own JDBC
connection pool. There was no such difference observed with Java Web Start on Oracle E-Business Suite Release 12.2.
The CPU utilization and memory consumption remained the same on this tier.
Section 3: Recommended Browsers

For a complete overview of recommended browsers that can use Java Web Start with Oracle E-Business Suite, see My Oracle
Support Knowledge Document 389422.1, Recommended Browsers for Oracle E-Business Suite Release 12.
For macOS platform, Firefox ESR is supported using Java Web Start. It is required to apply the latest patches as listed in
Section 4: Applying Required Patches to use Firefox ESR on macOS for launching the Forms application and other Java applets
using Java Web Start.
Section 4: Applying Required Patches

Before you install and configure Java Web Start in Oracle E-Business Suite, you must apply the required technology and
product-specific patches.
4.1 Minimum Java Runtime Environment for Java Web Start

4.2 Required Patches for Oracle E-Business Suite Release 12.2

4.4 Patch Application Instructions
4.5 Required Patches for Multiple Forms Session Support Using Java Web Start

Using Java Web Start
4.6 Required Patches for Supporting Firefox ESR on macOS (Catalina and Earlier)
4.7 Required Patches for Supporting Firefox ESR on macOS (Big Sur and Earlier) Using Java Web Start
4.8 Required Patches for Compatibility with JRE 8 Update 291 and Later
4.1 Minimum Java Runtime Environment for Java Web Start
Using Java Web Start with Oracle E-Business Suite previously required enhancements to Java Runtime Environment (JRE).
These were included in commercial JRE Bundled Patch Releases (BPR) namely, JRE 8 Update 131-b31 and JRE 8 Update 121-
b33.
These enhancements are now included in the public release of the July 2017 CPU, JRE 8 Update 141-b15. JWS users are
recommended to upgrade to this latest and therefore most secure version of JRE which can be obtained from the following
locations:
Download through the

Oracle Technology Network (OTN) or
Java.com public sites.
28/7/22, 14:43 Document 2188898.1
Alternatively, it is also available from My Oracle Support by downloading Patch 25951321 - Oracle JRE 8 Update 141.
Certain Java Web Start related features such as multiple Forms sessions require a more recent JRE on the client. For further
information, see 2.1 How Does Java Web Start Impact the Oracle E-Business Suite Architecture?
For further information on Java releases, see:
Java Development Kit 8 Update Release Notes

Critical Patch Updates, Security Alerts and Third Party Bulletin
Document 1682574.1, Java SE Update Releases and Schedules: Critical Patch Updates, Minor Updates, Early Access,
Public, and Commercial
Document 1439822.1, All Java SE Downloads on MOS
This section provides an overview of all patches required to install and configure Java Web Start on Oracle E-Business Suite
Release 12.2:
Instructions for applying these patches follow in 4.4.1 Applying Patches to Oracle E-Business Suite Release 12.2.
4.2.1 Minimum Prerequisites

4.2.2
Oracle Forms 10g Technology Patch for Oracle E-Business Suite Release 12.2
4.2.3 Application Technology Patches for Oracle E-Business Suite Release 12.2
4.2.4 Product-Specific Patches for Oracle E-Business Suite Release 12.2
The following lists the minimum codelevels 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
For further information, see the following My Oracle Support Knowledge documents:
Document 1586214.1, Oracle E-Business Suite Release 12.2.3 Readme

Document 1617461.1, Applying the Latest AD and TXK Release Update
Document 2159750.1, Oracle E-Business Suite Applications DBA and Technology Stack Release Notes for
R12.AD.C.Delta.8 and R12.TXK.C.Delta.8
Document 2113163.1, Applying the R12.ATG_PF.C.Delta.6 Release Update Pack
4.2.2 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 is the minimum required
Oracle Forms 10g overlay patch that adds support for Java Web Start to Oracle Forms as part of the Oracle E-Business Suite
technology stack.
It is a cumulative Forms overlay patch on top of Oracle Forms 10.1.2.3.2. As these patches are cumulative, future Forms
overlay patches will directly include Patch 25441839. For the most recent Forms overlay patch, see "Section 4.1: Forms and
Reports 10.1.2.3 Patches and Bug Numbers" in Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List
of Patches and Technology Bug Fixes.
For further information, see My Oracle Support Knowledge Document 805965.1, Applying OracleAS 10g Forms and Reports
Patches to Oracle E-Business Suite Release 12.
The following table lists all required application technology patches.
Application Technology Patch Description Patch Number
28/7/22, 14:43 Document 2188898.1
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
The following product-specific patches are required for the following Oracle E-Business Suite Release 12.2 products which use
Java applets:
Product Feature Patch Number
Oracle Workflow Status Diagram; Notification signing with Digital Patch

Signature 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 Plan Editor (PS/SNO) Patch

Planning 23586286:R12.MSC.C
Oracle Process Manufacturing Recipe Designer Patch

24833534:R12.GMD.C
This section provides an overview of all patches required to install and configure Java Web Start on Oracle E-Business Suite
Release 12.1.

4.3.2
Oracle Forms 10g Technology Patch for Oracle E-Business Suite Release 12.1
The following lists the minimum codelevels 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
For further information, see the following My Oracle Support Knowledge documents:
Document 1080973.1, Oracle E-Business Suite Release 12.1.3 Readme

Document 1640482.1, Oracle E-Business Suite Applications DBA Readme, Release 12.1.3+ (R12.AD.B.Delta.4, Patch
17884289)
Document 1066312.1, R12.1.3 : Oracle E-Business Suite Applications Technology Readme for Release 12.1.3
(R12.ATG_PF.B.delta.3, Patch 8919491)
28/7/22, 14:43 Document 2188898.1
4.3.2 Oracle Forms 10g Technology Patch for Oracle E-Business Suite Release 12.1
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 support for Java Web Start to Oracle Forms as part of the Oracle E-Business Suite
technology stack.
It is a cumulative Forms overlay patch on top of Oracle Forms 10.1.2.3.2. As these patches are cumulative, future Forms
overlay patches will directly include Patch 25441839. For the most recent Forms overlay patch, see "Step 2.1.2: Download
Additional Patches Required" in Document 437878.1, Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite
Release 12.
For further information, see My Oracle Support Knowledge Document 805965.1, Applying OracleAS 10g Forms and Reports
Patches to Oracle E-Business Suite Release 12.
The following table lists all required application technology patches.
AD: Add Java Web Start support to Oracle E-Business Suite Patch 24498616:R12.AD.B
TXK: Add Java Web Start support to Oracle E-Business Suite Patch 24319156:R12.TXK.B
Oracle E-Business Suite Java Applets launching with Java Web Start Patch 25380324:R12.FND.B
The following product-specific patches are required for the following Oracle E-Business Suite Release 12.1 products which use
Java applets:
Product Feature Patch Number
Oracle Workflow Status Diagram; Notification signing with Digital Patch

Signature 28713780:R12.OWF.B
Oracle Scripting Script Author Patch 23475123:R12.IES.B
Oracle Customers Online Party Relationships Patch

23280764:R12.IMC.B
Oracle General Ledger Account Hierarchy Manager Patch 25140916:R12.GL.B
Oracle Sourcing Auction Monitor Patch

23575933:R12.PON.B
Oracle Installed Base Visualizer Applet Patch 25075128:R12.CSI.B
Oracle Advanced Supply Chain Plan Editor (PS/SNO) Patch

Planning 25106959:R12.MSC.B
Oracle Process Manufacturing Recipe Designer Patch

24833534:R12.GMD.B
4.4 Patch Application Instructions
This section describes the required steps for applying Java Web Start-related patches to Oracle E-Business Suite Release 12.2
or 12.1.
Java Web Start is not enabled by default after applying the patches, therefore after completing these steps, proceed with
Section 5: Configuring and Enabling Java Web Start.
28/7/22, 14:43 Document 2188898.1
4.4.1 Applying Patches to Oracle E-Business Suite Release 12.2

Follow the instructions below to apply the required Oracle Forms 10g and application technology patches to Oracle E-Business
Suite Release 12.2 in preparation for Java Web Start.
1. Source the APPS environment.
$ source <EBS_ROOT>/EBSapps.env run
2. Start a new online patch cycle.
$ adop phase=prepare
3. Apply the Oracle Forms 10g technology patch.
$ source <EBS_ROOT>/EBSapps.env patch
Use OPatch to apply the latest Oracle Forms 10g technology overlay patch against the OracleAS 10.1.2 ORACLE_HOME
as explained in 4.2.2 Oracle Forms 10g Technology Patch for Oracle E-Business Suite Release 12.2.

4. Apply the required Oracle E-Business Suite application technology patches (AD/TXK/FND) as previously listed in 4.2.3
Application Technology Patches for Oracle E-Business Suite Release 12.2.
$ adop phase=apply patches=24498616,25449925,25380324 merge=yes
5. Apply product-specific patches as needed, as previously listed in 4.2.4 Product-Specific Patches for Oracle E-Business
Suite Release 12.2 using adop for those products that are in use. These product-specific patches add support for Java
Web Start for non-Forms Java applets in Oracle E-Business Suite.

6. Use the AD Administration tool (adadmin) to regenerate JAR files with force option.
$ source <EBS_ROOT>/EBSapps.env patch

$ adadmin
Navigation: Generate Applications Files Generate product JAR files

Regenerate JAR files with FORCE option set to Yes
Do you wish to force regeneration of all jar files? [No] ? Yes
7. Complete the online patch cycle.
$ adop phase=finalize,cutover

run
$ source <EBS_ROOT>/EBSapps.env
8. Perform a cleanup of the online patch cycle.
$ adop phase=cleanup
9. Synchronize the patch file system with the new run file system.
$ adop phase=fs_clone
This step ensures that the Oracle Forms 10g overlay Patch 25441839 is propagated to the new patch file system.

Follow the instructions below to apply the required Oracle Forms 10g and application technology patches to Oracle E-Business
Suite Release 12.1 in preparation for Java Web Start.
28/7/22, 14:43 Document 2188898.1
1. Source the environment file.
$ source <APPL_TOP>/APPS<CONTEXT_NAME>.env
2. Stop all application tier services.
$ <INST_TOP>/admin/scripts/adstpall.sh <apps user>/<apps password>
3. Apply the Oracle Forms 10g technology patch.

Use OPatch to apply the latest Oracle Forms 10g technology overlay patch against the OracleAS 10.1.2 ORACLE_HOME.
See 4.3.2 Oracle Forms 10g Technology Patch for Oracle E-Business Suite Release 12.1 for the recommended patch.

4. Source environment file.
$ source <APPL_TOP>/APPS<CONTEXT_NAME>.env
5. Apply the required Oracle E-Business Suite application technology patches (AD/TXK/FND) as listed in 4.3.3 Application
Technology Patches for Oracle E-Business Suite Release 12.1 using adpatch.
6. (Conditional) Apply product-specific patches as needed, as previously listed in
4.3.4 Product-Specific Patches for Oracle
E-Business Suite Release 12.1 using adpatch for those products that are in use. These product-specific patches add
support for Java Web Start for non-Forms Java applets in Oracle E-Business Suite.

the AD Administration tool (adadmin) to regenerate JAR files with force option.
7. Use
$ adadmin

Navigation: Generate Applications Files Generate product JAR files

Regenerate JAR files with FORCE option set to Yes
Do you wish to force regeneration of all jar files? [No] ? Yes
8. Start all application tier services.
$ <INST_TOP>/admin/scripts/adstrall.sh <apps user>/<apps password>
The installation of the patches does not enable Java Web Start. The Java Plug-in remains the default launch method for all
application users. Proceed with the instructions described in Section 5: Configuring and Enabling Java Web Start after having
applied the required patches.
4.5 Required Patches for Multiple Forms Session Support Using Java Web Start
Multiple Forms sessions are supported using Java Web Start on Windows and macOS. This section provides a summary of the
required patches and patch application instructions. For further information about multiple Forms session support, see 6.8
Using Multiple Forms Sessions with Java Web Start.
All required patches listed in 4.2 Required Patches for Oracle E-Business Suite Release 12.2 or 4.3 Required Patches for Oracle
E-Business Suite Release 12.1 must be applied before proceeding with the installation of the following patches.
The following table lists the required application technology patches for Oracle E-Business Suite Release 12.2:
JWS: Add System Property To forms_jnlp_tmp for Firefox on Patch 28700057:R12.TXK.C

macOS
Oracle E-Business Suite Java Applets Launching with Java Patch 29058008:R12.FND.C
Web Start Release 2
JWS: New Preference To Indicate Launch of New Forms

Session On top of R12.ATG_PF.C.Delta.7 or later: Patch
29024389:R12.FWK.C
28/7/22, 14:43 Document 2188898.1
On top of R12.ATG_PF.C.Delta.6: Patch

28706297:R12.FWK.C
TXK: Consolidated Patch for Java Web Start Release 2 Patch 29124450:R12.TXK.B
Oracle E-Business Suite Java Applets Launching with Java Web Start Release 2 Patch 29058008:R12.FND.B
JWS: New Preference To Indicate Launch of New Forms Session Patch 29052441:R12.FWK.B
These patches add multiple Forms session support using Java Web Start to Oracle E-Business Suite. See 4.4 Patch Application
Instructions for detailed steps on how to apply patches to Oracle E-Business Suite.
4.6 Required Patches for Supporting Firefox ESR on macOS (Catalina and Earlier) Using Java Web Start
Note: This section describes the minimum required patches to run Java content using Java Web Start with Firefox ESR on
macOS Catalina and earlier. It is recommended to apply the patches listed in 4.7 Required Patches for Supporting
Firefox ESR on macOS (Big Sur and Earlier) Using Java Web Start. Those patches add support for running Java content in
Oracle E-Business Suite Releases 12.2 and 12.1 using Java Web Start with Firefox ESR on all supported macOS releases
(Big Sur, Catalina, ...).
Firefox ESR on macOS is supported with Oracle E-Business Suite using Java Web Start. This section provides a summary of the
required patches and patch application instructions.
Before proceeding with the installation of the following patches, you must apply all required patches listed in 4.2 Required
Patches for Oracle E-Business Suite Release 12.2 or 4.3 Required Patches for Oracle E-Business Suite Release 12.1.
JWS: Add System Property To forms_jnlp_tmp for Firefox on macOS Patch

28700057:R12.TXK.C
Oracle E-Business Suite Java Applets launching with Java Web Start plus macOS Support using Patch
Firefox 28156520:R12.FND.C

28700057:R12.TXK.B
Oracle E-Business Suite Java Applets launching with Java Web Start plus macOS Support using Patch
Firefox 28156520:R12.FND.B
These additional patches add support for Firefox ESR on macOS using Java Web Start. See 4.4 Patch Application Instructions
for detailed steps on how to apply patches to Oracle E-Business Suite.
4.7 Required Patches for Supporting Firefox ESR on macOS (Big Sur and Earlier) Using Java Web Start
4.7.1 Overview
4.7.2 Required
Patches for Oracle E-Business Suite Release 12.2
4.7.3 Required Patches for Oracle E-Business Suite Release 12.1
28/7/22, 14:43 Document 2188898.1
4.7.1 Overview
Firefox ESR on macOS is supported with Oracle E-Business Suite Releases 12.2 and 12.1 using Java Web Start. This section
lists the required patches for running the Forms application and other Java applets with Firefox ESR on all supported macOS
releases (Big Sur, Catalina, Mojave and High Sierra). For further information, see My Oracle Support Knowledge Document
1533334.1, Oracle E-Business Suite Release Notes for Apple macOS Clients, Release 12 and Document 389422.1,
Recommended Browsers for Oracle E-Business Suite.
Note: The following patches include the compatibility bugfix to use JRE 8 Update 291 and later with Oracle E-Business
Suite as described in 4.8 Required Patches for Compatibility with JRE 8 Update 291 and Later.
All required patches listed in 4.2 Required Patches for Oracle E-Business Suite Release 12.2 must be applied before proceeding
with the installation of the following patches.
Apply Oracle Forms 10g Technology Patch

Platform Patch Number
Oracle Solaris on SPARC, IBM AIX on Power Systems, Linux x86-64 1, HP-UX Itanium Patch 32922089
Microsoft Windows x64 2 Patch 32960401
1 If you are a Linux x86-64 customer, you must download the Linux x86 patch.
2 If you are a Microsoft Windows x64 customer, you must download the Microsoft Windows (32-bit) patch.
For further information, see My Oracle Support Knowledge Document 805965.1, Applying OracleAS 10g Forms and
Reports Patches to Oracle E-Business Suite Release 12.

28700057:R12.TXK.C
Oracle E-Business Suite Java Applets launching with JWS for macOS Big Sur (and later) Patch
using Firefox ESR 32645734:R12.FND.C

Patch
Platform
Number
Oracle Solaris on SPARC, IBM AIX on Power Systems, Linux x86-64 1, HP-UX Itanium, HP-UX PA- Patch 32922089
RISC
28/7/22, 14:43 Document 2188898.1

28700057:R12.TXK.B
Oracle E-Business Suite Java Applets launching with JWS for macOS Big Sur (and later) Patch
using Firefox ESR 32645734:R12.FND.B
4.8 Required Patches for Compatibility with JRE 8 Update 291 and Later
4.8.1 Overview
4.8.2 Required
Patches for Oracle E-Business Suite Release 12.2
4.8.1 Overview
This section provides a summary of the required compatibility patches to use JRE 8 Update 291 and later with Oracle E-
Business Suite when using Java Web Start to run Java content on the client. These patches resolve the known issue described
as 7.20 Unable to Open URLs From the Forms Application or Java Applets When Using JRE 8 Update 291 or Later.

Platform Patch Number
Oracle Solaris on SPARC, IBM AIX on Power Systems, Linux x86-64 1, HP-UX Itanium Patch 32922089
Apply Applications Technology Patch 32902510:R12.FND.C JWS and JRE (8u291 and later) Compatibility Patch.

Patch
Platform
Number
Oracle Solaris on SPARC, IBM AIX on Power Systems, Linux x86-64 1, HP-UX Itanium, HP-UX PA- Patch 32922089
RISC
28/7/22, 14:43 Document 2188898.1
Apply Applications Technology Patch 32902510:R12.FND.B JWS and JRE (8u291 and later) Compatibility Patch.
Section 5: Configuring and Enabling Java Web Start

5.1 Overview

5.2 Enabling Java Web Start
5.1 Overview
The technology and product-specific patches referenced in the previous section add a new method for launching the Forms
application and non-Forms Java applets in Oracle E-Business Suite.
The following two launch methods are available:
Java Plug-in: The Java Plug-in runs within the web browser memory space. Browsers need to support the NPAPI
protocol to run Java applets using the Java Plug-in. It remains the default configuration after applying the Java Web
Start patches.
Java Web Start: Java applets launch as Java Web Start applications and these run in their own restricted environment,
known as a sandbox. It is launched from a web browser, but once it runs, it does not have any dependency on the web
browser.
The preferred launch method is configured by a combination of a new context file variable and two profile options.
Context File Variable
Variable Description Default Value
Enable Java Web Start or Java Plug-in.
Possible values:
s_forms_launch_method browser

browser - use Java Plug-in

jws - use Java Web Start
Profile Options
Profile Option / Internal

Description Default Value
Code
Enable Java Web Start / No

FND_ENABLE_JAVA_WEB_START Use Java Web Start to launch the Forms application and
Java applets.
Possible values:

Yes - Use Java Web Start
28/7/22, 14:43 Document 2188898.1
No - Use Java Plug-in
<s_webentryurlprotocol>://
The URL for launching the Forms application. <s_webentrydomain>:
<s_active_webport>/forms/f
Possible values:

Site level default:

<s_webentryurlprotocol>://<s_webentryhost>.
<s_webentrydomain>:
<s_active_webport>/forms/frmservlet
ICX: Forms Launcher / Java Plug-in:
ICX_FORMS_LAUNCHER <s_webentryurlprotocol>://<s_webentryhost>.
<s_webentrydomain>:
<s_active_webport>/forms/frmservlet?
config=browserMode
Java Web Start:
<s_webentryurlprotocol>://<s_webentryhost>.
<s_webentrydomain>:
<s_active_webport>/forms/frmservlet?
config=jws
The profile options 'Enable Java Web Start' and 'ICX: Forms Launcher' are automatically set by AutoConfig at the site level and
should only be set at the user level when it is required to override the default configuration.
5.2 Enabling Java Web Start
The previously described environment settings provide full control of how the Forms application and regular Java applets in
Oracle E-Business Suite are launched. The environment can use either Java Web Start or the Java Plug-in for the whole
environment, or a combination of both when configured accordingly at the user level.
The following configuration options are available:
Option 1: Set Java Web Start as the default for all application users
Option 2: Set Java Plug-in as the default and Java Web Start for specific application users
Option 3: Set Java Web Start as the default and Java Plug-in for specific application users
Option 1: Set Java Web Start as the default for all application users
Follow these instructions to enable Java Web Start in Oracle E-Business Suite:
1. Update the context file using Oracle Application Manager.

a. Using the System Administration responsibility, run
AutoConfig through the Oracle Applications Manager
interface.
b. Click the Edit Parameters icon for the application tier context file.
c. Click the System tab.
d. Expand the oa_system_config node.
e. Change the value of OA_VAR for s_forms_launch_method from browser to jws.
f. Click Save at the bottom of the page.
2. Stop all application tier services.

$ sh <ADMIN_SCRIPTS_HOME>/adstpall.sh
3. Run AutoConfig on the application tier.

$ sh <ADMIN_SCRIPTS_HOME>/adautocfg.sh
4. Start all application tier services.

28/7/22, 14:43 Document 2188898.1
$ sh <ADMIN_SCRIPTS_HOME>/adstrtal.sh
Completing these steps sets Java Web Start as the default launch method for the environment. In step 3, AutoConfig updates
the two profile options at the site level accordingly:
Profile Option / Internal Code Value at the Site Level
Enable Java Web Start / Yes

FND_ENABLE_JAVA_WEB_START
ICX: Forms Launcher / <s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:

ICX_FORMS_LAUNCHER <s_active_webport>/forms/frmservlet
Note: Do not modify these profile option values at the site level as those changes will always be updated by AutoConfig.
The configuration steps described above can also be performed to revert back to the Java Plug-in as the default for all
application users. In that case, specify browser for s_forms_launch_method in step 1.
It remains possible to use the Java Plug-in for some application users. See Option 3: Java Web Start as the default launch
method for all applications and Java Plug-in for specific users for the configuration steps.
Option 2: Set Java Plug-in as the default and Java Web Start for specific application users
This option enables Java Web Start only for a specific set of application users. This applies to an environment that has the Java
Plug-in set as the default launch method for all application users, as per the following environment configuration:
Context variable s_forms_launch_method is set to browser meaning that by default all application users use the Java
Plug-in.
Profile option values at the site level as a result of s_forms_launch_method being set to browser:
Enable Java Web Start is set to No
ICX: Forms Launcher set to <s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:
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
Note: The 'ICX: Forms Launcher' profile option gets ?config=jws appended at the user level as application users require
a launch method that is different from the site level configuration.
Option 3: Set Java Web Start as the default and Java Plug-in for specific application users
This option enables Java Plug-in only for a specific set of application users. This applies to an environment that has Java Web
Start set a default launch method for all application users, as per the following environment configuration:
Context variable s_forms_launch_method is set to jws, meaning that by default all application users use Java Web
Start.
Profile option values at the site level as a result of s_forms_launch_method being set to jws:
'Enable Java Web Start' is set to Yes
'ICX: Forms Launcher' set to <s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:
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
28/7/22, 14:43 Document 2188898.1
'ICX: Forms Launcher' set to <s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:

<s_active_webport>/forms/frmservlet?config=browserMode
Note: The 'ICX: Forms Launcher' profile option gets ?config=browserMode appended at the user level as application
users require a launch method that is different from the site level configuration.
Section 6: Browser User Experience and Configuration

This section describes differences in user experience, comparing the new Java Web Start with the Java Plug-in launch method.
If available, additional configuration steps to improve the user experience for specific web browsers are also described.
6.1 All Web Browsers

6.2 Microsoft Internet
Explorer

6.3 Mozilla Firefox Extended Support Release (ESR)

6.4 Google Chrome
6.5 Microsoft Edge
6.6 Microsoft Edge

(Chromium)
6.7 Apple Safari

Forms Sessions with Java Web Start
6.8 Using Multiple
6.1 All Web Browsers
A few product-specific Java applets run directly within the web browser when using the Java Plug-in. The functional flows
involving those Java applets have been improved to support Java Web Start. As a result, these Java applets appear as a
separate Java window instead of being displayed directly within the web browser when running them with Java Web Start.
6.2 Microsoft Internet Explorer
Internet Explorer supports both Java Web Start and the Java Plug-in for launching the Forms application and regular Java
applets as part of Oracle E-Business Suite.
Default behavior
Launching Java content with Java Web Start should provide a comparable user experience to that seen with the Java Plug-in.
The frmservlet.jnlp is downloaded to the web browser's cache directory and automatically removed from that location by
the Java Web Start Launcher.
There are no specific browser configuration steps required.
6.3 Mozilla Firefox Extended Support Release (ESR)
Firefox ESR 68.x and Firefox ESR 78.1 and later supports Java Web Start for running the Forms application and regular Java
applets as part of Oracle E-Business Suite. Firefox ESR is supported on both Windows and macOS platforms.
6.3.1 Firefox ESR for Windows Users

6.3.2 Firefox ESR for macOS Users
6.3.1 Firefox ESR for Windows Users
Default behavior
By default, Firefox ESR requires the user to choose the appropriate action on what to do with the JNLP file that is downloaded
when launching, for example, the Forms application using Java Web Start.
1. Open Firefox.
2. Log in to Oracle E-Business Suite.
3. Choose a responsibility (for example, System Administrator).
28/7/22, 14:43 Document 2188898.1
4. Click on an Oracle Forms-based menu item (such as Security → User → Define) to initiate the download of the
frmservlet.jnlp file.
5. Firefox displays the following message: "What should Firefox do with this file?", as shown in the following image:
6. Choose the first option "Open with" and in the corresponding drop-down list, select 'Java(TM) Web Start Launcher
(default)."
7. Select the check box "Do this automatically for files like this from now on" in order to associate the JNLP file extension
with the Java Web Start Launcher executable on the client PC.
8. Click OK.
You only need to do this once: future instances of the Forms application or a Java applet will then always launch using Java
Web Start, providing a comparable user experience to that seen with the Java Plug-in.
Each new frmservlet.jnlp (Windows) or frmservlet-n (macOS) file is saved into the default download location as defined
in Firefox. The Java Web Start Launcher will automatically remove this file from that location.
Note (Windows only): If you had inadvertently chosen "Save As" and saved the JNLP file to the desktop, you will need to
manually launch it from the desktop.
Manually configuring JNLP file association (Windows only)
The JNLP file association can also be manually configured by complete the following steps in Firefox:
1. Click Menu.
2. Click the Options icon.
3. Select the Applications tab.
4. Search for Content type "JNLP File."
5. In the Action drop-down list, select "Use Java(TM) Web Start Launcher (default)."
6.3.2 Firefox ESR for macOS Users
This section describes the behavior of Firefox ESR 78.x and earlier on macOS when launching an Oracle Forms application or
Java applet in an EBS environment that has the patches listed in 4.7 Required Patches for Supporting Firefox ESR on macOS
(Big Sur and Earlier) Using Java Web Start applied.
Oracle E-Business Suite uses the Java Web Start protocol handler on macOS clients to launch an Oracle Forms application or
Java applet. The Java Web Start protocol handler handles the custom URI schemes jnlp: and jnlps:. It runs the Java Web
Start launcher which downloads the frmservlet.jnlp, and then starts the Java Web Start application, for example, the Forms
application.
Note: If your Oracle E-Business Suite environment only has the patches listed in 4.6 Required Patches for Supporting
Firefox ESR on macOS (Catalina and Earlier) Using Java Web Start applied, then Firefox ESR behaves in the same way on
28/7/22, 14:43 Document 2188898.1
macOS and Windows. For further information about the default browser behavior of Firefox ESR, see "Default Behavior" in
6.3.1 Firefox ESR for Windows Users.
Default behavior
By default, Firefox ESR 78.x and earlier on macOS requires the user to choose the appropriate action on what to do when the
user launches the Forms application using Java Web Start.
1. Open Firefox.
4. Click on an Oracle Forms-based menu item (such as Security → User → Define).
5. A new browser tab opens, showing a page with the message "Launching Oracle forms-based application."
6. Firefox displays a Launch Application dialog window, as shown in the following image:

7. Choose "JavawsLauncher" from the Launch Application dialog window.

8. Select the check box "Remember my choice for jnlps links." to associate the JNLP protocol scheme with the Java Web
Start Launcher executable on the client.
9. Click Open link.
You only need to do this once: future instances of the Forms application or a Java applet will then always launch using Java
Web Start, providing a comparable user experience to that seen with the Java Plug-in.
The new browser tab in step 5 will close automatically after a short period, or you can close the tab manually at any time.
6.4 Google Chrome
Google Chrome has not supported the Java Plug-in since release 45. Therefore, the Forms application and regular Java applets
as part of the Oracle E-Business Suite can only run with Java Web Start.
Recommended browser configuration using Chrome policies (Windows only)
Google Chrome version 84 and later supports automatic opening of the Forms application and regular Java applets as part of
Oracle E-Business Suite offering the best user experience for the end users. This requires the configuration of two Chrome
policies.
Chrome policy Description Required value
AutoOpenFileTypes 1 List of file types that should be automatically opened on download. jnlp
28/7/22, 14:43 Document 2188898.1
AutoOpenAllowedForURLs URLs where AutoOpenFileTypes can apply. .ebs.example.com 2
1 Chrome policy AutoOpenFileTypes requires Windows clients to be joined to a Microsoft Active Directory domain,
running on Windows 10 Pro, or enrolled in Chrome Browser Cloud Management.
2It is recommended to match the exact hostname of the Oracle E-Business Suite web entry point. This is done by
adding a leading period. For example a value of .exacthost.example.com will match only the hostname
exacthost.example.com.
Chrome policies are centrally managed by system administrators as Group Policy Object (GPO) using Microsoft Active Directory
or Microsoft Intune. Deployment instructions supported by administrative templates (.admx) for Google Chrome are described
on the following Google Chrome Enterprise Help pages:
Chrome Browser on Windows (managed on premise), Chrome Browser Deployment Guide (Windows), section Policies
and Templates
Cloud-managed Chrome Browser, Manage Chrome Browser with Microsoft Intune
To properly configure these Chrome policies, please consult your system administrator. To confirm whether the Chrome policies
are correctly configured on the client, perform the following steps:
1. Open Google Chrome

2. Type chrome://policy in the location bar and press enter
3. Verify the following Chrome policy values and status:
Policy values
AutoOpenAllowedForURLs: hostname(s) of the Oracle E-Business Suite environment(s)
AutoOpenFileTypes: jnlp
Status value: OK
Default behavior (without Chrome policies)
The following describes a common use case of launching the Forms application with Java Web Start using Google Chrome. The
same concept applies to regular Java applets.
1. Open Google Chrome.

5. Google Chrome displays the following message: "This type of file can harm your computer. Do you want to keep
frmservlet.jnlp anyway?"

Note: This warning message is expected due to restrictions enforced by Google Chrome.
6. Click Keep to save the frmservlet.jnlp file.

7. Click the frmservlet.jnlp file in the download bar to run it.

8. The Forms application is now started with Java Web Start.
A new frmservlet.jnlp file is downloaded each time the Forms application or a regular Java applet is launched. The file is
saved in the default download location as defined in Google Chrome. Upon launching frmservlet.jnlp, the Java Web Start
launcher will automatically remove this file.
Behavior when having a specific location for each download preference set
28/7/22, 14:43 Document 2188898.1
Google Chrome has the option to present a Save As dialog window for every file downloaded. This feature is described on the
Chrome Help page Download a file on Chrome. More specifically, the section "Change download locations" covers the "Ask
where to save each file before downloading" user preference.
The following describes a common use case of launching the Forms application with Java Web Start using Google Chrome
when the "Ask where to save each file before downloading" preference is enabled.
1. Open Google Chrome.

3. Choose a responsibility (such as System Administrator).
4. Click on an Oracle Forms based menu item (for example, Security → User → Define) to initiate the download of
frmservlet.jnlp.
5. Google Chrome displays a Save As dialog window, asking where to save the frmservlet.jnlp.
6. Click frmservlet.jnlp in the download bar to run it:
7. The Forms application is started with Java Web Start.
6.5 Microsoft Edge
The Forms application and regular Java applets as part of Oracle E-Business Suite can run only with Java Web Start when
using the Microsoft Edge web browser. It has never supported NPAPI-based extensions such as the Java Plug-in.
Default behavior
The following describes a common use case of launching the Forms application with Java Web Start using Edge. The same
concept applies to regular Java applets.
1. Open the Edge web browser.

3. Choose a responsibility (such as System Administrator).
4. Click on an Oracle Forms based menu item (for example, Security → User → Define) to initiate the download of
frmservlet.jnlp.
5. A new browser tab opens and the downloaded frmservlet.jnlp is saved in the Downloads folder as shown in the
following image:

6. Click Open to run the file frmservlet.jnlp.

7. The Forms application is started with Java Web Start.
The Java Web Start launcher automatically removes the downloaded frmservlet.jnlp file from the browser's download
folder.
The extra blank browser tab in step 5 remains open even after opening the Forms application. This is the expected behavior as
a result of web browser limitations. It is safe to close this browser tab that opened when downloading the frmservlet.jnlp
file.
6.6 Microsoft Edge (Chromium)
Microsoft Edge (Chromium) version 83 and later requires the usage of Java Web Start to launch Oracle Forms based modules
and other Java applets that are part of Oracle E-Business Suite.
Recommended browser configuration using Edge policies (Windows only)
Microsoft Edge (Chromium) version 85 and later supports automatic opening of the Forms application and regular Java applets
as part of Oracle E-Business Suite offering the best user experience for the end users. This requires the configuration of two
28/7/22, 14:43 Document 2188898.1
Microsoft Edge policies.
Microsoft Edge policy Description Required value
AutoOpenFileTypes 1 List of file types that should be automatically opened on download. jnlp
AutoOpenAllowedForURLs URLs where AutoOpenFileTypes can apply. .ebs.example.com 2
1 Microsoft Edge policy AutoOpenFileTypes requires Windows clients to be joined to a Microsoft Active Directory domain,
running on Windows 10 Pro, or associated with Enterprise instances that are enrolled for device management.
2It is recommended to match the exact hostname of the Oracle E-Business Suite web entry point. This is done by
adding a leading period. For example a value of .exacthost.example.com will match only the hostname
exacthost.example.com.
Microsoft Edge policies are centrally managed by system administrators as Group Policy Object (GPO) using Microsoft Active
Directory or Microsoft Intune. Deployment instructions supported by administrative templates (.admx) for Microsoft Edge
(Chromium) are described on the following Microsoft Edge Enterprise pages:
Configure Microsoft Edge policy settings on Windows

Configure Microsoft Edge policy settings in Microsoft Intune
To properly configure these Microsoft Edge policies, please consult your system administrator. To confirm whether the
Microsoft Edge policies are correctly configured on the client, perform the following steps:
1. Open Microsoft Edge (Chromium)

2. Type edge://policy in the location bar and press enter
3. Verify the following Chrome policy values and status:
Policy values
AutoOpenAllowedForURLs: hostname(s) of the Oracle E-Business Suite environment(s)
AutoOpenFileTypes: jnlp
Status value: OK
Default behavior (without Microsoft Edge policies)
The following describes a common use case of launching the Forms application with Java Web Start using Microsoft Edge
(Chromium). The same concept applies to regular Java applets.
1. Open Microsoft Edge (Chromium).

5. Microsoft Edge (Chromium) displays the following message: "This type of file can harm your computer. Do you want to
keep frmservlet.jnlp anyway?"

Note: This warning message is expected due to restrictions enforced by Microsoft Edge (Chromium).
6. Click Keep to save the frmservlet.jnlp file.

7. Click the frmservlet.jnlp file in the download bar to run it.

8. The Forms application is now started with Java Web Start.
28/7/22, 14:43 Document 2188898.1
A new frmservlet.jnlp file is downloaded each time the Forms application or a regular Java applet is launched. The file is
saved in the default download location as defined in Microsoft Edge. Upon launching frmservlet.jnlp, the Java Web Start
launcher will automatically remove this file.
6.7 Apple Safari
When using the Safari web browser on macOS, Oracle E-Business Suite always uses the Java Plug-in instead of Java Web Start
for launching the Forms application and Java applets. It automatically falls back to the Java Plug-in, even if the environment
(at the site level) is configured for Java Web Start.
6.8 Using Multiple Forms Sessions with Java Web Start
6.8.1 Overview
6.8.2 Switching
Between Single or Multiple Forms Sessions
6.8.3 Comparison Between Java Web Start and Java Plug-in
Implementation

Oracle E-Business Suite Environments
6.8.4 Key Aspects of Multiple Forms Sessions Support When Accessing Multiple
Concurrently
6.8.1 Overview
Certain use cases benefit from running multiple Forms sessions of the same Oracle E-Business Suite environment concurrently
on the client. This functionality is available when using the Java Plug-in and Internet Explorer as described in Document
389422.1, Recommended Browsers for Oracle E-Business Suite, section 'Multiple EBS Java Sessions'.
Multiple Forms sessions using Java Web Start is supported with all supported web browsers on Windows, and Firefox on
macOS. It is required to apply the application technology patches as listed in 4.5 Required Patches for Multiple Forms Session
Support Using Java Web Start. The minimum JRE requirement on the client is described in 2.1 How Does Java Web Start
Impact the Oracle E-Business Suite Architecture? . Similar to the Java Plug-in, a user can run multiple Forms sessions of the
same Oracle E-Business Suite environment concurrently on the client using Java Web Start.
It is supported to run one or more Forms sessions of different Oracle E-Business Suite environments (for example, a
development and production environment) at the same time on the client tier using Java Web Start. This does not require
using different web browsers for each Oracle E-Business Suite environment.
6.8.2 Switching Between Single or Multiple Forms Session
A new user preference on the General Preferences page controls the behavior of launching the Forms application when using
Java Web Start.
Unchecked (default): Only single instance of the Forms application will run on the client. If it is already running, the
existing instance will be reused.
Checked: A new instance of the Forms application is created for every invocation of a Forms based form function (URL)
from an OAF/JSP/... page in the web browser.
You can toggle between either option as desired.
The user preference is enabled only when the user is set up to use Java Web Start as described in Section 5: Enabling Java
Web Start. Otherwise, the user preference will be grayed out as the user is using the Java Plug-in to launch the Forms
application.
The following steps describe by example how to set the user preference to use multiple Forms sessions:
1. Open a web browser (for example Firefox).

2. Log in to Oracle E-Business Suite (for example SYSADMIN).
3. Click on the Settings icon.
28/7/22, 14:43 Document 2188898.1
4. Choose Preferences.
5. Check the check box for "Always Launch New Forms Session".
6. Go back to the home page.
7. In the Navigator panel, click on Alert Manager, Vision Enterprises to expand.
8. Click on Distribution List.
→ The first Forms session is launched.
9. Go back to the browser.
10. In the navigator under Alert Manager, Vision Enterprises click on History.
→ A second Forms session is launched.
11. ...
New Forms sessions will continue to be opened when invoked from the web browser.
To switch back to a single Forms session, change the user preference back to unchecked. Note that existing Forms sessions
running on the client will remain as-is.
6.8.3 Comparison Between Java Web Start and Java Plug-in Implementation
The following table lists the key differences of run multiple Forms sessions on a client using Java Web Start or the Java Plug-in.
Multiple Forms versus EBS Sessions

Java Web Start Java Plug-in
Support
Supported browsers Windows: Internet Explorer, Firefox ESR, Chrome, Internet

Edge Explorer

Firefox ESR
macOS:
Supported operating systems Windows and macOS Windows
Number of Forms sessions One or more One or more
Number of product-specific Java applets 1 One or more
This new implementation of running multiple Forms instances concurrently on the client using Java Web Start does not rely on
of any browser-specific functionality. A user can continuously create new Forms instances with each activity within self service
/ the web browser that is linked to a Forms based functionality. Therefore, there is a one-to-many relationship between an
Oracle E-Business Suite browser session and the Forms sessions.
In comparison to the Java Plug-in approach using Internet Explorer, you create multiple Oracle E-Business Suite sessions by
launching each application session through a new browser session. These browser sessions are fully independent from one
another. For each one, a single Forms instance can be launched. In other words, there's always a one-to-one relationship
between an Oracle E-Business Suite browser session and a Forms session. The same behavior when using the Java Plug-in
cannot be achieved using Java Web Start.
6.8.4 Key Aspects of Multiple Forms Sessions Support When Accessing Multiple Oracle E-Business Suite
Environments Concurrently
This section summarizes some important aspects of multiple Forms sessions support when accessing multiple Oracle E-
Business Suite environments.
Forms application: There are no restrictions when connecting to two or more different Oracle E-Business Suite
environments (for example, PROD and DEV). Multiple Forms instances of each Oracle E-Business Suite environment can
run concurrently on the client using Java Web Start.
Product-specific Java applets (such as Help Builder, Workflow Status diagram, ...): Only one (1) instance of a product-
specific Java applet per Oracle E-Business Suite environment can run concurrent on the client using Java Web Start. For
example, when being connected to both a production and development environment, then for each of them a single
instance of the Help Builder can be running on the client.
Section 7: Known Issues

This section lists current known issues and restrictions of Java Web Start usage with Oracle E-Business Suite.
28/7/22, 14:43 Document 2188898.1
7.1 Only Different Java Applets May Run Simultaneously

7.2 Single Forms Session Allowed Per Oracle E-Business Suite Environment
7.3 Java Console Showing java.security.KeyStoreException: WIExplorerMy not found
7.4 Internet Explorer: Launching Java Applet Intermittent Fails Due to "frmservlet.jnlp might have been moved or deleted"
7.5 Directly Opening the Forms Application Leaves a Blank Browser Window Open
7.6 Forms Socket Mode is Not Supported with Java Web Start
7.7 Browser Tab Does Not Close After Uploading a File Attachment
7.8 Issues Closing HTML Pages After Opening From Forms Application
7.9 Buildup of JNLP files in the Browser's Download Folder
7.10 Product-specific Java Applets Supporting Only the Java Plug-in
7.11 Financial Dimension Hierarchy Manager Does Not Launch Using Java Web Start on Oracle E-Business Suite Release 12.1.3
7.12 Patch Failure On afgstusr.sql When Applying Application Technology Patch or Product Specific Patch
7.13 Oracle Discoverer Not Certified For Use With Java Web Start
7.14 Unable to Launch Forms Application or Java applets using Java Web Start on Windows 10 Creators Update via Internet
Explorer 11
7.15 JNLP Files in the Browser's Download Folder are not Automatically Removed Using Firefox ESR on macOS
7.16 Java Console Shows java.lang.IllegalArgumentException When Using Java Web Start on macOS
7.17 Generating a Graphical Display of Planning Data from the Planner Workbench Opens a Blank Browser Window
7.18 A Web Page Launched from the Forms Application Opens in a New Browser Window Instead of a New Browser Tab
7.19 Mozilla Firefox Extended Support Release (ESR) Shows a Warning Message When Launching Java Content using Java Web
Start
7.20 Unable to Open URLs From the Forms Application or Java Applets When Using JRE 8 Update 291 or Later
7.21 Running the frmservlet.jnlp from Google Chrome Intermittently Fails
7.1 Only Different Java Applets May Run Simultaneously
Attempting to launch a Java applet which is already running will show the following message: "This Applet is already running.
Please close the Applet and try again."
This applies to the product specific Java applets (for example, Help Builder, Workflow Status diagram, ...) as part of Oracle E-
Business Suite, and does not apply to the Forms application. Using Java Web Start, only a single instance of each of these Java
applets can run on the client for a given Oracle E-Business Suite environment. For example, one or more instance of the Forms
application (with multiple Forms session support), one instance of the Help Builder, and one instance of the Workflow Status
diagram can run in parallel. Each of these product specific Java applets are launched from the same web browser, and thus
share the same application session.
In case of accessing different Oracle E-Business Suite environments using Java Web Start at the same time (either from the
same or different web browsers), only a single instance of each product specific Java applets per environment can run on the
client.
Internet Explorer users can run multiple Oracle E-Business Suite sessions by adding the -noframemerging parameter to the
browser launch command (iexplorer.exe) when using the Java Plug-in. Using this parameter with Java Web Start may bring
up the login form again requiring the user to log in again, when switching between the Forms application and any of the other
Java applets of Oracle E-Business Suite. It is advised to remove the -noframemerging parameter from the Internet Explorer
launch command if this problem occurs. For information on setting this parameter, see "Multiple EBS Sessions" in Document
389422.1, Recommended Browsers for Oracle E-Business Suite Release 12.
7.2 Single Forms Session Allowed Per Oracle E-Business Suite Environment
The initial release of Java Web Start for Oracle E-Business Suite allowed only a single instance of the Forms application of a
specific Oracle E-Business Suite environment to run on the client tier. For example, using Java Web Start to launch the Forms
application from Internet Explorer will start a single Forms session. After that happens, using Firefox ESR on the same client to
launch a Forms link from the same Oracle E-Business Suite environment (for example, PROD) will direct the focus to the Forms
application that was already launched by Internet Explorer. At the same time, it is possible to open a single Forms session for a
different Oracle E-Business Suite environment (for example, DEV) from any support web browser.
This limitation is resolved as part of multiple Forms session support. The application technology patches as listed in 4.5
Required Patches for Multiple Forms Session Support Using Java Web Start add support for running multiple Forms sessions for
a given Oracle E-Business Suite environment concurrently on the client. A new user preference allows an end user to control
whether to use a single or multiple Forms sessions of a specific Oracle E-Business Suite environment. For further information,
28/7/22, 14:43 Document 2188898.1
see 6.8 Using Multiple Forms Sessions with Java Web Start. This enhancement also allows running multiple Forms sessions for
different Oracle E-Business Suite environments (for example, DEV) at the same time.
7.3 Java Console Showing java.security.KeyStoreException: WIExplorerMy not found
The following exception may show in the Java Console when using Java Web Start against an SSL/TLS enabled environment:
java.security.KeyStoreException: WIExplorerMy not found
at java.security.KeyStore.getInstance(Unknown Source)
at com.sun.deploy.services.WPlatformService$1.run(Unknown Source)
at com.sun.deploy.services.WPlatformService$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
...
at java.lang.Thread.run(Unknown Source)
Caused by: java.security.NoSuchAlgorithmException: WIExplorerMy KeyStore not available
at sun.security.jca.GetInstance.getInstance(Unknown Source)
at java.security.Security.getImpl(Unknown Source)
... 26 more
This exception can be ignored as it has no impact on the usability of the environment. It is fixed in Java 8 Update 201 and
later.
7.4 Internet Explorer: Launching Java Applet Intermittent Fails Due to "frmservlet.jnlp might have been moved
or deleted"
Microsoft Internet Explorer may fail to download the JNLP file and as a result it does not launch the Forms application or Java
applet. Instead, the following error is shown in the notification bar: "frmservlet.jnlp might have been moved or deleted."
This is a very intermittent issue (Bug 24528971) which may require a workaround as described on the Microsoft Support
website. For further information, see File is "moved or deleted" or "cannot be found" error when you download PDF files in
Internet Explorer 11 in Windows.
7.5 Directly Opening the Forms Application Leaves a Blank Browser Window Open
When using Java Web Start, you may notice that a blank browser window opens and does not automatically close when
launching Forms-based applications (Bug 24954981). This occurs when directly accessing the Forms application via
<s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_webport>/forms/frmservlet as
described in Document 552301.1, How To Access Forms Directly In Oracle Applications R12. Most application users will not
launch the Forms application directly as this functionality is not enabled by default.
This is the expected behavior. It is safe to close the browser window after launching the Forms application.
7.6 Forms Socket Mode is Not Supported with Java Web Start
By default, Oracle E-Business Suite Release 12.2 and 12.1 supports Oracle Forms 10g in servlet mode only. The use of socket
mode as described in Document 384241.1, Using Forms Socket Mode with Oracle E-Business Suite Release 12 is not supported
with Java Web Start.
7.7 Browser Tabs Do Not Close After Uploading a File Attachment or Restoring the Session after a Forms
Session Timeout
Impacts: Mozilla Firefox ESR, Google Chrome
Some functional flows in EBS open a browser tab/window from an Oracle Forms application. However, the browser tab/window
is unexpectedly left with an empty page after completing the transaction, and the following URL is shown in the browser's
address bar:
28/7/22, 14:43 Document 2188898.1
<s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_webport>OA_HTML/OALogout.jsp?
closeWindow=true&menu=Y
Examples of such functional flows are uploading a file attachment and EBS session timeout.
Solution: Apply whichever of the following patches is relevant.
Oracle E-Business Suite Release 12.2: patch 32421510:R12.FND.C

Oracle E-Business Suite Release 12.1: patch 33072993:R12.FND.B
After the appropriate patch has been applied, the browser tab/window will display the message "Please close this browser tab
or window". (The browser tab/window cannot be closed automatically as a result of browser limitations, reported in Bug
24321183).
7.8 Issues Closing HTML Pages After Opening From Forms Application
Impacts: Internet Explorer and Chrome
In Microsoft Internet Explorer, an additional dialog box appears when closing an HTML page as shown in the following screen
shot:
The end user is expected to click OK to close the browser window or tab.
In Google Chrome, closing an HTML page leaves a blank tab or window open. This can safely be closed manually. These blank
tabs or windows may accumulate as you open/close further pages from the Forms application.
7.9 Buildup of JNLP files in the Browser's Download Folder
Impacts: Mozilla Firefox ESR, Google Chrome, Microsoft Edge
Launching the Forms application or a Java applet requires the download of a JNLP file frmservlet.jnlp, frmservlet (1-
n).jnlp). Browsers such as Mozilla Firefox, Google Chrome, and Microsoft Edge save these JNLP files in their respective
browser's download location on the local PC. These are automatically removed by Java Web Start when launched from the web
browser by following the instructions described in Section 6: Browser User Experience and Configuration.
A buildup of JNLP files on the local file system may occur if the end user does not launch the downloaded JNLP files. It is safe
to manually remove old JNLP files from the browser's download directory for those that were not used to launch the Forms
application or a regular Java applet.
7.10 Product-specific Java Applets Supporting Only the Java Plug-in
The following product-specific features are only supported with the Java Plug-in:
Oracle Call Center Technology: the computer-telephone integration (CTI) feature that allows for integrations of Oracle
E-Business Suite with third-party telephone systems.
Oracle Demand Planning: the Demand Planning UI for managing Demand Planning objects such as documents,
measures, custom aggregates, saved selections, alerts, and scenarios.
Currently, these Java applets do not support Java Web Start.
7.11 Financial Dimension Hierarchy Manager Does Not Launch Using Java Web Start on Oracle E-Business
Suite Release 12.1.3
28/7/22, 14:43 Document 2188898.1
The Financial Dimension Hierarchy Manager fails to launch using Java Web Start on Oracle E-Business Suite Release 12.1.3.
The following exception is encountered when trying to launch it:
ExitException[ 3]com.sun.deploy.net.FailedDownloadException: Unable to load resource: https://ebs.example.com:4443/

at sun.plugin2.applet.JNLP2Manager.downloadResources(Unknown Source)
at sun.plugin2.applet.JNLP2Manager.prepareLaunchFile(Unknown Source)
at sun.plugin2.applet.JNLP2Manager.loadJarFiles(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
The issue reported to development as bug 6922442.
Workaround: Create an empty $OA_JAVA/jbodatum111.jar file on the Oracle E-Business Suite application tier.
7.12 Patch Failure On afgstusr.sql When Applying Application Technology Patch or Product Specific Patch
In rare cases, a patch failure may be encountered when applying the application technology patch for FND, or any of the
product specific patch. The AD (online) patch utility will show the following:
FAILED: file afgstusr.sql on worker 1 for product fnd username APPLSYS.
The corresponding AD worker log file shows the following:
sqlplus -s APPS/***** @/u01/R1213_EBS/MT/apps/apps_st/appl/fnd/12.0.0/patch/115/sql/afgstusr.sql &pw_apps
Connected.
DECLARE
ERROR at line 1:
ORA-04063: package body "APPS.FND_WEB_SEC" has errors
ORA-06508: PL/SQL: could not find program unit being called: "APPS.FND_WEB_SEC"
ORA-06512: at line 56
Complete the following steps to resolve the patch failure:
1. Abort the failed patch session.

2. Apply Patch 25475909 FND Core Security Fix And AD Prereq Combo Patch (available for both Oracle E-Business Suite
Release 12.2 and 12.1).
3. Apply the application technology patch or product-specific patch that initially failed.
7.13 Oracle Discoverer Not Certified For Use With Java Web Start
Oracle Discoverer is not certified for use with Java Web Start on both Oracle E-Business Suite Release 12.2 and 12.1. The
impact is limited to Discoverer Plus as part of Oracle Discoverer.
Users should continue to run Discoverer Plus using the Java SE (JRE) Plug-in technology.
For further information about Oracle Discoverer, see:
Oracle Lifetime Support Policy: Oracle Fusion Middleware

Document 1634827.1, Oracle Business Intelligence Discoverer Statement of Direction - March 2014
7.14 Unable to Launch Forms Application or Java applets using Java Web Start on Windows 10 Creators Update
via Internet Explorer 11
The Forms application and other Java applets in Oracle E-Business Suite fail to launch with Java Web Start when using Internet
Explorer 11 on the Windows 10 Creators Update. It is also not possible to manually run the JNLP file from Internet Explorer
11.
28/7/22, 14:43 Document 2188898.1
This is a known Java issue (JDK-8185661) that occurs only when having installed JRE 8 32-bit and 64-bit at the same time on
the Windows 10 Creators Update, and when attempting to launch Java Web Start applications using Internet Explorer 11.
This issue is resolved as of Java 8 Update 161. As a workaround: Uninstall the 64-bit JRE 8 so only the 32-bit JRE 8 is installed
on the client.
7.15 JNLP Files in the Browser's Download Folder are not Automatically Removed Using Firefox ESR on macOS
Impacts: Mozilla Firefox ESR on macOS
Launching the Forms application or a Java applet downloads a JNLP file frmservlet or frmservlet (1-n) to the Downloads
folder of the web browser. Firefox allows this JNLP file to be directly launched from the web browser using the Java Web Start
launcher. The JNLP file is not automatically removed by Java Web Start.
The solution will be included in a future Java release. It is safe to manually remove any old JNLP files from the browser's
download directory.
7.16 Java Console Shows java.lang.IllegalArgumentException When Using Java Web Start on macOS
Impacts: Mozilla Firefox ESR on macOS
The Java console log may show the following exception upon launching the Forms application or Java applet using Java Web
Start on macOS.
Exception in thread "AWT-EventQueue-2" java.lang.IllegalArgumentException: null source
at java.util.EventObject.<init>(EventObject.java:56)
at java.awt.AWTEvent.<init>(AWTEvent.java:337)
at java.awt.event.ComponentEvent.<init>(ComponentEvent.java:120)
at java.awt.event.WindowEvent.<init>(WindowEvent.java:206)
at java.awt.event.WindowEvent.<init>(WindowEvent.java:251)
at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:784)
...
This exception can be ignored as it has no impact on the usability of the environment. A fix for this issue is being worked upon
by development.
7.17 Generating a Graphical Display of Planning Data from the Planner Workbench Opens a Blank Browser
Window
Impacts: Google Chrome, Microsoft Edge, Firefox ESR (Windows and macOS)
A graphical representation of planning data can be generated from the Planner Workbench as part of Oracle Material
Requirements Planning (MRP). Generating such a horizontal plan graph from the Forms application opens a new browser
window or tab. A blank page is shown in the browser instead of the actual graph, and no errors are seen.
The issue reported to development as Bug 28714237.
Workaround: Use the Planner Workbench which shows the same data in tabular format. Alternatively, use a web browser that
supports the Java Plug-in such as Internet Explorer.
7.18 A Web Page Launched from the Forms Application Opens in a New Browser Window Instead of a New
Browser Tab
Impacts: Internet Explorer
Certain use cases, for example opening the Online Help, involve opening a web page from the Forms application. If Internet
Explorer is the browser that launched the Forms application, then the web page is opened in a new browser window instead of
a new browser tab.
This is the expected behavior as a result of web browser limitations. It is safe to close the newly created browser window
when it is no longer required.
28/7/22, 14:43 Document 2188898.1
7.19 Mozilla Firefox Extended Support Release (ESR) Shows a Warning Message When Launching Java Content
using Java Web Start
Impacts: Mozilla Firefox ESR 68.0 and 68.1
Due to a security fix introduced in Firefox ESR 68.0 and 68.1 a warning message is always shown when launching Java content
with Java Web Start on Windows clients:
Solution: The issue is resolved with Firefox ESR 68.2 and later. See 6.3 Mozilla Firefox Extended Support Release (ESR) for
further information about the default browser behavior of Firefox ESR 68.2 and later.
7.20 Unable to Open URLs From the Forms Application or Java Applets When Using JRE 8 Update 291 or Later
Impacts: All supported browsers on Windows and macOS
Attempting to open a URL from the Forms application or any other Java applet in Oracle E-Business Suite may appear to do
nothing, but no errors are seen. Example scenarios include accessing help; viewing concurrent request output or log files;
uploading file type type attachments; or navigating back to a self-service page.
The root cause is a change in behavior starting with JRE 8 Update 291 resulting in a potential failure when opening URLs from
the Forms application or Java applets when using Java Web Start. The unexpected behavior is typically observed with the
Microsoft Edge (legacy or Chromium) browser. However, other browsers supported with EBS may encounter similar issues
when attempting to open URLs from forms or Java applets.
Solution: See 4.8 Required Patches for Compatibility with JRE 8 Update 291 and later for the required patches to resolve this
issue.
7.21 Running frmservlet.jnlp from Chrome Intermittently Fails
Impacts: Chrome on Windows
The browser launches a Forms application or Java applet using Java Web Start by running the downloaded frmservlet.jnlp file.
If no Chrome browser policies are configured on the client to automate this process, you can run the frmservlet.jnlp file by
clicking on the frmservlet.jnlp file in the Chrome browser download bar.
With Google Chrome, trying to run the frmservlet.jnlp file by clicking on it in the download bar intermittently fails. No error
messages or indications of a failure are displayed. You should click again on the downloaded frmservlet.jnlp file, multiple times
if needed. After a few attempts, the file should run successfully and the Forms application launch as expected.
Solution: The issue is resolved in JRE 8 Update 301 b33, a bundle patch release available via My Oracle Support as Patch
33195274. The Java bug fix will be included in JRE 1.8.0_311 and higher, scheduled for release in October 2021. For further
information, see My Oracle Support Knownledge Document 1682574.1 Java SE Versions, Patch Updates and Schedules: CPUs,
PSUs, BPRs, Public v. Support Only Releases.
Section 8: References
Refer to the following My Oracle Support knowledge documents for further information:
Document 2510500.1, FAQ: Essentials of Java Usage in Oracle E-Business Suite

Document 389422.1, Recommended Browsers for Oracle E-Business Suite Release 12
Document 437878.1, Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12
28/7/22, 14:43 Document 2188898.1
Document 1591073.1, Enhanced Jar Signing for Oracle E-Business Suite

Document 393931.1, Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12
Document 1533334.1, Oracle E-Business Suite Release Notes for Apple macOS Clients, Release 12
Document 1682574.1, Java SE Update Releases and Schedules: Critical Patch Updates, Minor Updates, Early Access,
Public, and Commercial
Document 1155883.1, Oracle E-Business Suite Desktop Client Hardware and Software Requirements
Change Log
Date Description
Jul 28, 2022

Updated 2.1 How Does Java Web Start Impact the Oracle E-Business Suite Architecture?
Aug 25, 2021

Added minimum JRE release requirements for macOS Big Sur and earlier clients
Added patches for Firefox ESR on macOS Big Sur support (macOS Big Sur and earlier clients)
Added 6.3.1 Firefox ESR for Windows Users
Updated known issue 7.7 Browser Tabs Do Not Close After Uploading a File Attachment or Restoring
the Session after a Forms Session Timeout
Added known issue 7.21 Running the frmservlet.Jnlp from Google Chrome Intermittently Fails
Jun 16, 2021

Added compatibility patches for JRE 8 Update 291 and later
Added known issue 7.20 Unable to Open URLs From the Forms Application or Java Applets When
Using JRE 8 Update 291 or Later
Jan 23, 2021

Added Recommended browser configuration using Chrome policies
Added Recommended browser configuration using Edge policies
Aug 6, 2020
Added Mozilla Firefox Extended Support Release (ESR) 78.x
Jul 21, 2020

Added Microsoft Edge (Chromium)
Oct 30, 2019

Updated section 6.3 Mozilla Firefox Extended Support Release (ESR)
Updated section 4.3.2 Oracle Forms 10g Technology Patch for Oracle E-Business Suite Release 12.1
with a reference to Document 437878.1, Upgrading OracleAS 10g Forms and Reports in Oracle E-
Business Suite Release 12
Added known issue 7.19 Mozilla Firefox Extended Support Release (ESR) Shows a Warning Message
When Launching Java Content using Java Web Start
Aug 12, 2019

Added Mozilla Firefox Extended Support Release (ESR) 68.x
Added section 6.7.4 Key Aspects of Multiple Forms Sessions Support When Accessing Multiple Oracle
E-Business Suite Environments Concurrently
Updated known issues 7.1, 7.2, 7.3 and 7.4 with the latest information
Added known issue 7.18 A Web Page Launched from the Forms Application Opens in a New Browser
Window Instead of a New Browser Tab
Jan 21, 2019

Added multiple Forms session support with Java Web Start
Oct 24, 2018

28/7/22, 14:43 Document 2188898.1
Replaced patches 24709902:R12.OWF.C and 24709902:R12.OWF.B by 28713780:R12.OWF.C and

28713780:R12.OWF.B
Oct 18, 2018

Updated for added support of Firefox ESR on macOS using Java Web Start
Added FND Patch 28156520:R12.FND.C and 28156520:R12.FND.B
Added TXK Patch 28700057:R12.TXK.C and 28700057:R12.TXK.B
Added known issues 7.15, 7.16 and 7.17
Sep 7, 2018
Updated section 6.3 Mozilla Firefox Extended Support Release (ESR) due to end of end-of-life of
Firefox ESR 50.x
Sep 19, 2017

Added JRE 8 Update 144 as a certified Java release for JWS.
Added known issue 7.14 Unable to Launch Forms Application or Java applets using Java Web Start
on Windows 10 Creators Update via Internet Explorer 11
Jul 19, 2017

Added JRE 8 Update 141 (July CPU) as a certified Java release for JWS.
May 4, 2017
Updated section 7.2, clarifying that single Forms session limit is per EBS environment, not per client.
Apr 19, 2017

Initial publication.
My Oracle Support Knowledge Document 2188898.1 by Oracle E-Business Suite Development.
Copyright © 2017, 2022, Oracle and/or its affiliates.
Didn't find what you are looking for?

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

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

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

Uploaded by

Copyright:

Available Formats

28/7/22, 14:43 Document 2188898.

There is a change log at the end of this document.

This document is divided into the following sections:

Section 1: About Java Web Start

Section 1: About Java Web Start

1.1 What is Java Web Start?

1.2 Architectural Comparison of Java Plug-in and Java Web Start

Figure 1: Java Plug-in architecture Figure 2: Java Web Start architecture

1.3 Why is Oracle E-Business Suite Implementing Java Web Start?

Section 2: Impact of Java Web Start on Oracle E-Business Suite

JRE 8 Update 144 b01 Patch 26512977 or

Section 3: Recommended Browsers

Section 4: Applying Required Patches

4.1 Minimum Java Runtime Environment for Java Web Start

4.2 Required Patches for Oracle E-Business Suite Release 12.2

4.4 Patch Application Instructions

4.1 Minimum Java Runtime Environment for Java Web Start

Download through the

For further information on Java releases, see:

Java Development Kit 8 Update Release Notes

4.2 Required Patches for Oracle E-Business Suite Release 12.2

4.2.1 Minimum Prerequisites

4.2.4 Product-Specific Patches for Oracle E-Business Suite Release 12.2

4.2.1 Minimum Prerequisites

Oracle E-Business Suite Release 12.2.3

Document 1586214.1, Oracle E-Business Suite Release 12.2.3 Readme

The following table lists all required application technology patches.

Application Technology Patch Description Patch Number

4.2.4 Product-Specific Patches for Oracle E-Business Suite Release 12.2

Product Feature Patch Number

Oracle Workflow Status Diagram; Notification signing with Digital Patch

Oracle Scripting Script Author Patch 23475123:R12.IES.C

Oracle Customers Online Party Relationships Patch

Oracle General Ledger Account Hierarchy Manager Patch 23645622:R12.GL.C

Oracle Sourcing Auction Monitor Patch

Oracle Installed Base Visualizer Applet Patch 22221603:R12.CSI.C

Oracle Advanced Supply Chain Plan Editor (PS/SNO) Patch

Oracle Process Manufacturing Recipe Designer Patch

4.3 Required Patches for Oracle E-Business Suite Release 12.1

4.3.1 Minimum Prerequisites

4.3.4 Product-Specific Patches for Oracle E-Business Suite Release 12.1

4.3.1 Minimum Prerequisites

Oracle E-Business Suite Release 12.1.3

Document 1080973.1, Oracle E-Business Suite Release 12.1.3 Readme

The following table lists all required application technology patches.

Application Technology Patch Description Patch Number

4.3.4 Product-Specific Patches for Oracle E-Business Suite Release 12.1

Product Feature Patch Number

Oracle Workflow Status Diagram; Notification signing with Digital Patch

Oracle Scripting Script Author Patch 23475123:R12.IES.B

Oracle Customers Online Party Relationships Patch

Oracle General Ledger Account Hierarchy Manager Patch 25140916:R12.GL.B

Oracle Sourcing Auction Monitor Patch

Oracle Installed Base Visualizer Applet Patch 25075128:R12.CSI.B

Oracle Advanced Supply Chain Plan Editor (PS/SNO) Patch

Oracle Process Manufacturing Recipe Designer Patch

4.4 Patch Application Instructions

4.4.1 Applying Patches to Oracle E-Business Suite Release 12.2

4.4.1 Applying Patches to Oracle E-Business Suite Release 12.2

1. Source the APPS environment.

$ source <EBS_ROOT>/EBSapps.env run

2. Start a new online patch cycle.

3. Apply the Oracle Forms 10g technology patch.