What is Java Web Start and how is it launched?
The Java Web Start software allows you to download and run Java applications from the web. The Java Web Start software:
Provides an easy, one-click activation of applications
Guarantees that you are always running the latest version of the application
Eliminates complicated installation or upgrade procedures
Getting Java Web Start Software
Java Web Start is included in the Java Runtime Environment (JRE) since release of Java 5.0. This means that when you install Java, you get Java Web Start installed automatically. The Java Web Start software is launched automatically, when a Java application using Java Web Start technology is downloaded for the first time.
The Java Web Start software caches (stores) the entire application locally on your computer. Thus, any subsequent launches are almost instantaneous as all the required resources are already available locally. Every time you start the application, the Java Web Start software component checks the application's website to see if a new version is available, and if so, automatically downloads and launches it.
Let us see how to build this in Our R12.1 series:
List of Patches to be downloaded:
JRE 8 Update 121 b33 Patch 25767257*
R12.AD.B.delta.8 23569686
DB Patch 19393542
Patch 24693065:R12.AD.B.
Patch 25441839 TechStack Patch.
Patch 24498616:R12.AD.B
Patch 24319156:R12.TXK.B
Patch 25380324:R12.FND.B
Patch 24709902:R12.OWF.B
Patch 23475123:R12.IES.B
Patch 25140916:R12.GL.B
Patch 25075128:R12.CSI.B
* JRE 8 Update 131 b31 Patch 25767257 has to be installed in all Client system which is the minimum requirement.
Steps to apply patches:
Source the environment file.
$ source <APPL_TOP>/APPS<CONTEXT_NAME>.env
Stop all application tier services.
$ <INST_TOP>/admin/scripts/adstpall.sh <apps user>/<apps password>
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. 25441839
Source environment file.
$ source <APPL_TOP>/APPS<CONTEXT_NAME>.env
Apply the required Oracle E-Business Suite application technology patches (AD/TXK/FND) as listed below:
R12.AD.B.delta.8 23569686
Pre-Requisites:
Apply DB Patch 19393542
Add "_plsql_conditional_compilation"=true
For running adgrants.sql, download Patch 24693065:R12.AD.B.
Execute adgrant.sql following the instructions in the ad_run_adgrants.xml PAA step.
Apply Patch 24693065:R12.AD.B.
AD.B.8 Patch application:
Patch 23569686.
Note: As higher version of adgrants.sql has already run as Prerequisite Step, you can skip executing adgrant.sql again for R12.AD.B.Delta.8 (Patch 23569686).
Post-Install Steps
Invoker's Right processing is re-enabled in the latest AD minipack. Customers who have already upgraded to 12.1.1 can optionally run AD Admin as follows to re-enable Invoker's Right on existing PL/SQL packages:
Run adadmin > Compile/Reload Applications Database Entities menu >
Compile APPS schema.
Choose "No" at the following prompt:
Run Invoker Rights processing in incremental mode [No]
Apply below patches using adpatch
Patch 24498616:R12.AD.B
Patch 24319156:R12.TXK.B
Patch 25380324:R12.FND.B
Apply product specific patches using adpatch
ProductPatch Number
Oracle WorkflowPatch 24709902:R12.OWF.B
Oracle ScriptingPatch 23475123:R12.IES.B
Oracle General LedgerPatch 25140916:R12.GL.B
Oracle Installed BasePatch 25075128:R12.CSI.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
The installation of the patches does not enable Java Web Start. The Java Plug-in remains the default launch method for all application users.
Enabling JWS For Specific 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>:<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_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.
The Java Web Start software allows you to download and run Java applications from the web. The Java Web Start software:
Provides an easy, one-click activation of applications
Guarantees that you are always running the latest version of the application
Eliminates complicated installation or upgrade procedures
Getting Java Web Start Software
Java Web Start is included in the Java Runtime Environment (JRE) since release of Java 5.0. This means that when you install Java, you get Java Web Start installed automatically. The Java Web Start software is launched automatically, when a Java application using Java Web Start technology is downloaded for the first time.
The Java Web Start software caches (stores) the entire application locally on your computer. Thus, any subsequent launches are almost instantaneous as all the required resources are already available locally. Every time you start the application, the Java Web Start software component checks the application's website to see if a new version is available, and if so, automatically downloads and launches it.
Let us see how to build this in Our R12.1 series:
List of Patches to be downloaded:
JRE 8 Update 121 b33 Patch 25767257*
R12.AD.B.delta.8 23569686
DB Patch 19393542
Patch 24693065:R12.AD.B.
Patch 25441839 TechStack Patch.
Patch 24498616:R12.AD.B
Patch 24319156:R12.TXK.B
Patch 25380324:R12.FND.B
Patch 24709902:R12.OWF.B
Patch 23475123:R12.IES.B
Patch 25140916:R12.GL.B
Patch 25075128:R12.CSI.B
* JRE 8 Update 131 b31 Patch 25767257 has to be installed in all Client system which is the minimum requirement.
Steps to apply patches:
Source the environment file.
$ source <APPL_TOP>/APPS<CONTEXT_NAME>.env
Stop all application tier services.
$ <INST_TOP>/admin/scripts/adstpall.sh <apps user>/<apps password>
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. 25441839
Source environment file.
$ source <APPL_TOP>/APPS<CONTEXT_NAME>.env
Apply the required Oracle E-Business Suite application technology patches (AD/TXK/FND) as listed below:
R12.AD.B.delta.8 23569686
Pre-Requisites:
Apply DB Patch 19393542
Add "_plsql_conditional_compilation"=true
For running adgrants.sql, download Patch 24693065:R12.AD.B.
Execute adgrant.sql following the instructions in the ad_run_adgrants.xml PAA step.
Apply Patch 24693065:R12.AD.B.
AD.B.8 Patch application:
Patch 23569686.
Note: As higher version of adgrants.sql has already run as Prerequisite Step, you can skip executing adgrant.sql again for R12.AD.B.Delta.8 (Patch 23569686).
Post-Install Steps
Invoker's Right processing is re-enabled in the latest AD minipack. Customers who have already upgraded to 12.1.1 can optionally run AD Admin as follows to re-enable Invoker's Right on existing PL/SQL packages:
Run adadmin > Compile/Reload Applications Database Entities menu >
Compile APPS schema.
Choose "No" at the following prompt:
Run Invoker Rights processing in incremental mode [No]
Apply below patches using adpatch
Patch 24498616:R12.AD.B
Patch 24319156:R12.TXK.B
Patch 25380324:R12.FND.B
Apply product specific patches using adpatch
ProductPatch Number
Oracle WorkflowPatch 24709902:R12.OWF.B
Oracle ScriptingPatch 23475123:R12.IES.B
Oracle General LedgerPatch 25140916:R12.GL.B
Oracle Installed BasePatch 25075128:R12.CSI.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
The installation of the patches does not enable Java Web Start. The Java Plug-in remains the default launch method for all application users.
Enabling JWS For Specific 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>:<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_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.