bonus java web start with oracle e-business suite r 12.2.6 ed2
TRANSCRIPT
Using Java Web Start
Oracle E-Business Suite R 12.2.6
[Edition 10]
[Last Update 191011]
For any issues/help contact :[email protected]
1 Introduction................................................................................................................................................... 3
2 Documentation ............................................................................................................................................. 4 2.1 Oracle Documentation ........................................................................................................................................ 4
3 REQUIREMENTS ............................................................................................................................................ 6 3.1 Hardware Requirements.................................................................................................................................... 6 3.2 Software Requirements ...................................................................................................................................... 6 3.3 Minimum Prerequisites...................................................................................................................................... 7
4 Checking JAVA Version in EBS R12.2.X ................................................................................................... 9
5 Required Application Technology Patches for Oracle E-Business Suite Release 12 .............. 10
6 Product-Specific Patches for Oracle E-Business Suite Release 12.2 ........................................... 11
7 Applying Product & Application Technology Patches for Oracle E-Business Suite Release 12.2....................................................................................................................................................................... 12
7.1 Apply patch 25441839 (Merge Request On Top Of 10.1.2.3.2PSU) ...................................................... 12 7.2 Apply the required Oracle E-Business Suite application technology patches (AD/TXK/FND) .... 15 7.3 Applying Product-Specific Patches for Oracle E-Business Suite Release 12.2 .................................. 15 7.4 Generate the JAR File......................................................................................................................................... 19 7.5 Complete the online patch cycle .................................................................................................................... 20 7.6 Perform a cleanup of the online patch cycle ............................................................................................... 21 7.7 Synchronize the patch file system with the new run file system. ......................................................... 21
8 Required Patches for Supporting Firefox ESR on macOS Using Java Web Start ...................... 22 8.1 Applying Required Patches for Supporting Firefox ESR on macOS Using Java Web Start ............. 22
9 Configuring and Enabling Java Web Start ........................................................................................... 24 9.1 Set Java Web Start as the default for all application users ..................................................................... 24
10 Mozilla Firefox Extended Support Release (ESR) ......................................................................... 34 10.1 Disable Firefox update on Mac.................................................................................................................... 34 10.2 Default behavior ............................................................................................................................................. 35 10.3 JNLP Files in the Browser's Download Folder are not Automatically Removed Using Firefox ESR on macOS ................................................................................................................................................................. 38
11 Troubleshooting .................................................................................................................................... 40 11.1 Unable to Expand Responsibility ............................................................................................................... 40 11.2 R12 E-Business Suite Java Web Start Fails To Launch Forms With "Oracle Corporation Oracle Forms Java Webstart Oracle Forms Applet"........................................................................................................... 42 11.3 Opatch fails with Lock file error ................................................................................................................. 44 11.4 R12 E-Business Suite Applications Technology Stack Command 'make -f ins_forms.mk sharedlib install' Fails With '/usr/bin/ld: Cannot Find -lhpi collect2: ld returned 1 exit status make: *** [frmbld] Error 1 ' ..................................................................................................................................................... 45
1 INTRODUCTION
This guide is activity guide on how to use Java Web Start with Oracle E-Business Suite Releases 12.2.X
2 DOCUMENTATION
2.1 Oracle Documentation
1. https://blogs.oracle.com/stevenchan/java-web-start-now-available-for-ebs-121-and-122
2. https://blogs.oracle.com/stevenchan/safari-12-implications-for-e-business-suite-users
3. R12 E-Business Suite Applications Technology Stack Forms Issues With Apple Mac OS
(OS X) Desktops After Upgrading To Safari 12, Chrome, Or Firefox (Doc ID 2452227.1)
4. Oracle E-Business Suite Release Notes Release 12 for macOS (Doc ID 1533334.1)
5. Using Java Web Start with Oracle E-Business Suite (Doc ID 2188898.1)
6. Recommended Browsers for Oracle E-Business Suite Release 12 (Doc ID 389422.1)
7. Firefox Quantum ESR 60 Certified with EBS 12.1 and 12.2 for macOS High Sierra 10.13
8. Applying OracleAS 10g Forms and Reports Patches to Oracle E-Business Suite
Release 12. (Doc ID 805965.1)
9. Migrate to Java Web Start from Java Plug-In Now
https://blogs.oracle.com/stevenchan/migrate-to-java-web-start-from-java-plug-in-now
10. Applying any overlay Patch Over a Cumulative Patch returns the Error 'OPatch cannot
process overlay patches because of no OUI support' (Doc ID 1083935.1)
11. R12 E-Business Suite Applications Technology Stack Command 'make -f ins_forms.mk
sharedlib install' Fails With '/usr/bin/ld: Cannot Find -lhpi collect2: ld returned 1 exit
status make: *** [frmbld] Error 1 ' (Doc ID 1529324.1)
12. Opatch fails with Lock file error (Doc ID 257800.1)
13. R12 E-Business Suite Java Web Start Fails To Launch Forms With "Oracle Corporation
Oracle Forms Java Webstart Oracle Forms Applet" (Doc ID 2291861.1)
14. Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release
12 (Doc ID 393931.1
Note: Oracle E-Business Suite Release 12 is not certified with browsers on macOS other than those listed above. Safari 12 is not certified with E-Business Suite Release 12 due to the removal of support for NPAPI plugins in the browser which is required for use with Oracle Forms and the Java plug-in.
3 REQUIREMENTS
To achieve optimal performance, you must have adequate CPU power and memory on the macOS client. Oracle recommends the following configuration settings.
3.1 Hardware Requirements
The macOS client must have 800 x 600 minimum display resolution (1024 x 768 or higher is preferred). For a complete description of macOS requirements (including processor, RAM, and disk requirements), review Apple's informational web page at
https://www.apple.com/macos/how-to-upgrade/
3.2 Software Requirements
The following desktop software is required:
1. OS X El Capitan 10.11:
• OS X El Capitan version 10.11.6 or higher
• Safari 11 (11.0.2 or higher)
• Java Plug-in (version 1.8.0_91 or higher)
2. macOS Sierra 10.12:
• macOS Sierra version 10.12.6 or higher • Safari 11 (11.0.2 or higher) • Java Plug-in (version 1.8.0_121 or higher)
3. macOS High Sierra 10.13:
• macOS High Sierra version 10.13.3 or higher • Safari 11 (11.0.3 or higher) using Java Plug-in or Firefox ESR 60.x using Java Web
Start (JWS) • JRE 8 Update 171 (version 1.8.0_171) or higher
4. macOS Mojave 10.14:
• macOS Mojave version 10.14.1 or higher • Firefox ESR 60.x & 68.x using Java Web Start (JWS) • JRE 8 Update 191 (version 1.8.0_171) or higher
3.3 Minimum Prerequisites
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.X
• R12.AD.C.Delta.8
• R12.TXK.C.Delta.8
• R12.ATG_PF.C.Delta.6
1.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.
2. Minimum JRE Required
4 CHECKING JAVA VERSION IN EBS R12.2.X
1. Go under the Application context_file
vi $CONTEXT_FILE
2. Search For JRE and copy the location
3. Go under the JRE Location and under bin check java version by using below command
5 REQUIRED APPLICATION TECHNOLOGY PATCHES FOR ORACLE E-BUSINESS SUITE RELEASE 12
The following table lists all required application technology patches.
The following table lists the required application technology patches for Oracle E-Business Suite Release 12.2:
6 PRODUCT-SPECIFIC PATCHES FOR ORACLE E-BUSINESS SUITE RELEASE 12.2
The following product-specific patches are required for the following Oracle E-Business Suite Release 12.2 products which use Java applets:
7 APPLYING PRODUCT & APPLICATION TECHNOLOGY PATCHES FOR 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.
$ adop phase=prepare
patch
7.1 Apply patch 25441839 (Merge
Request On Top Of
10.1.2.3.2PSU)
1. unzip p25441839_101232_LINUX.zip
2. cd 25441839
3. $ORACLE_HOME/OPatch/opatch apply
Note: Make sure you fulfill the readme pre-requiste before applying the patch
7.2 Apply the required Oracle E-
Business Suite application
technology patches
(AD/TXK/FND)
1. Apply patch 24498616,25449925,25380324
$ adop phase=apply patches=24498616,25449925,25380324 merge=yes
7.3 Applying Product-Specific
Patches for Oracle E-
Business Suite Release 12.2
1. Apply Patch 28713780
adop phase=apply patches= 28713780
1. Apply Patch 23475123
adop phase=apply patches= 23475123
2. Apply Patch 23280764
adop phase=apply patches= 23280764
3. Apply Patch 23645622
adop phase=apply patches= 23645622
4. Apply Patch 23575933
adop phase=apply patches= 23575933
5. Apply Patch 22221603
adop phase=apply patches= 22221603
9.Apply Patch 24833534
adop phase=apply patches= 24833534
7.4 Generate the JAR File
1. 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.5 Complete the online patch
cycle
$ adop phase=finalize,cutover
$ source <EBS_ROOT>/EBSapps.env run
7.6 Perform a cleanup of the
online patch cycle
$ adop phase=cleanup
7.7 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.
8 REQUIRED PATCHES FOR SUPPORTING FIREFOX ESR ON MACOS USING JAVA WEB START
The following table lists the required application technology patches for Oracle E-Business Suite Release 12.2:
8.1 Applying Required Patches
for Supporting Firefox ESR
on macOS Using Java Web
Start
1. Apply Patch 28700057
adop phase=apply patches= 28700057
9 CONFIGURING AND 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
Note: We are going with option 1: Set Java Web Start as the default for all application users
9.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. Access EBS URL: http://ebiznis.gh.pri:8000/OA_HTML/AppsLogin 2. Enter the following:
a) Username: sysadmin b) Password: sysadmin c) Click on Login button
3. Expand System Administrator responsibility and then Oracle Application Manager and then click on AutoConfig
4. Click the Edit Parameter button for the application tier context file to access the Context File Parameters page
6. Change the value of OA_VAR for s_forms_launch_method from browser to jws.
Should look like this
1. Click Save at the bottom of the page.
2. Click OK
3. Click OK
4. Stop all application tier services.
. APPSVIS_ip-10-0-20-192.env
cd $ADMIN_SCRIPTS_HOME
./adstpall.sh apps/apps
5. Run AutoConfig on the application tier.
./adautocfg.sh
When prompted for APPS user password: apps
Completing these steps sets Java Web Start as the default launch method for the environment. In step 11, AutoConfig updates the two profile options at the site level accordingly:
Profile Option / Internal Code
Value at the Site Level
Enable Java Web Start / FND_ENABLE_JAVA_WEB_START
Yes
ICX: Forms Launcher / ICX_FORMS_LAUNCHER
<s_webentryurlprotocol>://<s_webentryhost>.<s_webentrydomain>:<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.
10 MOZILLA FIREFOX EXTENDED SUPPORT RELEASE (ESR)
Note: Firefox ESR 60.x and Firefox ESR 68.x support Java Web Start for launching the Forms application and regular Java applets as part of Oracle E-Business Suite
10.1 Disable Firefox update on
Mac
1. Open firefox application and then click this button in the upper-right corner, then choose Preferences
2. Select “General” on the left pane. 3. Scroll down to the “Firefox Updates” section and choose either Check for updates,
but let me choose whether to install them or Never check for updates
10.2 Default behavior
By default, Firefox 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 Mozilla Firefox. 2. Log in to Oracle E-Business Suite. 3. Choose a responsibility (for example, System Administrator). 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.
By doing this once, launching Java content with Java Web Start provides a comparable user experience to that seen with the Java Plug-in. Future instances of the Forms application or a Java applet will now launch using Java Web Start.
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 (macOS only): For more information, see 7.3 JNLP files in the Browser's Download Folder are not automatically removed using Firefox ESR on macOS.
10.3 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 executed 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 down
11 TROUBLESHOOTING
11.1 Unable to Expand
Responsibility
Issue: Unable to expand responsibility after login to EBS page
Cause: Browser cache issue
Fix: After clearing the Browser Cache, we were able to expand responsibilities. 1. Open Firefox Browser
2. Click on top right corner and then click on Options
Now you should be able to expand responsibility
11.2 R12 E-Business Suite Java
Web Start Fails To Launch
Forms With "Oracle
Corporation Oracle Forms
Java Webstart Oracle Forms
Applet"
Error: When launching forms after enabling Java Web Start, a white page is received with the following message:
"Oracle Corporation Oracle Forms Java Webstart Oracle Forms Applet"
The JWS frmservlet.jnlp file does not download either
Reason: Patch 25441839 was missed / not applied when following the below document: Note 2188898.1 - Using Java Web Start with Oracle E-Business Suite (Doc ID 2188898.1) SOLUTION To resolve the issue test the following steps in a development instance and then migrate accordingly: 1. Download and apply Patch 25441839 along with any required prerequisite patches via OPatch. 2. Confirm patch is applied with the following command: >opatch lsinventory | grep 25441839
3. Run adop phase=fs_clone, as this step ensures the Oracle Forms 10g overlay Patch 25441839 is propagated to the new patch file system. 4. Launch Forms with Java Web Start and ensure the Form now opens correctly.
11.3 Opatch fails with Lock file
error
Issue Encountered: “Problems with the lock fileLock file exists, details are:
Interim Patch 18620223 is holding the lock from this patch 17653437,
probably due to previous unsuccessful operation
ERROR: OPatch failed during prerequisite check.”
Reason:
When Opatch is invoked, it creates patch_locked file in $ORACLE_HOME/.patch_storage during its execution.
If the patch application is interrupted or cancelled, this file gets retained under /.patch_storage directory. Hence, On an an attempt to re-apply the patch, the presence of patch_locked file doesn't allow further processing and throw error.
Solution:
1. Check if the file "patch_locked" is present in the directory
$ORACLE_HOME/.patch_storage
2. If present, rename, move or remove the patch_locked file from
$ORACLE_HOME/.patch_storage
3. Re-apply the patch
11.4 R12 E-Business Suite
Applications Technology
Stack Command 'make -f
ins_forms.mk sharedlib
install' Fails With '/usr/bin/ld:
Cannot Find -lhpi collect2: ld
returned 1 exit status make:
*** [frmbld] Error 1 '
Issue Encountered:
“OPatch found the word "error" in stderr, please look into it.
You may have to run the make again.
Stderr Output (from /u01/oracle/PROD/fs1/EBSapps/10.1.2/.patch_storage/18620223/make_local.stderr):
/usr/bin/ld: cannot find -lhpi
collect2: error: ld returned 1 exit status
Make * [frmbld] Error 1”
While apply the patch using opatch
Reason:
It is documented unpublished defect 14665319
SOLUTION
1. Download and apply Patch 17653437.
2. Relink the forms binaries:
cd $ORACLE_HOME/forms/lib
make -f ins_forms.mk sharedlib install
3. Re-apply the patch using opatch