Sunday, July 11, 2021

Java Web Start with Oracle E-Business Suite

 Java Web Start with Oracle E-Business Suite 

(Doc ID 2188898.1)


About Java Web Start

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:



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.


Steps to follow to implement JWS

  • adop phase=prepare 
  • EBSenv patch
  • cd $PATCH_TOP/25441839
  • opatch apply
    • Opatch succeeded
  • adop phase=apply patches=24498616,25449925,25380324 merge=yes (!! 25380324 _D)
    • adop exiting with status = 0 (Success)
  • adop phase=apply patches=23645622,23645622_D:u23645622.drv
    • adop exiting with status = 0 (Success)
  • "adop phase=apply patches=28700057,29058008,29058008_D:u29058008.drv,29024389,29024389_D:u29024389.drv
    • adop exiting with status = 0 (Success)
  • 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
  • adop phase=finalize,cutover 
    • adop exiting with status = 0 (Success)
  • EBSenv run
  • adop phase=cleanup 
    • adop exiting with status = 0 (Success)
  • adop phase=fs_clone 
    • adop exiting with status = 0 (Success)

Context File Variable

VariableDescriptionDefault Value
s_forms_launch_method

Enable Java Web Start or Java Plug-in.

Possible values:

  • browser - use Java Plug-in
  • jws - use Java Web Start
browser

Profile Options

Profile Option / Internal CodeDescriptionDefault Value
Enable Java Web Start / FND_ENABLE_JAVA_WEB_START

Use Java Web Start to launch the Forms application and Java applets.

Possible values:

  • Yes - Use Java Web Start
  • No - Use Java Plug-in
No
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>/forms/frmservlet
  • Java Plug-in: <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
<s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_webport>/forms/frmservlet

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.


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.


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.
    1. Using the System Administration responsibility, run AutoConfig through the Oracle Applications Manager interface.
    2. Click the Edit Parameters icon for the application tier context file.
    3. Click the System tab.
    4. Expand the oa_system_config node.
    5. Change the value of OA_VAR for s_forms_launch_method from browser to jws.
    6. 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 CodeValue at the Site Level
Enable Java Web Start / FND_ENABLE_JAVA_WEB_STARTYes
ICX: Forms Launcher / ICX_FORMS_LAUNCHER<s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<s_active_webport>/forms/frmservlet
Posted by at
Labels:

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)