Java Web Start The New Way to Open Oracle Financials Form Applications

Java Web Start The New Way to Open Oracle Financials Form Applications 7 April, 2018

What is Java Web Start Java Web Start changes the way that Java Applet Forms runs on end-users desktops in order to open Oracle Financials form driven applications such as the General Ledger, Accounts Payable, Accounts Receivable, CAPS, CSMA, & Oracle Assets to name a few modules. Java Web Start architecture 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. Currently, Oracle Financials form applications rely on these soon to be deprecated Java Plug-in interfaces needed to open Oracle Forms. 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. 2

Java Web Start Will Resolve the Problem Below Oracle Financials E-Business Suite interacts with browsers through HTML web pages and Oracle Application Framework Forms pages, depending upon what the end user is trying to accomplish. Currently, forms are opened from the EBS Home page by a Java applet which is launched by the Java Plug-in using a browser that supports plug-ins via the NPAPI protocol (Netscape Plugin Application Programming Interface). Java Plug-in is being phased out. IE11 and Firefox ESR 52.x (& lower) are the only browsers left which support the existing JRE Plug-in. Some examples of the E-Business Suite HTML pages are the Home Page, HCOM iProcurement, PCARD, & Vendor Request. These pages will continue to work in modern browsers and are not impacted by this Java Plug-in deprecation and Java Web Start change. Firefox ESR 52.x will continue to allow the use of the NPAPI plug-in for Java through May 2018. Future releases of Firefox will not support NPAPI plug-in. 3

What is Changing with Java Web Start All common browsers will now work with the Oracle Financials applications. More choices for the users to use a preferred browser. Successfully Tested functionality on the following Browsers Internet Explorer 11 for Windows Microsoft Edge for Windows Google Chrome for Windows Firefox ESR 52 & beyond for Windows Safari for Windows Please Note: Safari on the Mac will continue to work with the Java Plug-in (Oracle is still working on a solution for the Mac) In most of the browsers Oracle Forms will open either seamlessly or with a one time single click or one extra click. Browser specific behavior is available in following slides. Drill down from Java Forms to HTML pages will appear somewhat different. Only one form session of Oracle Financials per Environment can be open at a time. 4

What is Changing HTML & Forms Independence With Java Web Start, Oracle gives you the flexibility to close the HTML Page and continue working in Oracle Forms whereas in today’s world Oracle Forms are closed as soon as you close the HTML Browser page. 5

What is Changing HTML & Forms Independence – contd. Close the Oracle Home Page Browser. 6

What is Changing HTML & Forms Independence – contd. You can still do tasks in Oracle Forms like Data Entry, Viewing Output/Log of Concurrent Requests etc. 7

What is Changing HTML & Forms Independence – contd. However you cannot navigate back to an Oracle HTML responsibility like iProcurement - an error message will be received as shown below. 8

What is Changing Elimination of Extra Browser Tabs After Java Web Start users will not see the extra Java browser tabs which are shown in the screenshots below. Firefox Example Internet Explorer Example 9

What is Changing Impact on Logout/Exit from Oracle In today’s world users just close the HTML homepage and that automatically closes the Java Forms session as well but that’s not going to happen after Java Web Start. This new independence has an impact and users will need to change the way they logout/exit from Oracle. Now to exit completely from Oracle properly, users will have to first close the Java Forms Window and then click Logout on the HTML Browser page. 10

What is Changing Impact on Logout/Exit from Oracle – contd. If a user clicks Logout on the HTML Browser page before closing the Java Forms, the Java Forms will remain open and an error will be received when you try to do anything on them. 11

What is Changing Concurrent Oracle Form Sessions per Environment Java Web Start has a limitation that it only allows 1 form session per Environment. A warning/confirmation message will be received if you try to open the 2nd form session as shown below. 12

What is Changing Concurrent Oracle Form Sessions per Environment – contd. If you click Yes, the current form session will close and you will have to click on the Function Link again to open the new Oracle Form session. If you click Cancel or No, the current form session will continue and the second session will not become active. 13

What is Changing No More Local JRE Update Message for Windows PC Users After Java Web Start, Windows PC users can continue working with a lower version of Local JRE (baseline of 1.8.0 141) even when the Oracle Server has a higher version of JRE (1.8.0 162 or higher) which means they will no longer see a message to update the JRE when accessing Oracle. Mac Users will continue to see this and will need to act accordingly. 14

What is Changing Windows vs Tabs (Only for Internet Explorer) With Java Web Start, the core of how Java events are handled has been changed and as a result, all the events which lead to opening up of a browser will now invoke a new browser window instead of opening a new tab in the existing browser session. E.g. after Java Web Start if you try to open a concurrent request output/log or try to navigate to a HTML only responsibility from Java Forms, it will open a new browser window instead of opening a new tab in the existing browser session. Before After 15

Browser Behavior – IE11 with Windows Seamless Auto Opening of Forms – JNLP Files are automatically linked to Java Web Start when JRE 8 update 141 or latest is installed. Desktops will already have the necessary file associations to make this work. These are found: 16

Browser Behavior – IE11 – contd. No additional Browser setting is required. No Extra Clicks to open Oracle Forms. Performance Checks Screen Navigation Data export Navigation HTML to Forms Navigation Forms to Forms Open Multiple Java Forms Viewing Request Output/Logs Viewing XML Publisher outputs – – – – – Normal Normal Normal – Normal Normal – Normal Normal 17

Browser Behavior – IE11 – contd. Navigation from Java Form to HTML and vice versa. There is an known issue with Internet Explorer which prevents users from going to an HTML responsibility like iProcurement from Java Forms. Users will receive the error message as shown in the screenshot below. However, we have resolved this issue! 18

Browser Behavior – IE11 – contd. Navigation from Java Form to HTML and vice versa. This issue does not impact opening of Output or Log files of concurrent requests. 19

Browser Behavior – IE11 – contd. Registry setting for fixing the navigation from Java Form to HTML and vice versa. Computer\HKEY CURRENT USER\Software\Microsoft\Internet Explorer\Main – set frame merging from 0 to 1 The HUIT Endpoint team will push this setting to users and their local portal manager to avoid Users from encountering this issue. The setting depiction is seen below. 20

Browser Behavior – IE11 – contd. 21

Browser Behavior – Microsoft Edge with Windows 2 Additional Clicks required every time - JNLP Files will be downloaded when you click on any Java Form link in Oracle and then the downloaded JNLP file needs to be clicked once again to launch Java Forms. No additional Browser setting is required Recommended to not click Save in the illustration below (Click Open) 22

Browser Behavior – Microsoft Edge – contd. Performance Checks Screen Navigation Data export Navigation HTML & Forms Navigation Forms to Forms Open Multiple Java Forms Viewing Request Output/Logs Viewing XML Publisher outputs – – – – – Normal Normal Normal – Normal Normal – Normal Normal 23

Browser Behavior – Chrome with Windows 2 Additional Clicks required every time - JNLP Files will be downloaded when you click on any Java Form link in Oracle and then the downloaded JNLP file needs to be clicked once again to launch Java Forms. No additional Browser setting is required Performance Checks Screen Navigation – Data export – Navigation HTML & Forms – Navigation Forms to Forms – Open Multiple Java Forms – Viewing Request Output/Logs – Viewing XML Publisher outputs Normal Normal Normal Normal Normal Normal – Normal 24

Browser Behavior – Firefox (ESR Release) with Windows 1 Additional Click required only for the first time for the JNLP file. After that Java Forms open without any additional clicks. Please be aware that marking the second box below could introduce a security vulnerability to the desktop. Recommended to not click Save. 25

Browser Behavior – Firefox (ESR Release) – contd. Launching Oracle Forms in Firefox ESR 52 or above leaves an orphan browser tab open. - This issue is a result of web browser limitations and can be resolved by setting (dom.allow scripts to close windows) preference to true. - This work-around seems to work for most of us but not for all of us. So, you may encounter this even after changing the setting. - You can safely close the Orphan Tab if you want. - The HUIT Endpoint team will push this setting to users. 26

Browser Behavior – Firefox (ESR Release) – contd. Performance Checks Screen Navigation – Data export – Navigation HTML & Forms – Navigation Forms to Forms – Open Multiple Java Forms – Viewing Request Output/Logs – Viewing XML Publisher outputs Normal Normal Normal Normal Normal Normal – Normal 27

Browser Behavior – Safari with Windows 1 Additional Click required every time – A popup will be displayed when you click on any Java Form link in Oracle asking to Open or Save the JNLP file. Click Open. It is not recommended to click Save. Safari needs to be set as the Default Browser for it to work properly with Oracle. Performance Checks Screen Navigation – Data export – Navigation HTML & Forms – Navigation Forms to Forms – Open Multiple Java Forms – Viewing Request Output/Logs – Viewing XML Publisher outputs Normal Normal Normal Normal Normal Normal – Normal 28

Browser Behavior – Safari with Mac Mac will continue to function as it does today in Production i.e. using the plug-in process Oracle does not yet support using Java Web Start on a Mac and is continuing to work on a solution. The main browsers currently used on a Mac are Safari and Firefox. If you have a Mac and need to open forms, the best browser to use will be Safari. FireFox works today but will no longer be an option come end of May, as Firefox will no longer support JRE plug-ins. Please Note: As stated in our Desktop standards that Oracle Financials is not fully supported on a Mac and should mostly be used for HCOM/iProcurement and other HTML page drive modules. If a Mac user is encountering issues opening Oracle Forms, they may need their local desktop support to install the latest version of Java JRE. The next supported version to use is JRE 1.8.0 162. 29

