X

The Latest Technology Stack News Directly from EBS Development

Migrate to Java Web Start from Java Plug-In Now

Tahir Ahmad
Senior Director

Since we originally announced availability of Java Web Start for Oracle E-Business Suite 12.2 and 12.1 in April 2017 some developments have taken place. The bottom line is that we highly recommend all our Oracle E-Business Suite customers to migrate your Oracle E-Business Suite client tier to use Java Web Start (JWS) without delay.

Some of the recent expected developments that increase the importance of moving to Java Web Start include:

In addition to this, Oracle E-Business Suite has released the following:

Begin Your Migration to Java Web Start

My Oracle Support Note 2188898.1, Using Java Web Start with Oracle E-Business Suite contains details about how you can migrate an existing Oracle E-Business Suite 12.2 or 12.1 environment to use Java Web Start. This includes recently added support for multiple Oracle Forms sessions.

While you transition to Java Web Start, you may ask what happens if you encounter issues using the Java Plug-in with EBS?  For the answer to this and many other important Java-related questions, refer to My Oracle Support Note 2510500.1, FAQ: Essentials of Java Usage in Oracle E-Business Suite.

References

Related Articles

Join the discussion

Comments ( 8 )
  • Henry Monday, March 4, 2019
    This is Henry from Taiwan Support , My EBS customer concern about, Does it required buy extra java license fee?

    thanks.
  • Tahir Ahmad Monday, March 4, 2019
    Hello Henry,
    Thank you for your question on behalf of our customer.
    Moving from Java Plug-in to Java Web Start does not require any extra licensing. In fact, Oracle E-Business Suite customers are entitled to Java SE as explained in My Oracle Support Knowledge Document 2510500.1 (Question 20: Do I need to buy any specific Java SE licenses to use Java with Oracle E-Business Suite?).
  • Gopal Wednesday, March 6, 2019
    Hello Tahir,
    Java webstart is depreciated in Java 9 and will be removed from Java 11. Is EBS planning on moving to complete web application from a thick client(Applet/JWS) architecture ?

    Java road map:

    https://www.oracle.com/technetwork/java/javase/javaclientroadmapupdate2018mar-4414431.pdf
  • Tahir Ahmad [Oracle Development] Wednesday, March 6, 2019
    Gopal,
    Thank you for your excellent question. This is addressed in MOS document 2510500.1, "FAQ: Essentials of Java Usage in Oracle E-Business Suite" in the answers to the following two questions:
    2. Will Oracle E-Business Suite depend upon Java in the future?
    The short answer for the client tier is that we expect EBS to keep using Oracle Forms and hence keep using Java on the client tier.
    9. What future version of JRE (beyond JRE 8) will customers be able to use with Oracle E-Business Suite client tier?
    The short answer is that we expect EBS customers to use JRE 8 and Java Web Start for some time. EBS is not certified on JDK 11.

    We hope you find additional details in the FAQ useful.

    The future implications to EBS, of using Java on client tier without Java Web Start, are a topic of internal discussion for us. We will provide further guidance on this blog when our plans are more concrete.
  • James Friday, March 8, 2019
    Hi Tahir,
    We will be following your advice and migrating to JWS in the near future. However, the implication that we will no longer be able to open multiple EBiz forms from different instances (e.g. Test/Production) at the same time has dismayed many of our team. Is there any prospect of this being worked around somehow - could it be as simple as making the applet name dependant on the EBiz instance so this would be possible?

    James
  • Tahir Ahmad [Oracle Development] Wednesday, March 13, 2019
    Hi James,
    Thank you for raising this important question.
    As you and I have been discussing privately, our solution works with different instances i.e. it is possible to run multiple forms sessions simultaneously against test and production.

    Our MOS Note 2188898.1 will be improved to clarify this point, and update any existing wording that caused this confusion. We are tracking this internally via documentation bug 29475836 and will post an updated version of this MOS note once our review is complete.
  • Roberto Monday, March 25, 2019
    Hi Tahir,
    our customer is upgrading to eBS R12.2 right now,
    and start to use Java Web Start with JRE 8.
    He have other applications using JRE
    so he want to know the future support plan
    for the next JRE release,
    and is an hard sentence to say (until now):
    "Oracle have no plan to support JRE other than JRE 8!"
    Is possible to have more details in how,
    and when Oracle will plan to replace JWS or JRE 8 for eBS?
    Best Regards
    Roberto
  • Tahir Ahmad [Oracle Development] Monday, March 25, 2019
    Hi Roberto,

    Thank you for your question.

    If you haven't already, please review answers to the following questions in our recently published My Oracle Support Note 2510500.1: FAQ: Essentials of Java Usage in Oracle E-Business Suite.
    https://support.oracle.com/rs?type=doc&id=2510500.1

    7. Given that Oracle E-Business Suite Release 12.2 is supported through to at least 2030, what should Oracle E-Business Suite customers do after Java SE 8 extended support ends in 2025?
    9. What future version of JRE (beyond JRE 8) will customers be able to use with Oracle E-Business Suite client tier?
    17. Can I use multiple JRE versions to access different Oracle E-Business Suite environments from the same user's desktop? What about systems other than Oracle E-Business Suite that require a version of Java other than 8? (Scenario 2 or Scenario 3 may apply to your customer at the moment)

    The future implications to EBS, of using Java on client tier without Java Web Start, are a topic of internal discussion for us. We will provide further guidance on this blog when our plans are more concrete.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha