Java Web Start Configuration.

Applying Patches on Oracle E-Business Suite Release 12.1

Source the environment file.

Stop all application tier services.

Use OPatch to apply the latest Oracle Forms 10g technology overlay patch against the OracleAS 10.1.2
ORACLE_HOME.

Patch 25441839

Application Technology Patch Description Patch Number

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

Status Diagram; Notification signing with Digital Patch

Oracle Workflow
Signature 24709902:R12.OWF.B

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

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

Patch
Oracle Sourcing Auction Monitor
23575933:R12.PON.B

Oracle Process Patch

Recipe Designer
Manufacturing 24833534:R12.GMD.B
Use the AD Administration tool (adadmin) to regenerate JAR files with force option.

$ 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

Start all application tier services.

The installation of the patches does not enable Java Web Start. The Java Plug-in remains the default
launch method for all application users.

Configuring and Enabling Java Web Start

The following two launch methods are available:

1. 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.

2. 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.

New Context Variable:

s_forms_launch_method = browser (use Java Plug-in) -- DEFAULT VALUE

s_forms_launch_method = jws (use Java Web Start)

Profile Options

Enable Java Web Start / FND_ENABLE_JAVA_WEB_START

  Yes - Use Java Web Start
 No - Use Java Plug-in -- DEFAULT VALUE

ICX: Forms Launcher / ICX_FORMS_LAUNCHER

The URL for launching the Forms application.

Possible values:

 Site level default:

<s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_webport>/form
s/frmservlet – DEFAULT VALUE
 Java Plug-in:
<s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_webport>/form
s/frmservlet?config=browserMode
 Java Web Start:
<s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_webport>/form
s/frmservlet?config=jws

Note: 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.

Set Java Web Start as the default for all application users

Option 1: 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.

$ 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
<s_webentryurlprotocol>://<s_webentryhost>.<s_web
ICX: Forms Launcher / ICX_FORMS_LAUNCHER
entrydomain>:<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 Auto Config.

Different options to configure Java Web Start:

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:
o Enable Java Web Start is set to No
o ICX: Forms Launcher set to
<s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_
webport>/forms/frmservlet

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_webpor
t>/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:
o 'Enable Java Web Start' is set to Yes
o 'ICX: Forms Launcher' set to
<s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_
webport>/forms/frmservlet

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

 'Enable Java Web Start' is set to No

 'ICX: Forms Launcher' set to
<s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_webpor
t>/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.

Browser User Experience and Configuration

Microsoft Internet Explorer
There are no specific browser configuration steps required.

Mozilla Firefox Extended Support Release (ESR)

Firefox ESR 52 is the final release that supports the Java Plug-in. Oracle E-Business Suite users can use
either Java Web Start or the Java Plug-in until Mozilla release the next major ESR release (expected early
2018 with Firefox ESR 59.0).

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.

Apple Safari
On Mac OS, 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.
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.

Known Issues and Limitations

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

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