Browser Behavior Summary Browser Auto-Open Auto-Open Details Known Issues In some cases users may encounter an issue where IE prompts to Login again when navigating from Oracle Forms to HTML pages. IE 11 Yes Automatic linking to JNLP with JWS through JRE8 update 141 or later Edge No 2 extra clicks required every time None Firefox ESR 52 Yes 1 extra click required only once when opening forms for the first time Orphan Browser Tab when launching Oracle Forms Google Chrome No 2 extra clicks required every time None Safari for Windows No 1 extra click required every time Safari needs to be set as Default Browser to make Oracle work properly. Safari for Mac N.A. Oracle on Mac uses plugin mode instead of JWS None If you have questions, please do not hesitate to contact the HUIT Service Desk at 5-7777. 30

User Experience Impact and Reported Issues Java Web start has limitation that only one form session per Environment can be open at a time. - We will have to wait until Oracle releases a fix for this Java Web start does not work on Mac. JRE plugin is used by Oracle on Mac - We will have to wait until Oracle releases a fix for this Other list of known issues include performance, session logouts, what if someone closes the browser, how does the interaction between browser and Forms work. - No Issues faced in Performance & No unexpected session logouts encountered. - In most of the cases, the interaction between browser and form is seamless. What happens if users signs out from HTML screen and FORM session is open or otherwise - Sign-Out functionality is tested and found to be working as expected. Oracle OATS needs to upgraded to version 13.1 in order to work with Java Web Start - Completed In some cases users may encounter an issue where IE prompts to Login again when navigating from Oracle Forms to HTML pages. - A registry setting needs to be changed to fix this 31

. Known Issues Only Different Java Applets May Run Simultaneously - We will have to wait until Oracle releases a fix for this Single Forms Session Allowed per Oracle E-Business Suite Environment - We will have to wait until Oracle releases a fix for this Java Console Showing java.security.KeyStoreException: WIExplorerMy not found. - 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. Internet Explorer: Launching Java Applet Intermittent Fails Due to “frmservlet.jnlp might have been moved or deleted” - This is a very intermittent issue and was not encountered during testing Directly Opening the Forms Application Leaves a Blank Browser Window Open - This occurs when directly accessing the Forms application which is not enabled at Harvard. Also this is the expected behavior and it is safe to close the browser window after launching the Forms application. Forms Socket Mode is Not Supported with Java Web Start - Harvard use Oracle Forms in Default Mode i.e. Servlet Mode and not in Socket Mode Browser Tab Does Not Close After Uploading a File Attachment - This issue impacts Firefox and Chrome and is a result of web browser limitations - There is a work-around available for Firefox (dom.allow scripts to close windows) preference to true. This workaround seems to work for most of the people but not for all. Financial Dimension Hierarchy Manager Does Not Launch Using Java Web Start on Oracle EBusiness Suite Release 12.1.3 - Financial Dimension Hierarchy Manager is not used at Harvard 32

Known Issues – Contd. Issues Closing HTML Pages After Opening From Forms Application - This issue 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. Buildup of JNLP files in the Browser's Download Folder - A buildup of JNLP files on the local file system only occur if the end user does not launch the downloaded JNLP files or hits save. These can be safely deleted. JNLP files are time sensitive and the session information in it gets expired after timeout. Product-specific Java Applets Supporting Only the Java Plug-in - This issue effects Oracle Call Center Technology & Oracle Demand Planning. Both of these are not used at Harvard 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 : “FAILED: file afgstusr.sql on worker 1 for product fnd username APPLSYS.” - Patch 25475909 will be needed to fix this issue 33

Known Issues – Contd. Oracle Discoverer Not Certified For Use With Java Web Start - Oracle Discoverer is not used at Harvard Unable to Launch Forms Application or Java applets using Java Web Start on Windows 10 Creators Update via Internet Explorer 11 - This issue only occurs when both 32 Bit and 64 Bit JRE’s are installed in the system. 64 Bit JRE needs to be uninstalled for Oracle to work properly. JNLP files in the Firefox's Download History - In Firefox, end users will see a list of JNLP files which are downloaded to run the Oracle Applications. Although the actual JNLP file gets deleted as soon as the session is closed, but the download list is not cleared automatically. Users are advised to regularly clear the Firefox download list. 34

Rollout Plans Share documents with IT Support with browser behavior and hopefully push some settings Establish a communication plan for the change management process. Engage user community, identify all user experience changes, share & publish training docs, flyers, documents Rollout plan will be for all users 35

Java Web Start Reference documents Using Java Web Start with Oracle E-Business Suite (Doc ID 2188898.1) https://blogs.oracle.com/stevenchan/e-business-suite-and-java-web-start:-frequently-askedquestions SR 3-15915730241 : Add Harvard CSI# 1206767 to Enhancement request 25993693 SR 3-16836411901 : Raised to get a fix for Internet Explorer Issue. - Oracle provided the fix for this IE issue. SR 3-17034714268 : Raised to find out whether code signing is required for JWS - As per Oracle we should continue code signing the JAR files just like today. Google Drive Folder for FINDINI Java Web Start https://drive.google.com/drive/u/0/folders/1s5q3cPRqSGNVjDl6duP8ArchnfjPk1N1 36