| Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i (文档 ID 290807.1) |  转到底部 |  |
| In This Document
This document covers the procedure to upgrade the version of the JRE Native Client in Oracle E-Business Suite 11i. The most current version of this document can be obtained in Document 290807.1. There is a change log at the end of this document. EBS 11i is in sustaining support. P1 patch fixes and CPU's may still be provided for customers registered in the Advanced Customer Support (ACS) as outlined in Document 1596629.1. Latest JRE Production Releases Java Deployment Technology (JRE 6 and 7 Users) The Java deployment technology component has been removed from JRE 6 & 7 starting with the October 2017 releases JRE 1.6.0_171 and JRE 1.7.0_161. While the removal of this component means these releases and higher can no longer be used to initially launch Java they can still run it. Using these releases now requires JRE 8 to also be installed on the desktop to initially launch Java before the earlier release is used to run the Java content. For details on how to implement this see Java Plug-in Coexistance on a Desktop Client. The latest production releases for each Java family certified with Oracle E-Business Suite are listed below. Note: Oracle strongly recommends that Oracle E-Business Suite customers move to the latest and therefore most secure CPU public build version of the JRE Native Plug-in available for any certified Java family (JRE 7 or 8) as listed below. JRE 8 The JRE 8 stream is the latest Java desktop release certified for running Java content within Oracle E-Business Suite. JRE 1.8.0_261 (8u261) CPU (Recommended) Oracle recommends that Oracle E-Business Suite users run this latest and most secure Crtical Patch Update (CPU) JRE release. JRE 7 The JRE 7 stream has reached 'End of Life and is no longer available through the public download sites. Oracle E-Business Suite users can continue to run JRE 7 during the extended support period of their EBS release. For further information see Java SE 7 End of Public Updates Notice. JRE 1.7.0_271 (7u271) CPU This latest standard JRE 7 CPU release is available in a patch from My Oracle Support which is listed in the JRE Parameter Settings table. Note: Users wanting to run Java content using JRE 1.7.0_271 must also have JRE8 installed on their desktop to initially launch Java.For seamless operation it is recommended to install JRE 1.8.0_261 or later of which JRE 1.7.0_271 is a security baseline. See Java Plug-in Coexistance on a Desktop Client for further information JRE 6 The October 2018 CPU (JRE 1.6.0_211) was the final release on the Java 6 stream. Users that are still using JRE 6 are strongly recommended to upgrade to JRE 7 or JRE 8 in order to uptake the latest CPU release. Section 1. OverviewThe Oracle E-Business Suite 11i has two interfaces: a web-based model for modules like iProcurement and iStore, and an Oracle Forms-based model for our professional services modules like Oracle Financials. This document will explain the steps needed to upgrade to the latest certified version of JRE Native Client for supporting forms-based modules used with Oracle E-Business Suite 11i. It is important that you read and follow this document in its entirety before starting an upgrade or applying any patch. Unraveling Java TerminologyA wide range of products are available for the Java platform. Many of these product names sound similar, and are sometimes even used interchangeably in Sun's own documentation. For more information on Java terminology see the Unraveling Java Terminology webpage. JRE 6 family refers to JRE 1.6.x. JRE 7 family refers to JRE 1.7.x. To access Oracle Forms-based content in the Oracle E-Business Suite, end-users require the "Sun Java2 Standard Edition Java Runtime Engine". In this documentation, this is referred to as "JRE", since it is the runtime component required for end-user desktop clients. For historical reasons, certain parts of this documentation, particularly the installation scripts, may refer to "J2SE". You should interpret these references to be equivalent to "Sun Java2 Standard Edition Java Runtime Engine" or "JRE". Client JRE and Server JDK CompatibilityJRE releases 6, 7, and 8 on the client tier are all compatible with any certified JDK 6 or JDK 7 release running on the application tier. Certification MatricesFor further information on browsers see Document 285218.1 entitled 'Recommended Browsers for Oracle E-Business Suite 11i'.Certification Matrix for JRE Plug-in (64-bit) ReleasesThis table outlines the currently certified 64-bit Browser, Windows Desktop Client Operating System and minimum 64-bit JRE Plug-in versions.
1 Internet Explorer 11 is only certified running Desktop Mode on Windows 8 and higher. The Metro version does not support Java and is not certified for Oracle E-Business Suite. 2 Microsoft Office: Microsoft Office (64-bit) is NOT certified with Oracle E-Business Suite 11i. Continue to run the Microsoft Office (32-bit) version with the 64-bit browser. 3 Windows 7: Microsoft ended support of Windows 7 on 14th January 2020. If you are running this desktop operating system see 3rd Party Software Support Lifecycle 4 Windows 10: See Microsoft Windows 10 Servicing Options For further information regarding the 64-bit stack see Appendix A: Information for JRE 64-bit Users within this document. Certification Matrix for JRE Plug-in (32-bit) ReleasesThe 32-bit JRE Plug-in can run on both the 32-bit and 64-bit (using the 32-bit home) releases of the Windows Operating System This table outlines the currently certified Windows Desktop Client Operating System, 32-bit Browser and minimum 32-bit JRE Plug-in versions.
1 Internet Explorer 11 is only certified running Desktop Mode on Windows 8 and higher. The Metro version does not support Java and is not certified for Oracle E-Business Suite 2 Windows Vista: Microsoft ended support of Vista on the 11th April 2017. If you are running this desktop operating system see 3rd Party Software Support Lifecycle 3 Windows 7: Microsoft ended support of Windows 7 on the 14th January 2020. If you are running this desktop operating system see 3rd Party Software Support Lifecycle 4 Windows 10: See Microsoft Windows 10 Servicing Options Certification Notes Compatibility with Higher JRE releases Oracle E-Business Suite end-users may run or upgrade to higher production releases of the JRE Plug-in on any JRE family certified with Oracle E-Business Suite at their discretion. Oracle will continue to test and certify the Oracle E-Business Suite with future versions of any JRE family certified with Oracle E-Business Suite in advance of their general availability to the public. Any known compatibility issues or workarounds will be updated within this document as required. All current production versions equal to or higher than the minimum versions stated in the 'Certification Matrices' tables above are compatible with Oracle E-Business Suite 11i.
3rd Party Software Support Lifecycle Oracle's support of the various third party client operating system, service pack levels and browsers aligns with the respective vendor's support life cycle. It is recommended that users running software versions that are no longer supported by the vendor upgrade to the current release. Oracle will continue to offer support for earlier versions with Oracle E-Business Suite R12 on a 'Best Effort' basis only. Consequently, where issues are due to problems with the old release, we may, where necessary, require customers to upgrade to resolve the issue. Internet Explorer, Windows desktop operating system and service pack requirements are available from Microsoft.
Microsoft Windows 10 Servicing Options
Oracle E-Business Suite is certified with all these Windows 10 service options. Minimum Patch Requirements JRE 8 Minimum Patch RequirementsThe JRE 8 desktop Plug-in is certified for the following Windows desktop releases:
The JRE 8 desktop Plug-in is certified for Oracle E-Business Suite 11i with the following minimum patch requirements: If you have previously applied the JRE 7 Minimum Patch Requirements there are currently no additional patch requirements needed to run JRE 8. Discoverer Users See Discoverer with JRE 1.8 for further information. JRE 7 Minimum Patch RequirementsThe JRE 7 desktop Plug-in has the following minimum patch requirements for Oracle E-Business Suite 11i: Windows Vista SP2, Windows 7 SP1 (32-bit & 64-bit), Windows 8 (32-bit & 64-bit) and Windows 10 (32-bit and 64-bit)
JRE 6 Minimum Patch RequirementsThe JRE 6 desktop Plug-in is certified for Oracle E-Business Suite 11i with the following minimum patch requirements: Windows Vista Desktop Clients
Windows 7 Desktop Clients (32-bit and 64-bit), Windows 8 (32-bit and 64-bit)
Note: New fixes are no longer provided on top of Oracle Developer 6i Patch 18 (6.0.8.27.x). Users must upgrade to PS19 (6.0.8.28.x) and uptake any new or existing fixes for developer 6i. PS19 (6.0.8.28.x) is also now a minimum requirement for JRE upgrades. Also, see Section 5. Known Issues for any further requirements or limitations that may be applicable. Section 2. Pre-Upgrade StepsStep 1. Source the Environment On the Application tier as the file system owner source your APPS env file. Step 2. Download and Apply the Prerequisite and Interoperability Patches (If Required) Note: Historically, the JRE upgrade scripts (txkSetPlugin.*) have been designed to work with JRE plugin versions of up to 2 digits e.g. JRE 1.6.0_07 (JRE 6u7), JRE 1.7.0_85 (JRE 7u85) etc. Step 2.1. Apply the JRE Interoperability Patch (If Required) Note: If you want to change the default JRE Plug-in version you are currently using and have previously applied the interop patch on your environment, there is no need to apply it again. Skip this step and continue to Section 3. Upgrade & Configuration and run the JRE Upgrade Script. To install up to a 3 digit Java release on your web server (e.g. 1.6.0_101) or simply to uptake the latest upgrade scripts, apply interoperability Patch 21624253. If not applied previously, apply the old interoperability Patch 6863618 as a pre-requisite to Patch 21624253. Step 2.2. Download the JRE Plug-in JRE uses a 'Non-Static Versioning' model, meaning, for Internet Explorer users, the version installed here denotes the minimum version that will be used to access Oracle E-Business Suite. (Historically when running a 'Static Versioning' model the version installed would denote the specific version that would have to be used to access Oracle E-Business Suite from the desktop client.) For further information including the behavior when using 'next-generation Java Plug-in technology' (JRE 1.6.0_10 and higher) see, Appendix B: Static vs Non-Static Versioning and Set Up Options Note: Only one version of the JRE plug-in can be installed for download through Oracle E-Business Suite. This can be either a 32-bit or a 64-bit version as required. Download the latest "JRE" update (Do not download the "Server JRE" version) from the Java SE Downloads page or as a patch from My Oracle Support as listed in the JRE Parameter Settings table.
If an earlier version of the JRE Plug-in is required, it can be downloaded from the Oracle Java Archive site or as a patch from My Oracle Support as listed in the JRE Parameter Settings table.
Step 2.3. Rename the JRE Plug-in Note: As there is no immediate requirement for all users to uptake the new JRE Plug-in upgrade scripts through Patch 21624253, the required commands for both the latest version of the scripts as well as the original versions from Patch 6863618 are included . Use the appropriate section as applicable to your patch level for the following step. The I Am Using the Latest Scripts from Patch 21624253 The latest scripts have the following version numbers:
Rename the downloaded JRE Native Plug-in file to The For example:
Continue to Step 2.4. Place the Renamed JRE Plug-in on the Web Application Tier I Am Using the Original Scripts from Patch 6863618 The original scripts have the following version numbers:
Rename the downloaded JRE Native Plug-in file to The For example:
Continue to Step 2.4. Place the Renamed JRE Plug-in on the Web Application Tier Step 2.4. Place the Renamed JRE Plug-in on the Web Application Tier Move the
Section 3. Upgrade & ConfigurationTo upgrade the JRE Plugin run the txkSetPlugin upgrade script following the instructions as applicable to your operating system.
Step 3.1. Run the JRE Upgrade Script (Unix Users Only) Run the The script will prompt you for the following values, if it does not find them automatically:
The
Where: Latest Script Requiring a 6 Digit <jversion> Value using JRE 1.8.0_51 as an Example:
Original Script Requiring a 5 Digit <jversion> Value using JRE 1.8.0_51 as an Example:
Step 3.2. Run the txkSetPlugin.cmd Script (Windows Users Only) Run the The
Where:
Latest Script Requiring a 6 digit <jversion> Version with JRE 1.8.0_51 as an Example:
Original Script Requiring a 5 digit <jversion> Value with JRE 1.8.0_51 as an Example:
Section 4: Post-Installation StepsStep 4. Verify your upgrade Once the JRE Plug-in has been installed on your client, follow these steps to verify that you have successfully upgraded JRE. Step 4.1. Enable Java Console Enable the Java Console on your desktop client through the 'Java Control Panel' by setting:
Step 4.2. Close Browser Windows Close all browser windows. Wait a minute or so after the windows are closed until the processes have finished saving their data to disk. Step 4.3. Sign into Oracle E-Business Suite Sign into Oracle E-Business Suite, and choose a Forms-based (Professional user interface) responsibility. For information on requirements and possible issues when trying to connect to a new or freshly upgraded Oracle E-Business Suite environment see Accessing Oracle E-Business Suite from a Desktop Client in the Appendices section. Step 4.4. Check the Console Window The Java Console should appear and display lines describing the JRE version being used. Examples: JRE 6 32-bit Version
JRE 7 32-bit Version
JRE 8 64-bit Version
Note: If a higher version of JRE than the one just installed is shown, it may be because a higher version has previously been installed on the desktop. You can check the versions installed through the 'Java Control Panel':
Section 5: Known IssuesDepending on which products technologies and products you are using, there may be some limitations to be aware of and/or other steps you need to perform. Java Plug-in Issues
JRE 1.8.0_101 May Cause Extra Pop-Ups When Using IEJRE 1.8.0_101 does not recognize the 3-digit point release from the numeric CLSID: CAFEEFAC-0018-0000-0101-ABCDEFFEDCBA and only picks up the 2-digit number. Incorrectly it therefore looks for 1.8.0_01 on the desktop causing the following pop-up as it cannot be found:
Selecting 'Run with the latest version' will cause forms to launch using JRE 1.8.0_101. Selecting 'Cancel' will prevent forms from launching. To avoid this problem, upgrade to JRE 1.8.0_102 where this issue is fixed. This issue does not affect users running with a Dynamic or Family CLSID where, If JRE 1.8.0_101 is the latest release on the desktop, it will launch seamlessly. Oracle Security Alert for CVE-2016-0636For further information see Oracle Security Alert for CVE-2016-0636. This issue is fixed in the following JRE releases (JRE 6 is unaffected): JRE 1.8.0_77 (8u77) and higher Firefox: Session Crash (FF ESR 38.4.0 Users)Running Java content with Firefox ESR 38.4.0 using JRE 7 or JRE 8 may cause Firefox to crash. For example, this may be seen when closing your Oracle E-Business Suite browser session. JRE 8 Users This has been fixed for JRE 8 users in JRE 1.8.0_66-b18 which is now available for download from the Oracle Java SE Downloads page. This fix is not included in JRE 1.8.0_66-b33 which fixes the Internet Explorer: Applet Launch Delay issue. To fix both the Firefox: Session Crash and the Internet Explorer: Applet Launch Delay issues, apply JRE 1.8.0_66-b35 which is available through Patch 22286087 - Oracle JDK 8 Update 66 b35. JRE 7 Users This issue is fixed for JRE 7 users in Patch 22217483 - Oracle JRE 7 Update 91 b33. Internet Explorer: Applet Launch DelayLaunching Java content through Internet Explorer will show a delay of around 20-25 seconds delay before the applet starts to load (Java Console will come up if enabled). This occurs when using the following JRE releases:
This issue does not affect Firefox where the applet starts as usual after only a few seconds. JRE 8 Users This issue is fixed for JRE 8 users in the following releases::
JRE 7 Users This issue is fixed for JRE 7 users in the following releases:
Note: Although Java patches may contain both the JRE and JDK releases you only need the JRE version installed on the desktop client to uptake this fix. JRE 1.6.0_85When launching Java through JRE 1.6.0_85 on the desktop, a command window may open from the launcher program
Forms will continue to launch normally but the command window will remain open on the desktop. This error will not occur if using JRE 7 and JRE 6 coexistence on your desktop where for example JRE 1.6.0_85 would run on top of JRE 1.7.0_71 as outlined in Multiple Client Java Plug-in Versions. This issue is fixed in JRE 1.6.0_91 and later. Java Update Needed"Your Java Version is Insecure" Trying to run a version of JRE that is below the security baseline or past its expiration date can cause the following warning message to display: Windows 7 Users Clicking "Update" will download and attempt to install the latest version of the JRE Plug-in from java.com. Suppressing the Message If you want to prevent this message appearing again until the next new JRE release becomes available check the "Do not ask again until the next update is available" checkbox and then select the "Later" button. This option updates the users deployment.properties file as follows: deployment.expiration.decision.timestamp.10.17.2=5/14/2013 11\:0\:19 The above example is based on JRE 1.7.0_17, if the JRE version was 1.7.0_21 the numbering would be "10.21.2" rather than "10.17.2" An administrator may update this information for all their users deployment.properties file so that they do not need to go through the manual steps outlined above on first launch. Depending on which Desktop O/S you are running the users deployment.properties file is held in the following directory: Windows Vista, 7 and 8: Other Ways to Suppress this Message Customers who wish to keep up to date with the later Java releases but also want control over when they upgrade can prevent this message appearing by using a special build of JRE 7 which has the 'Java Auto Update Mechanism' turned off. These versions are available as a patch download, see Document 1439822.1 titled 'All Java SE Downloads on MOS' for a list of JRE versions and their patch numbers. Although Java patches contain both the JRE and JDK releases you only need the JRE version installed on the desktop client to uptake this feature. For further information on using this patch see: Document 1553875.1 - Handling New JRE Security Dialogs JRE 'Out of Date' Warning If your installed JRE 7 or 8 release falls below the security baseline, or passes it's built-in expiration date, an additional 'JRE Out of Date' warning is shown to users to update their installed JRE to the latest version. To suppress this specific warning message, add the following entry in the deployment properties file:
For more information, see Deployment Configuration File and Properties. JRE 1.7.0_45 (7u45) and HigherCertificate Revocation Lists Error using LDAP URL The Certificate Revocation Lists (CRL) check may fail if using an LDAP URL causing forms launch to fail with the following error:
The CRL check was introduced in JRE 7u25 so this error may also be seen when using earlier releases than JRE 7u45 in certain circumstances. How to Fix this Issue This Issue is fixed in JRE 7u51-b32 and higher which is only available through Patch 17981166. (All Java patches contain both the JRE and JDK releases. Only extract the JRE version of Java from the patch and install on your desktop to fix this issue.) Workaround If you are unable to upgrade at this time, turn off the CRL check in the Java Control Panel as a temporary workaround:
Unsigned Entry in Resource Error Running JRE 1.7.0_45 (7u45) on an Oracle E-Business Suite environment that is using JDK 4 on the application tier will fail with the following error in the Java Console (Jar files signed against JDK 4 are not compatible with this JRE release):
How to Fix this Issue To fix this issue follow the steps below: 1. Upgrade the JDK version of your application tier node by following the document below:
2. Regenerate the jar files using the 'force' option through adadmin. JRE 1.7.0_25 (7u25) and HigherJRE 7u25 includes a new security function for permissions and attributes in the Jar Manifest file. This can result in the following warning messages appearing in the Java Console:
For further information regarding this function see the New JAR Manifest File Attributes section within the Java 7u25 Update Release Notes. Patch Fix To fix this issue, apply Patch 17191279. This patch also contains a number of other AD fixes which incorporate the latest jar signing architecture. For further information see Document 1591073.1 titled, 'Enhanced JAR File Signing for Oracle E-Business Suite'. JRE 1.7.0_21 (7u21) and Higher"Your security configuration will not allow granting permission to self signed certificates" JRE 1.7.0_21 (7u21) and higher will no longer run with a 'Very High' security setting set within the Java Control Panel when using Self-Signed certificates. Trying to run Oracle Forms-based content using such a certificate will pop the following message:
After clicking through or closing these messages the following error will appear in the Java Console and forms will not launch:
JRE 1.7.0_21 and higher run on a default security setting of 'High'. If you wish to use a 'Very High' security setting sign the jar files with a Trusted Certificate. The security level can be changed using the slider under the 'Security' tab within the 'Java Control Panel'. For full details regarding the code signing changes, see - Java Applet & Web Start - Code Signing and Setting the Security Level of the Java Client. For further information on Jar signing in EBS see Document 1591073.1 titled, 'Enhanced JAR File Signing for Oracle E-Business Suite'. JRE 1.7.0_11 (7u11)Security AlertJRE 1.7.0_11 (7u11) is a CPU security release which includes the fix for Oracle Security Alert CVE-2013-0422. It is highly recommended that customers on the JRE 7 stream upgrade to this release of higher. JRE 1.6.0_24 (6u24)Security AlertJRE 1.6.0_24 (6u24) is a critical patch update which fixes security vulnerabilities in Oracle Java SE including CVE-2010-4476 (Java Runtime Environment hangs when converting "2.2250738585072012e-308" to a binary floating-point number) which can affect users running JRE 1.6.0_23 (6u23) and earlier. For further information regarding this security alert see alert-cve-2010-4476-305811.html Although the impact of this vulnerability on desktops is minimal and the desktop will not be compromised Oracle recommends that customers upgrade to "JRE 1.6.0_24 (6u24) or higher" as soon as possible. Java Certificate Warning - Publisher UnknownIf you are using a self-signed certificate for jar signing the Publisher will display as UNKNOWN in the Java 'Warning - Security' window when running JRE 1.6.0_24 (6u24) or higher. For further information, see Connecting to an Oracle E-Business Suite Instance for the First Time. General Technology Issues
Adding Custom Jar FilesAdding custom jar files to appsweb.cfg through the use of "userjarfile=<custom.jar>", can cause the forms navigator to function incorrectly after the initial launch of a form. On subsequent form launches the initial navigator window is closed and a new one is opened with the new form. The standard behavior is for the subsequent form to open in the same navigator window. To fix this issue apply Patch 10210925 by following its readme. Application Freeze/Hang IssuesResizing the Forms Applet WindowResizing the forms applet window multiple times may cause the application to freeze when using JRE 1.6.0_10 or JRE 1.6.0_11. This is fixed in JRE 1.6.0_12 (6u12) and later. Right Click in Forms FieldMenu access by right clicking in a forms field may cause the application to freeze when using next-generation Java Plug-in through JRE 1.6.0_10 or JRE 1.6.0_11. This is fixed in JRE 1.6.0_12 (6u12). Windows Rendering slowly using JRE 1.6.0_10 to JRE 1.6.0_13Certain graphics cards (for example NVIDIA GeForce, ATI Radeon) may cause windows to render and display slowly, after moving the form within the window when using next-generation JRE Plug-in technology through JRE 1.6.0_10 to JRE 1.6.0_13. This issue is fixed in JRE 1.6.0_14 and higher. If you are unable to upgrade at this time to workaround the issue in Oracle E-Business Suite it is recommended to either update the appsbase.htm file on the web server OR update the individual desktop clients. Solution 1: Modify the appsbase.htm file Change both the 1) Add - var xjdkprogcolor = "%jdk_progresscolor%" 2) Add - if(xplugin == "jdk"){ 3) Add - IEhtml += '' + 'PARAM name=serverUserParams value="' + xenv + " ';
4) Add -
Solution 2: Update each Individual Desktop Client 1) Open the' Java Control Panel' on the desktop client, 2) Add -Dsun.java2d.d3d=false to the appropriate JRE version under;
Developer 6i Interop PatchApply the Developer 6i Patch 19 (6.0.8.28.x) interop Patch 9935935 or later. Failure to apply this patch can result in the following error:
File Export / Forms Attachments FunctionsJRE 1.6.0_27 (6u27) adheres more strictly to Internet Explorer browser settings. Users may find that the File -> Export and Forms Attachments functions (for example opening Word, *.rtf and Excel attachments) will not work after upgrading to this Plug-in version when running IE6, IE7 or IE8. Trying to run these functions may cause a window to open briefly before closing again, the 'File Download' window will not open. To fix this issue set the following browser setting within IE under the appropriate security zone (using 'Trusted Sites' as an example):
This setting no longer exists in IE9 therefore these functions will not be affected by this issue when running this browser release. Forms Launch IssuesFRM-92095: Oracle JInitiator version too low. Please install version 1.1.8.2 or higher. The above error may be seen when trying to launch forms using the JRE 7.x or higher client Plug-in. To fix this issue ensure you have applied the JRE 7 pre-requisite Patch 14615390 or later as outlined in JRE 7 Minimum Patch Requirements. After applying the patch regenerate your jar files through ADADMIN with the the force option on. 3. Different Users run different JRE Releases from multiple JRE Streams If you have individual users running different versions of JRE streams (for example User A still runs JRE 1.6.0_95 while User B is running JRE 1.7.0_95) or you simply want to allow users to run the latest JRE version on their desktop client, update the appsweb.cfg file to use the dynamic CLSID. When using this setting Oracle Forms-based content will launch using the highest JRE Plug-in version from the highest JRE family stream found on the desktop. Only if no JRE Plug-in version is found on the desktop will the user will be prompted to download the JRE version from the Oracle E-Business Suite web server. Upgrading to a later JRE 1.6.x release must therefore be done from the desktop client. 3.1. Take a backup copy of the runtime appsweb.cfg file under 3.2. Find section "4a) Sun JDK Plugin Parameters" and replace the
3.3. Save the file. (After this change is made users will pick up the new clsid when they next launch a new forms session) Note: This change will get overwritten if AutoConfig is run. To make the change more permanent update the following parameter in the AutoConfig file.
Forms Will Not Launch Using JRE 1.6.0_10 and Higher through PHP Forms will not launch when using 'Personal Home Page' through Oracle E-Business Suite with JRE 1.6.0_10 and higher. 'Personal Home Page' is not supported with Oracle E-Business Suite 11.5.10. To fix the issue change the profile option 'Self Service Personal Home Page mode' to 'Framework Only'. For more information see Document 782315.1. Forms Focus IssuesEnsure you have applied the latest forms focus MLR patches as stipulated in Step 2. Apply Prerequisite Patches (Conditional) above. If you still see forms focus problems follow Document 760250.1 for further information on diagnosing and solving these issues. JRE 8 Users: Possible Focus Loss After Forms Launch Clicking outside the frame onto the desktop or other application during forms launch may cause a loss of focus within the form once it's launched. This can occur in all Oracle E-Business Suite releases when using JRE 8. If this occurs pressing the 'tab' key should regain the correct focus within the form. To fix this issue, apply Patch 22709024 or later. If this is not available for your required platform request it through support. Browser Window Opens Behind the Forms Window Opening an html page from the forms navigator may cause the html window to open behind the navigator window when using Internet Explorer or Firefox browsers. Windows 7 Users Running Internet Explorer This is fixed for Windows Vista and Windows 7 users running the default IE tab browser settings or using non tab browser settings in JRE 1.6.0_27 (6u27). Workarounds for Internet Explorer If you are unable to upgrade the Java Plug-in at this time try one of the following workarounds. 1. Alter the tabbed browser settings in IE7 or Higher To workaround this issue when using IE7 or higher, select the following options in the browser;
Also select either
2. Alter the Registry Settings using TweakUI (XP Users) Altering the registry settings as follows may resolve the issue for all Internet Explorer versions.
3. Turn off Next-Generation Java Turning off next-generation java will workaround the issue for all Internet Explorer versions (IE6 and higher) when using the default browser settings. This can be turned off as follows:
Firefox Users This issue is fixed for users running Firefox in JRE 1.6.0_30 (6u30) and higher by setting the following browser options:
Type Ahead in FormsIf focus is moved out of the window, while a form is loading (for example if a message window pops up and takes the focus), any characters that were typed before the form opened will not register within the form. Forms Closure IssuesInternet Explorer "Close Window" Link - Modal Window“The webpage you are viewing is trying to close the tab, Do you want to close this tab?”. Using the "Close Window" link within an HTML page opened from the "Forms Navigator Menu" through Internet Explorer can cause the following modal window to pop. This requires the user to acknowledge they wish to close the form by clicking the 'Yes' button therefore creating an extra keystroke. To fix this issue upgrade to JRE 1.6.0_27 (6u27) or higher. Forms Listener Socket Mode IssuesHTTPS Connect Mode Using https for the forms communication layer requires the forms listener servlet architecture. For further information on using forms servlet, see Document 201340.1 titled, 'Using Forms Listener Servlet with Oracle Applications 11i'. In contrast, ConnectMode=HTTPS is not supported with the JRE Native Plug-in with the Forms Listener (non-servlet listener) and will cause the following error:
Mismanaged Cookie Session IssueNote: The fix for the Mismanaged Session Cookie Issue is included in the standard release of JRE 1.6.0_23 (6u23) and higher which is available through the usual channels. Update through the Java Update Mechanism Users running either of the following two patched JRE releases cannot rely on the Java update mechanism to upgrade to the latest JRE release:
The Java update mechanism is disabled within these releases and cannot be re-enabled through the 'Java Control Panel'. Users must therefore download and install the latest JRE Plug-in from another source. After installing the latest JRE release the Java update mechanism will once again be enabled allowing full functionality. The Java update mechanism is fully functioning in the usual way for users running the JRE 6u22 patched release listed below:
Running any of the following functionalities using JRE 1.6.0_18 (6u18) through JRE 1.6.0_22 (6u22) in Internet Explorer 6 or 7 may result in a new login page being rendered rather than the correct window or functionality thereby making the functionalities unusable:
To fix this issue it is recommended that users upgrade to JRE 1.6.0_23 (6u23) or higher. If you cannot upgrade at this time it is recommended to remain on JRE 1.6.0_17 (6u17) or use one of the patched releases of the JRE 6u22, JRE 6u21 or JRE 6u20 streams of the Plug-in. These versions are only available through the following patches: JRE 1.6.0_22 build 3 (6u22-b03) through Patch 10189354 Note: If you are affected by this issue, do not download JRE 1.6.0_22, JRE 1.6.0_21 or JRE 1.6.0_20 through the usual channels or through the Java Auto Update Mechanism as these releases do not contain this fix. The standard Java SE versions available are : JRE 1.6.0_22 build 4 (6u22-b04) Patch Installation Instructions for the Desktop The patch can be downloaded and installed directly to a desktop as follows: 1. Download the required patch to your desktop Distributing the Patched Releases of the JRE Plug-in to Users If you wish to distribute a patched release of the JRE Plug-in as a download through Oracle E-Business Suite follow the standard JRE Plug-in upgrade instructions in this document. If users are upgrading to a higher JRE release the Plugin will be downloaded and installed in the usual way as described in this document. If users have already installed the same Plug-in version number that does not include the fix from the usual download sources or through the 'Java Auto Update Mechanism', they will not be offered the Plug-in release for download from Oracle E-Business Suite until the current version is uninstalled from the desktop. Using JRE 1.6.0_22 (JRE 6u22) as an example: JRE 1.6.0_22 (JRE 6u22) Users If you already have JRE 1.6.0_22 build 4 (JRE 6u22-b04) from the usual download site or through the 'Java Auto Update Mechanism' installed on your desktop, uninstall it as follows: Uninstall the existing JRE 6u21 Plug-in 1. Uninstall the Plug-in from your desktop (see Uninstalling a JRE Plug-in Version from your Desktop Client)2. Install the new release on the desktop or download it through Oracle-E-Business Suite Alternatively, if you download the JRE 6u22-b03 release from Patch 10189354 you can simply overwrite the existing version with the newer release as follows: Overwriting your Existing JRE6u22 Release 1. Run the patched j2se16022.exe on the desktop Workaround To workaround the issue disable next-generation java through the 'Java Control Panel' as follows:
Note: Turning off next generation java can cause forms launch issues in certain very specific circumstances, see Forms Launch Issues for further information. Running JRE 6u20-b02 may also prevent the file opening when running the 'File->Export' functionality. Apply Patch 9915543 (JRE 6u20-b05) and turn next generation java on again to fix the problem. NLS/MLS IssuesChinese (Taiwan) Characters Characters in any workflow diagram are incorrectly displayed when using 'Chinese (Taiwan)' locale settings on the desktop client, running JRE 1.6.0_17 (6u17) or JRE 1.6.0_18 (6u18). This issue is fixed in JRE 1.6.0_19 (6u19) and later. Accented Characters If you need to use two or more keystrokes to input an accented character apply Patch 5526175. (This patch requires Developer 6i patch 18 (Forms 6.0.8.27)). Multiple Language Display Support By installing the Albany WT J fonts, the JRE Plug-in can render Chinese, Japanese or Korean characters on any Windows systems. However, it is extremely important to have your Windows regional settings configured to use your primary language for the JRE Plug-in to render language dependent characters in appropriate fonts. Install Albany WT J Font To obtain and install the Albany WT J font follow Document 240862.1. Setting Primary Language on the Desktop Client. Windows Vista Users To set your primary language on a Windows Vista desktop client, go to Control Panel > Regional and Language Options window. Select your primary language from the 'current format' LOV under the 'Formats' tab. Also make sure your primary language is chosen as the 'Current Language for non-Unicode programs' under the 'Administrative' tab. Windows 7 Users To set your primary language on a Windows 7 desktop client, go to Control Panel -> Region and Language -> Formats (tab). Select your primary language the the 'Format:' drop down LOV. Also make sure your primary language is chosen as the 'Current Language for non-Unicode programs' under the 'Administrative' tab. Japanese Language Users Japanese language customers should upgrade to Developer 6i Forms Patch 18 (6.0.8.27.x) or higher. Earlier versions of the Developer 6i Patch will cause the longer prompts in forms to be cut short, which will impact the forms layout. If you have your machine locale set to Japanese, you may find that the Underline for the 'Menu Access' key on the 'Button Label' is incorrectly placed by one character to the right. This may also be seen in other places where English characters are used, for example in the Logon Dialog, LOV Search box and Menus. To work around this issue: 1. Make a backup of 2. Change the existing line that reads:
to:-
Japanese JIS X 0213:2004 Character Set The Japanese 'JIS X 0213:2004 Character Set' is included in Windows Vista and is also available through a Microsoft package for Windows XP. This character set has only partial character support with Oracle E-Business Suite. There is no support for the supplementary character set, while combining characters is partially supported with the appropriate fonts. Currently, there is also no Oracle font support, however a solution to this issue is being investigated and will be announced in due course. Arabic Characters When Arabic characters Alef and Lam are joined in the middle of a word, they appear incorrectly at runtime. This issue is fixed in JRE 1.5.0_17 and JRE 1.6.0_12 (6u12). Security Warning Running JRE 6u19 and Later"Java has discovered application components that could indicate a security concern" JRE 6u19 and higher includes a new security setting parameter called, By default the following warning dialog window will display when running certain forms and functionalities in Oracle E-Business Suite. This may occur when running certain forms or functionalities due to the associated (*.gif) files, for example:
To continue to the form or functionality click the 'No' button. After selecting this option the form or functionality will behave normally and the message will not appear again for the remainder of that browser session. For further information see the Mixing Signed and Unsigned Code webpage. Patch fix To fix these issues, apply Patch 17401744 (which includes fndjar.dep version 115.307) or later. Account Hierarchy Manager & Financial Dimensions Hierarchy Manager To fix this issue for Account Hierarchy Manager (AHM) & Financial Dimensions Hierarchy Manager (FDHM) you can download a signed jbodatum111.jar file through Patch 17391300. Alternatively you can sign jbodatum111.jar using jarsigner. For full details on using jarsigner see 'The Java Tutorials', Signing Jar Files. Note: If you have applied the enhanced jar signing AD Patch 17191279 see Appendix C: Jar File Manifest Updates and Jar File Signing in Document 1591073.1 titled, 'Enhanced Jar Signing for Oracle E-Business Suite' for information on signing a single jar file. If you have not yet applied the enhanced jar signing AD Patch 17191279 you may use the following steps to sign jbodatium111.jar. To sign the jar file you will require the following four values: These can be obtained by running the following commands: 1. $ cat $APPL_TOP/admin/adsign.txt
The basic form of the command for signing a JAR file is
Where: jar-file = pathname of the JAR file that's to be signed. To sign jbodatum111.jar run the following command and enter the appropriate passwords when asked:
Overwrite and remove the $APPL_TOP/admin/keyinfo.txt file
Alternatively use one of the workarounds outlined below. Workarounds If you are unable to apply the fix at this time or a fix is not yet available, one of the following workarounds can be used to prevent the activation of the warning window and allow the affected functionalities to work normally: Java Control Panel Select the following option in the 'Java Control Panel' from the desktop client;
deployment.properties File Add the following entry to the deployment.properties file on the desktop client;
For information on updating the deployment.properties file reference the Deployment Configuration File and Properties document. SSL IssuesSSL Enabled Webcache Environments If you are connecting to an SSL enabled Webcache instance using JRE 1.6.0_xx ensure the following parameter is checked in the 'Java Control Panel' on the desktop client';
JRE 6 is not truly SSL 2.0 compatible TLS 1.0 clients that support SSL Version 2.0 servers must send SSL Version 2.0 client hello messages. TLS servers should accept client hello format if they wish to support SSL 2.0 clients on the same connection port. Without this parameter checked, forms will not launch and the following error will appear in the java console;
Other IssuesFont metrics were incorrect in JDK 1.1.8.x (JInitiator 1.1.8.x) and changed in JDK 1.3.1.x (JInitiator 1.3.1.x) and higher. Logical fonts are bigger when running the JRE native Plug-in compared to JInitiator 1.1.8.x, this is intentional behavior. Forms will default to a 'Portrait' orientation when printing from Oracle E-Business Suite ignoring the print orientation settings from the desktop. To print in 'Landscape' will require the setting to be altered at runtime each time you print a form. For forms to print using the desktop default setting apply Patch 8485936. Note: This patch is also included in the forms focus Patch 14009893 and later. System administrators should apply Patch 4469342 to their Oracle E-Business Suite environments to allow connection through TCF when using JRE Native Plug-in. Product Specific Issues
Oracle Applications Framework Navigator PageIf you are using Oracle Applications 11.5.10 CU1 or earlier, you must apply Patch 4517707. This patch will fix serious performance issues on subsequent 'Oracle Forms' launches from the Framework Navigator. Oracle Applications 11.5.10 CU2 and higher users do not need to apply this fix. ABM UsersABM users must apply ABM G.5 Patch 4912215 or later. Account Hierarchy Manager UsersAccount Hierarchy Manager users must use the Thin Client Framework (tcf) connection method when using JRE, by applying Patch 4994984. Discoverer UsersDiscoverer users running JRE 1.8.0_25 or higher must upgrade to OracleBI Discoverer (11g) 11.1.1.7 and also apply Patch 20219002 by following its readme. Discoverer with JRE 1.7 Discoverer users running OracleBI Discoverer (11g) 11.1.1.7 or higher should apply Patch 20219002 by following its readme. Discoverer users running JRE 1.7.10 or higher must upgrade to OracleBI Discoverer (11g) 11.1.1.6 or higher. Discoverer (11g) 11.1.1.6 users must apply Patch 13877486. (Also see Document 233047.1 titled, 'How To Find Oracle BI Discoverer 10g and 11g Certification Information'). Discoverer with JRE 1.6 Discoverer users running JRE 1.6.0_03 or higher must upgrade to OracleBI Discoverer 10.1.2.2 CP6 or higher. JVM Shared, not allowed to set security manager Discoverer may display the following error when trying to launch from another application or a managed link URL:
To fix this issue apply the following patch as applicable to your Discoverer release: Oracle BI Discoverer (11g) 11.1.1.7 Users - Patch 17303613 Oracle BI Discoverer (11g) 11.1.1.6 Users - Patch 17319353 RMI Protocol over JRMP transport: Session has timed out (JRE 1.6.0_23 or lower) Trying to launch Discoverer Plus from Oracle E-Business Suite may cause the following error:
To fix this issue upgrade to JRE 1.6.0_24 or higher. Financial Dimension Hierarchy Manager UsersFinancial Intelligence users with 'E-Business Intelligence Family Pack 11i.BIS_PF.D.1 (DBI 7.0.1, Patch 4054609) or earlier, must also apply the 'FDHM on Thin Client Framework (TCF) - ROLLUP 1' Patch 4534669 or later. Financial Intelligence users with 'E-Business Intelligence Family Pack 11i.BIS_PF.E (DBI 7.1, Patch 4143498) or later, must apply 'FDHM on Thin Client Framework (TCF) with Sort Order - ROLLUP 1' Patch 4534531 or later. Rendering IssuesUsers may see issues such as Frame and Scroll bar shake and the incorrect rendering of drop down LOV's. These problems will cause an error in the Java Console window starting:
To fix this issue apply JEWT Patch 5261689 - Rehost JEWT V4.1.12 for Apps 11i. Scripting IssuesDue to certain jar files not being cached, scripting users may notice poor performance when running a script. To fix this issue apply Patch 8400346 by following its readme. Sourcing - Auction MonitorAfter applying Sourcing 11.5.10 RUP3 (patch 6505173), Auction Monitor will not launch through JRE and will only launch using JInitiator 1.3.1.21. This issue is fixed in Oracle Procurement Family 11.5.10 Rollup Patch 12, (Patch 8791241). Windows Vista and Windows 7 UsersJRE Cache Directory When running Windows Vista, Windows 7 or Windows 8 the JRE cache directory can no longer be changed through the Java Control Panel. The Change button is disabled under
Users wishing to change the cache location must do so through the deployment.properties file:
For information on updating the deployment.properties file reference the Deployment Configuration File and Properties document. Note: If the cache directory is changed to a non low-integrity directory, 'Protected Mode' must be turned off within Internet Explorer at runtime to allow the initial download of new or updated jar files into that cache directory. With 'Protected Mode' turned on, users may get a Appendices
Appendix A: Information for JRE 64-bit UsersRunning 64-bit JRE with IE11 Internet Explorer runs in a multi-process architecture whereby there is a Frame (Manager) process and one or more Tab (Content) processes. There is no longer a separate 32-bit and 64-bit install of the browser when running a 64-bit version of Windows. To use JRE 64-bit versions with IE11 see the browser set up requirements under 'Internet Explorer: Running IE 11 in 64-bit Mode' within Document 389422.1. Java Control Panel If both the 32-bit and 64-bit JRE versions are installed on the desktop the 64-bit 'Java Control Panel' will default as the viewable version under ' Control Panel':
You can view the 32-bit version of the 'Java Control Panel' by running the
Appendix B: Static vs Non-Static Versioning and Set Up OptionsThis section provides an overview regarding the historical use of 'Static Versioning' and the current 'Non-Static Versioning' models for Oracle E-Business Suite users. Static Versioning (Historical information)Static versioning denotes the behavior by which a specific version of the Java Plug-in must be used to access an application regardless of whether later JRE Plug-in versions were also installed on the desktop client. This was the default behavior when accessing Oracle E-Business Suite through Oracle JInitiator. This behavior could also be maintained using classic JRE Plug-in releases (JRE 1.6.0_07 and lower) through registry changes on the desktop which ceased with the introduction of next-generation Java (JRE 1.6.0_10 and higher). With static versioning Oracle E-Business Suite would use a specific Plug-in version meaning users could only access the instance if using that particular Plug-in version. Advantages
Disadvantages
Non-Static VersioningNon-Static versioning denotes the behavior by which the latest Java Plug-in version installed on the desktop client is used to try and run Java content. For IE users, the Plug-in version set as the CLSID value on the web server is the minimum version that can be used to run a forms-based (professional user interface) responsibility from the desktop client. If multiple versions equal to or greater than the version specified are installed on the desktop client the preference will be to connect using the latest available version. Firefox uses an open mimetype and will therefore always have a preference for the latest available version of Java installed on the desktop. Advantages
Disadvantages
Appendix C: Advanced JRE Set Up OptionsJava Plug-in Coexistence on a Desktop ClientThis section provides an overview of having multiple JRE Plug-in versions coexisting on a single desktop client. In the correct circumstances two different JRE families may seamlessly coexist on the same desktop client and allow connection to the same or multiple Oracle E-Business Suite environments using one plug-in or the other. This can be useful for testing purposes and connection to multiple Oracle E-Business Suite environments that may be calling different Plug-in streams. It may also be possible to connect to the same environment using different Plug-in streams see Adding Additional JRE Plug-in Versions in EBS. Java Deployment Technology Components With multiple versions of Java installed on a desktop Java content will initially launch using the 'Deployment Technology Components' of the latest version of JRE from the highest Java family available. Note: The 'Deployment Technology Components' have been removed for the Java 6 & 7 streams starting with the October 2017 CPU releases, JRE 1.7.0_161 & JRE 1.6.0_171. This means you will no longer be able to launch any Java content using these or later releases standalone. In the correct circumstances Java content can still be run using these releases by also installing JRE 8 on the client in order to facilitate the intial launch. The 'Java Security Baseline' is applicable when different JRE family versions are installed on the desktop client and the web server is calling a lower JRE family version. The latest security baselines are:
The security baselines for each JRE version are stated in the Update Release Notes. Coexistence Using the Latest JRE Releases Note: Ensure you have applied the Jar Manifest permissions and attribute fix to all EBS environments where you require coexistence even if it is running JRE 6, see JRE 1.7.0_25 (7u25) and Higher for the patch requirements. Although this security change is a requirement for JRE 8 and JRE 7 you will still require this fix on an environment where you also want to run JRE 6. This is because the 'Deployment Technology Components' of JRE 8 or JRE 7 will be used to initially launch the applet which will check the suitability of the Jar file manifest before attempting to hand over control to JRE 6. Running different JRE streams seamlessly from the same desktop using the recommended Java security setting or higher (High or Very High) requires the latest available JRE CPU release with the equivalent JRE family baseline. In some cases you may also be able to run this function using a primary release below the latest CPU, however it will cause extra pop-ups or may not function at all. The following table provides a few examples outlining the expected behavior when implementing multiple JRE releases from the same desktop client.
1 Internet Explorer uses the 2 Running JRE 1.6.0_171 requires JRE 1.8.0_152 due to a bug in earlier releases, see JRE 6 Coexistence with JRE 8 for further information. Coexistence Using JRE Releases Below the Security Baseline Note: When running on the recommended 'High' or 'Very High' security settings; where the expiration date of a JRE release has been reached this function will stop working causing the Warning - Unavailable Version of Java Requested message to pop. JRE expiration dates are available in the JRE 8 Release Notes and JRE 7 Release Notes. JRE releases will expire upon the release of a later version that includes security fixes if you are accessing an Oracle server. For systems unable to reach Oracle servers, the JRE will expire one month later through an internal mechanism. For further information see the JRE Expiration Date page. Coexistence of older JRE versions may be achieved but often requires the Java security levels to be lowered. This is therefore not recommended as a long term solution but can be useful for testing purposes for example. Versions below the latest security baseline, or versions that are past their expiry date can be deemed Older versions. The following provides a brief overview of the required settings for running older versions of JRE from different families. The same principles can be used if you wish to run two versions from the same family. Running JRE 8 and JRE 7 from the same desktop
Running JRE 8 and JRE 6 from the same desktop
Running JRE 7 and JRE 6 from the same desktop Note: This combination is no longer possible using JRE 1.7.0_161 and later as the 'Deployment Technology Components' allowing Java launch have been removed in this release and later on the JRE 7 stream.
Deployment Rule Set Further control over calling different JRE releases for different applications or security access can also be achieved by implementing a Deployment Rule Set. Coexistence Known Issues and Limitations Firefox Browser Firefox users cannot run multiple JRE versions simultaneously from the same desktop client. This browser uses a single cookie session which restricts usage to a single Java version per desktop client at a time. You can access environments using different JRE versions from the same desktop client, but the previous browser session must be completely closed down and a new one started before running a different JRE version. You may still access the same Oracle E-Business Suite environment simultaneously using different JRE versions, but only by using separate desktop clients. Each desktop client would use a specific JRE version. With the correct set up you can run multiple JRE versions simultaneously from the same desktop using Internet Explorer. Coexistence using JRE 1.6.0_121 and later with JRE 8 will fail, displaying the following or similar error within the Java Console:
This issue is fixed through JRE 1.8.0_152 or later, allowing coexistence with JRE 6 to function correctly. 3-Digit Point Release Versions Not Recognized by Java 8 It is not possible to run 3-digit point release versions of JRE using the 'Deployment Technology Components' of some earlier JRE 8 releases. Only the final 2-digits are recognized and therefore the correct Java version is not found. For example if trying to use the coexistence rules to run JRE1.7.0_101 with JRE 1.8.0_91 a pop up message will display stating: "This application would like to use a version of Java (1.7.0_01) that is not installed on your system.We recommend running the application with the latest version of Java on your computer." If you click the "Run with the latest version" button, the Java content will simply launch using JRE 1.8.0_91. This issue is fixed in JRE 1.8.0_102 and later. General Warning Messages Warning - Unavailable Version of Java Requested Trying to call a version of Java that is past it's expiration date when using the recommended 'High' or 'Very High' security settings will cause the following warning message to pop. Selecting 'Run with the latest version' will cause forms to launch using the higher JRE version on your desktop. Selecting 'Cancel' will prevent forms from launching. An Application would like access to an out-of-date version of Java If you have JRE 1.7.0_21 or higher installed on your desktop with Java security set at 'Medium' (Not Recommended) or have JRE 1.7.0_17 or earlier installed on your desktop running with their default Java security settings the following security warning may display: Selecting 'Run with the latest version on your system...' will cause forms to launch using JRE 1.7.0_25. Selecting 'Allow this application to run with the requested version...' will launch using JRE 1.6.0_43 on top of JRE 1.7.0_25. Resetting Security Prompts The choice made by the user in response to this security message is stored in the Java cache. Choosing which version to use is therefore remembered when accessing the environment in future and the warning will not pop again. If you wish to change your choice and run using the other the version to access the environment you can make this message pop again as below: JRE 1.7.0_40 and Earlier If running JRE 1.7.0_40 or earlier you can restore the security certificates by clearing the 'Installed Applications and Applets' in the Java Cache:
JRE 1.7.0_45 and Later If running JRE 1.7.0_45 or later you can restore the security certificates by selecting the 'Restore Security Prompts' button:
Note: Running two JRE Plug-in versions from the same desktop client can be managed seamlessly by using IE8 or IE9 32-bit and 64-bit browser as outlined in Appendix A: Information for JRE 64-bit Users. Adding Additional JRE Plug-in Versions in EBSIt is recommended that only one JRE version is used to access a single Oracle E-Business Suite instance There may be occasions where it is desirable to test and compare changes in functionality or security across different Plug-in versions in a test system. Users may access the same Oracle E-Business Suite instance from the same desktop client using different JRE client Plug-in versions in the following ways. The txkSetPlugin script outlined in Step 4. Apply the Interoperability Patch section above, is only run for the version of JRE that you wish to have as your default Plug-in.To add additional JRE versions to be run against the same environment follow the steps below. Adding a JRE Version Using JRE 1.6.0_161 as an example. 1. Copy the j2se16161.exe file to your 2. Take a backup copy of your original 3. Add the following information under [myExtensions] at the bottom of your Substitute the environment values as appropriate to your own environment. The connectMode and serverPort settings can be copied from your Socket Example:
4. Enter the forms URL against the ICX: Forms Launcher profile at user level for the appropriate E-Business Suite user. (If required, you may set up a new user through the System Administrator Responsibility for this). In this example, logging in as this user will cause JRE 1.6.0_161 to be used as the Plug-in instead of the default version providing JRE 1.6.0_161 is the highest available version of JRE available on that particular desktop client or a suitable security baseline version. The name you used in the update above under step 3, e.g. [J16161] must be referenced as the 'config' parameter like the example below:
5. Run autoconfig to filter the changes through to the runtime version of appsweb.cfg. Appendix D: Desktop Client Information
Java Auto Update MechanismBy default the 'Java Auto Update Mechanism' is enabled in the 'Java Control Panel' when JRE is installed on the desktop client. With this enabled users may be automatically upgraded to a later JRE version on their desktop client. Turning this feature off will not prevent the possibility of an admin user downloading a higher Plug-in version from another source, for example another application or web page Installing another Plug-in version in this way can re-enable the default automatic update behavior. JRE versions without the 'Java Auto Update Mechanism' are also available through patch download as outlined in Document 1439822.1, titled 'All Java SE Downloads on MOS'. Disabling the Java Auto Update MechanismJRE Releases with Auto Update Off Customers that wish to control when their users are upgrade to the latest JRE release may use special versions of the JRE Plug-in that have the 'Java Auto Update Mechanism' turned off. JRE Plug-in releases with Auto Update turned off can only be downloaded through My Oracle Support. The required patch number is listed in the JRE Parameter Settings table within this document. These are also listed in Document 1439822.1, titled 'All Java SE Downloads on MOS' and look for patches named 'Oracle JRE X Update XX with Auto Update Off' e.g. 'Oracle JRE 7 Update 79 with Auto Update Off'. Auto Update is turned off by default on all builds of JRE 1.6.0_60 (6u60) and higher. Standard JRE Releases To prevent the automatic update of higher JRE Plug-in versions this feature may also be disabled when using a standard JRE release with one of the options below: Option 1: From the 'Java Control Panel'
Option 2: Through the Registry
Before editing the Microsoft Windows registry, users are strongly advised to review Windows registry information for advanced users (Microsoft Knowledge Base Article 256986). Accessing Oracle E-Business Suite from a Desktop ClientAdministrator privileges are required for installing all JRE Plug-in versions on the desktop client. IE Browser Settings for User Download of the Java Plug-in (oaj2se.exe) Oracle recommends that customers running Oracle E-Business Suite through a Microsoft Internet Explorer (IE) browser should use a 'Medium' security setting through the 'Trusted Sites' zone in the browser at runtime. Further information on browser settings are available from Document 285218.1 titled, 'Recommended Browsers for Oracle E-Business Suite 11i'. If the appropriate Plug-in or higher is not already installed on the desktop client, you should be prompted to download it when trying to connect to a 'forms link' through an Oracle E-Business Suite forms-based (professional user interface) responsibility. Note: The oaj2se.exe can usually be downloaded manually by adding '/OA_HTML/oaj2se.exe' to the base url of the environment. For example; if the base url of the environment was 'https://server1.example.com:4443', you could run 'https://server1.example.com:4443/OA_HTML/oaj2se.exe'. With a medium security setting, after clicking on a 'forms link', a message similar to the following should appear at the top of the browser window; JRE 6 Users
JRE 7 Users
If you see this message, follow the steps below to install the Plug-in:
Alternatively, you can avoid this message by temporarily altering the security settings for the initial install, using one of the two methods below. Once the Plug-in has been installed on the desktop client, the browser security settings should be reset to 'medium'. Method A: Change Security Setting to Medium-low
Method B: Change Individual Parameter Settings
Connecting to an Oracle E-Business Suite Instance for the First Time "The application's digital certificate cannot be verified. Do you want to run the application?" If accessing Oracle E-Business Suite using a Forms-based (Professional user interface) responsibility where the Java certificate for the environment you are accessing has not previously been installed into the Java certificate store, the following warning window will display: JRE 7 Users JRE 7u40 and Higher Users If your Jar files are still signed with a self-signed certificate, the option to 'remember the decision' for future logins has been removed in JRE 1.7.0_40 (7u40) and later. This warning message will therefore appear each time you start a new session requiring the user to agree to accept the risk before running.
Tick the checkbox and click the To prevent this security window popping it is recommended that you sign all your jars using a trusted certificate authority (CA). Signing can be done using either an official CA (such as Verisign, Thawte etc.) or an in-house CA. For further information on Jar signing requirements see Document 1591073.1 titled, 'Enhanced JAR File Signing for Oracle E-Business Suite'. Running with a Self-Signed Certificate If your Jar files are signed with a self-signed certificate you can still launch Java content and also prevent this window from popping by utilizing a Deployment Rule Set. However, the DeploymentRuleSet.jar file must itself be signed with a certificate from a Trusted CA, either an official CA (such as Verisign, Thawte etc.). If your Jar files are signed with a self-signed certificate you can also still launch Java content using a self-signed certificate by utilizing the Exception Site List feature from the desktop. However, this will not suppress this warning message. Users will still be required to respond to this warning each time they launch a new session. JRE 7u21 and Lower Users If accessing Oracle E-Business Suite using a Forms-based (Professional user interface) responsibility where the Java certificate for the environment you are accessing has not previously been installed into the Java certificate store, the following, or similar, security warning window will display: Check the JRE 6 Users JRE 6u60 and Lower Users Check JRE 6u65 and Higher Users To further enhance Java security the option to install the certificate into the Java certificate store and remember the decision for future logins when using self-signed certificates has been removed in JRE 1.6.0_65 (6u65) and higher. This warning message will therefore appear each time you start a new session if using self-signed certificates. To prevent this message appearing sign your jar files using a trusted CA by following Document 1591073.1. Click the Note: If you are using a self-signed certificate for jar signing the Publisher will display as UNKNOWN in the Java 'Warning - Security' window as shown above. This is an intended change in behavior to avoid misrepresentation and spoofing attacks. Trusted signing authorities will continue to display the publisher name as in previous JRE Plug-in releases. Return to Step 5.3 (if required). Return to Section 5. Known Issues Uninstalling a JRE Plug-in Version from your Desktop ClientWindows Vista and Windows 7 To uninstall a JRE Plug-in version from your desktop client: 1. From the Windows 'Control Panel' click on 'Programs and Features'. Reverting to a Previous JRE Plug-in VersionIf you wish to revert back to previously installed version of JRE to be used in your Application re-install the required version by re-running the Appendix E: Reference InformationJRE Tracing optionsJRE native Plug-in has the following levels of tracing available;0 - off The trace level can be enabled by entering the appropriate number key for the tracing level required in the java console window once it has launched. This can however be problematic as the speed of the jar download may mean that the initial information is not captured. You may enable the required trace level before start up by updating the 'Java Runtime Parameters' in the 'Java Control Panel': 1. Open the Java Plug-in Control Panel on your desktop through:
The Java Console output can also be written to a log file by enabling logging in the 'Java Control Panel': 1. Open the Java Plug-in Control Panel on your desktop through: The log file will be written to the Windows Vista, 7 and 8
See the Tracing and Logging page for further information. JRE Parameter SettingsJRE Parameter and Patch Numbers The following table shows the required parameter values and patch numbers for the latest as well as historical versions of JRE for use with Oracle E-Business Suite. Occasionally a one off patch release of JRE may also be recommended to fix a specific problem. All JRE patch numbers are listed in Document 1439822.1, titled 'All Java SE Downloads on MOS'. Many of the special builds listed in that document are not required for EBS users and are therefore not tested against EBS. Unless specifically instructed otherwise only use the standard releases listed in the table below. Note: Odd number versions (e.g. 1.8.0_211) denote that it is a Critical Patch Update (CPU) release. Even number versions (e.g. 1.8.0_212) are generally Patch Set Updates (PSU) or Bundled Patch Releases (BPR) (Builds 31 and higher). Users are recommended to only use the PSU/BPR release if they are being impacted by any additional fixes that may be included in them. These later builds are not tested unless they include a specific bug fix applicable to Oracle E-Business Suite.
1 Patch No. Standard Public Build: This patch contains the same JRE build that was/is available from the public download sites and through the 'Java Auto Update Mechanism'. 2 Patch No. Auto Update Off Build: This patch contains the standard JRE build with the 'Java Auto Update Mechanism' turned off. This is specifically for customers who wish to keep up to date with the latest Java 32-bit releases but also want control over when their users upgrade. Note: Java patches generally contain both the JRE and JDK releases. Extract and use the JRE version of Java from the patch, the JDK version is not required for the purposes of this document. Related Notes
Change Log
Document 290807.1 by Oracle Applications Development | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
扫一扫
2971
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
