Oracle E-Business Suite Technology

I'm very pleased to welcome Sanchit Jindal to this blog's ever-growing ranks of guest authors.

Sanchit Jindal is a Project Lead and Database Administrator in my Applications Technology Integration group. Sanchit spends the majority of his time on new technology integration certifications with Oracle E-Business Suite releases.

Sanchit has been with Oracle since 2004. He has 7 years of experience in the software industry with overall experience spanning more than a decade including Business Development. He has worked as a production DBA during his consulting days.

Prior to joining Oracle, Sanchit has worked for Yamaha India, IRIS Software and other companies. Sanchit holds a Bachelors degree in Electronics and Communication Engineering and is an Oracle Certified Database Administrator.

Sanchit works at Oracle India located in Hyderabad, India.

With the onward march of progress, I would like to draw your attention to the newly-published Obsolescence notice for JInitiator 1.3 for E-Business Suite 11i (Metalink Note 552692.1).

As of July 31, 2009 Error Correction Support for JInitiator 1.3 will end.  In other words, the Oracle Forms group will no longer issue bug fixes via new versions of JInitiator 1.3.x as of July 31, 2009.

What Do You Do Now?

You need to start the upgrade process for your end-users' desktops to the native Sun Java plug-in as soon as possible.  This extract from note 552692.1 sums it up well by stating :-

All E-Business Suite customers using Oracle Jinitiator 1.3.x need to upgrade to the Sun JRE (Native Plug-in). Oracle highly recommends that EBS customers upgrade to the latest certified version of the Sun plug-in by following Metalink document 290807.1, "Upgrading Sun JRE(Native Plug-in) with Oracle Applications 11i"

Why Choose the Native Sun JRE Over JInitiator?

Nearly every business desktop has multiple Java clients installed.  These Java clients often clash; see this article for a more in-depth discussion about JRE conflicts.  The main benefit of switching from JInitiator to the native Sun Java plug-in lies in reducing  conflicts between these clients on your desktop.

In addition, Steven's previous blog article elegantly describes the reasons why Oracle is moving to using the native Sun Java plug-in in favour of JInitiator:

Oracle JInitiator was originally released as a licenced version of Sun's Java client back when specific features were required to support Oracle Forms.  This was particularly necessary for E-Business Suite Forms-based functionality, since the E-Business Suite pushed the envelope of what Forms and Java could do collectively from a user interface perspective.

Sun has since incorporated all of the enhancements needed to support Oracle Forms into their native Sun Java plug-in.  As a result, the Oracle JInitiator team is pleased that they can get out of the business of maintaining and repackaging Sun's Java client code. 

Oracle's emphasis from this point forward will be to certify future versions of the Sun Java client with the E-Business Suite. 

Related

• Upgrading Sun JRE (Native Plug-in) with Oracle Applications 11i for Windows Clients (Metalink Note 290807.1)
• Replacing JInitiator with Sun Java Plug-in 1.5.0_13 (Metalink Note 393931.1)
  
• Running Multiple Java Plug-Ins on the Same Windows PC