Adjusting Oracle EBS Forms resolution

Customer September 8, 2020 at 7:04 pm

We have users running EBS Forms on Mac OS workstations, and they constantly report that the Forms size is incorrect—either too large or too small. We believe the resolution is inferior compared to the native Mac OS resolution. How can we resolve this display issue?

Viewing 10 reply threads

Author
Replies
- Support September 10, 2020 at 2:06 pm
  This is a recognized issue, and the solution typically involves consulting the specific guidance outlined in MOS Doc ID 2924556.1, which addresses the inferior resolution of EBS Forms-based applications on Mac OS workstations. This solution focuses on adjustments related to the display settings impacting Java Forms.
- Customer September 12, 2020 at 11:47 am
  Our users are on the latest macOS (Tahoe 26, M4 chip) and Java 1.8.0_461. We followed some steps for generating an `open_forms.command` script, but the EBS session only displayed the Oracle copyright information. Could this be a JWS issue?
- Support September 13, 2020 at 4:09 am
  The behavior suggests that while the Java environment might be running, the EBS form launch configuration may be incomplete. If you see only the copyright, it’s often a sign that the necessary Java Web Start (JWS) launch sequence isn’t fully executing. Crucially, you should confirm if JWS is enabled on your system as a prerequisite.
- Customer September 13, 2020 at 6:08 pm
  I confirmed with our DBA; JWS is indeed not enabled. If we enable JWS for 12.2, are there any known issues with the jnlp files not being cleaned up after session timeouts?
- Support September 14, 2020 at 9:15 am
  The jnlp files should typically be deleted automatically after the session closes or times out. If cleanup issues persist, consult Section 6 of Using Java Web Start with Oracle E-Business Suite (Doc ID 2188898.1), which details browser user experience and configuration related to file cleanup.
- Customer September 14, 2020 at 5:35 pm
  We need to automate the launch task on the Mac OS desktop using a script, as described in some documentation. Can you confirm the simplest way to create this automation file (`open_forms.command`)?
- Support September 16, 2020 at 3:48 pm
  To automate the Forms launch on Mac OS, you would create a script file named `open_forms.command` on the Desktop. The recommended command typically uses a standard shell command like `touch open_forms.command` or a similar utility to create the file and populate it with the required JWS execution instructions for automation. However, ensure your DBA enables JWS first, as confirmed in your previous communication.
- Customer September 17, 2020 at 9:49 pm
  If we were to develop new reports, can we integrate them into these JWS-launched forms?
- Support September 19, 2020 at 10:25 pm
  Yes, Blitz Report provides specific guidance on How to add Blitz Report™ to your favorite form. This integration utilizes the underlying EBS forms technology, regardless of whether the form itself is launched via JWS, ensuring users have immediate access to highly formatted reports like those used for Supply Chain or Cost Accounting.
- Customer September 21, 2020 at 8:06 pm
  Is there a simple way to check if all the required EBS patches, potentially related to JWS or Forms, are installed after our recent 12.2 upgrade?
- Support September 22, 2020 at 4:21 pm
  You can use a custom Blitz Report based on the AD_PATCH.IS_PATCH_APPLIED function. This simplifies checking patch status quickly from the EBS forms interface, confirming if critical components related to JWS compatibility are correctly applied in your 12.2 instance.
Author
Replies