Java Client Certification for OmegaPS 10g

Transcription

1 Java Client Certification for OmegaPS 10g OmegaPS 10g is NOT compatible with : Google Chrome browser (Version 42 and onwards), due to a Java issue Java 7 Update 21 Java 6 Update 45 Applies to: OmegaPS R16 (10g Web Variant) to OmegaPS R OmegaPS 10g is certified with the following Java Clients (also known as Java Runtime Engine or Java SE Runtime Environment), 32-bit editions: Java 8 Update 60 Java 8 Update 51 Java 8 Update 45 Java 8 Update 40 Java 7 Update 76 Java 7 Update 75 Java 7 Update 72 Java 7 Update 71 Java 7 Update 67 Java 7 Update 65 Java 7 Update 60 Java 7 Update 51 Java 7 Update 45 Java 7 Update 40 Java 7 Update 25 Java 7 Update 17 and earlier Java 8 & Java 7 require client configuration before being used with OmegaPS 10g; see the Java 8 & 7 Configuration Steps on the next page. Java 6 Update 43 and earlier Java Editions Please note that only the Java 32-bit edition is certified; however, Java 32-bit is fully compatible with 64-bit Windows clients such as Windows 7 64-bit. Google Chrome no longer supported Google have deactivated the required protocol to run Java from the Google Chrome browser, from the April 2015 Chrome update (version 42). Whilst this can currently be manually re-activated in the Chrome browser client, this protocol (NPAPI) will be permanently deactivated in Google Chrome from September Please contact Pennant Support if you require details of the workaround. This is a fundamental change to the Google Chrome browser, which will prevent it from running any web-launched Java application the problem is not specific to OmegaPS. Pennant therefore have had to follow Oracle s lead, and can no longer certify OmegaPS with the Google Chrome browser. We assure our customers that the Microsoft Internet Explorer and Mozilla Firefox browsers remain fully compatible with the Java client, and are certified to run OmegaPS. For further details, see this Google Chrome web site and this Oracle Java web site Page 1 of 14

2 Java 8 & 7 Configuration Steps OmegaPS 10g requires the following configuration steps to work with the Java 8 or 7 client: Part 1 : Environment Variable Configuration 1. Ensure that all browser windows are closed 2. On a Windows 7 client machine, perform the following: a) Navigate to the Control Panel, and select the System item: Page 2 of 14

3 b) In the System panel, select the Advanced system settings option: Page 3 of 14

4 3. On a Windows XP client machine, perform the following: a) Navigate to the Control Panel, and locate and open the System item: Page 4 of 14

5 b) In the System Properties dialog, navigate to the Advanced tab: 4. Select the Environment Variables button: 5. Go through both the User variables box and the System variables box, looking for an existing variable called JAVA_TOOL_OPTIONS. If this variable is found, please contact Pennant Support for further advice on performing this configuration. Page 5 of 14

6 6. Assuming no existing JAVA_TOOL_OPTIONS variable is found, select the New button in the System variables block, at the bottom of the screen: 7. In the resultant New System Variable dialog, create a new variable with the following information: Variable name JAVA_TOOL_OPTIONS Variable value -Djava.vendor="New Oracle" Note the leading hyphen - then select the OK button: 8. Select the OK button in the Environment Variables dialog, then the OK button in the System Properties dialog to save this change. Page 6 of 14

7 Part 2 : Java Client Exception Site List New from Java 7 Update Locate the Java 32-bit icon in the Control Panel: (Windows 7 Control Panel examples shown) Page 7 of 14

8 10. Open the Java Control Panel: 11. Navigate to the Security tab, ensure that the Enable Java content in the browser checkbox is checked, then click on the Edit Site List button : Page 8 of 14

9 12. The Exception Site List dialog will be displayed: 13. Leaving this dialog open, examine the icon / shortcut / browser favourite used to run OmegaPS; e.g (from an Internet Explorer shortcut): 14. Note the URL in this shortcut; this may also be known as the web address or web link. In the above example, it is: Page 9 of 14

10 15. Make a note of the first part of this text string from the beginning ( ) up to and including the next / From the above example, this would be: Return to the Exception Site List dialog, and press the Add button: 17. In the Location field, enter the extract from the OmegaPS URL text string entered above: Note that the icon on the left of the Location field has changed from a red exclamation mark to an unlocked padlock Page 10 of 14

11 18. Press Enter the following dialog is displayed: 19. Press the Continue button 20. If this site has OmegaPS installed on multiple web servers, each one will need to be added to the Exception Site List. To do this, repeat steps 13 to 19 for each additional OmegaPS web server. 21. Press the OK button to close the Exception List: Page 11 of 14

12 22. Back on the Security tab of the Java Control Panel, note that the added Locations are now displayed in the summary of the Exception Site List: 23. Press OK to close the Java Control Panel. 24. Close the Control Panel window. Configuration is now complete; OmegaPS can now be used on this workstation. Page 12 of 14

13 Known Issue In OmegaPS 10g, the old style database logon window does not accept keyboard input to move to a new field. Details: If your OmegaPS installation is setup to use a generic web (or SSO) logon, or you use the standard Change Connection option, then you will be familiar with this Logon dialog: This is the standard Oracle Forms Logon dialog - the end user enters their Oracle database connection details, and then presses the Connect button to login. There is a minor issue with this dialog when used via the Java 8 or 7 client - the Tab button is not recognised, preventing easy movement from field to field; instead, the mouse must be explicitly clicked into the required field. Workaround 1: Use the mouse to move around the fields in the dialog. Workaround 2: Enter the username, password and database onto the first line (labelled Username: in the dialog), using this syntax: <username>/<password>@<database> Page 13 of 14

14 FAQ Q1. What happens if the above configuration steps are not performed for a Java 8 or 7 client? A1. After the web logon, OmegaPS 10g will fail to start, with either of the following messages displayed: In the web browser window: A popup dialog, in the Java window: To fix this, click OK to exit this dialog, then close the web browser and follow the above configuration steps. Q2. Is OmegaPS still certified with the previous Java 6 client? A2. OmegaPS 10g is certified and fully functionality with the Java 6 (or 1.6) JRE client, from JRE 1.6 Update 18 onwards. Q3. With the Java 7 Update 10 or later version of the Java client, OmegaPS does not work - when trying to start it the browser displays errors about missing or disabled plugins? A3. Java 7 Update 10 introduced a new Security feature, to allow the Java client to be disabled from use via a web browser. As this is how OmegaPS uses the Java client, this new feature must not be used. To confirm this, ensure that the Enable Java content in the browser checkbox noted in step 11 above is checked. Page 14 of 14