The Latest Technology Stack News Directly from EBS Development

Updated Tips for Debugging Sun JRE + Forms Focus Issues for EBS 11i and 12

Steven Chan
Senior Director

Oracle Jinitiator 1.3 will be desupported for Oracle E-Business Suite Release 11i users at the end of this month, July 31, 2009.  If you haven't already begun your conversion from JInitiator to the native Sun Java Runtime Engine (JRE) plug-in, now is the time to start. 

The end of this month marks the end of the JInitiator era for Apps 11i.  After this point, we will only support the Sun JRE for Forms users connecting to the E-Business Suite.  I've summarized everything you need to know about the EBS switch from JInit to the Sun JRE in this roundup article.

Sun Java Website screenshot Screencap of Sun's Java SE website

Clusters of Common Focus-Related Issues

As more of you make the cutover, we've seen that your reported issues are clustering around some common themes.  Based on your feedback and reported issues, we've updated our internal training for all Support engineers who cover Applications Technology topics.  Our latest diagnostic and debugging techniques for EBS Forms focus-related issues have been refreshed. 

Our Support and Development teams published notes for diagnosing Forms focus-related issues with Apps 11i earlier this year.  That troubleshooting guide's scope has been broadened to include additional guidance and tips for Oracle E-Business Suite Release 12 environments, too:

The latest topics covered in this Note include:

  • What is a focus issue?
  • Why are Focus Issues Experienced?
  • Symptoms Indicating a Loss in Focus
  • Strategy for Investigating and Resolving Focus Issues
  • The Right Checks to Ensure it's a Focus Issue
  • Fixing Known Focus Issues
  • Determining the Current Forms Version and MLR Patch (Release 11i)
  • Determining the Current Forms Version and MLR Patch (Release 12)
  • Gathering the Right Information
  • Debugging Steps for Focus Issues
  • Reporting a Focus Loss to Oracle Support Services

Getting Support from Oracle for Your Conversion

I've noted this before, but it's worth repeating. We're very interested in helping you get through this conversion with a minimum of pain. If you hit any problems with your Apps conversion to the native Sun JRE plug-in, please log a formal Service Request via Metalink. Our Support engineers will work with you on this, and also track the underlying issues to see whether changes to our documentation or patches are warranted. If necessary, we'll work with Sun to get fixes prioritized for future JRE releases, too.

Given my position in Oracle Development and the visibility of this blog, I sometimes think that my perspective on customer deployments might be a little skewed.  I'd appreciate your help in getting an accurate view of how these conversions are going for you. I'd be very interested in hearing about your experiences, good or bad. What went well? What went sideways? Please feel free to sound off in the comments or drop me a private email with more details about your migration.

Related Articles

Join the discussion

Comments ( 40 )
  • Vikram Das Thursday, July 23, 2009

    Hi Steven,

    We have been facing forms focus issues after going on Dev 6i patchset 19 since Feb 2009. The issues are difficult to reproduce, but we have recorded it using "Demo it to Oracle" program. We are on Jinitiator Oracle support has steadfastly pushed back all our requests to investigate the matter and are forever suggesting us to upgrade to latest Sun JRE plugin. When we logged SR with them in March they were recommending upgrade to 1.6.0_10 and now they are recommending 1.6.0_14. It is obvious that they are waiting for July 31, 2009 when Jinitiator will be obsoleted. After that they can officially say that Oracle doesn't support Jinitiator.

    However upgrading JRE in our environment is not so simple. There are hundreds of applications dependant on JRE and simply upgrading it may break many of them. Our desktop team is doing a year long project to bring all applications on JRE 1.6. Till that is done, we can't really migrate from Jinitiator to Sun JRE.

    The attitude of Oracle support regarding this matter is no good.

    - Vikram

  • Steven Chan Monday, July 27, 2009

    Hi, Vikram,

    Thanks for sharing this with me.

    I'm sorry to hear about your experiences with Oracle Support. Sun continues to release new JRE versions to address focus-related issues, which might account for some of the continued suggestions to go to yet-another JRE version.

    Can you email me the SR number? I'd like to have someone look into this.



  • OptimisticDBA Tuesday, July 28, 2009

    Oracle Jinitiator 1.3 will be desupported for Oracle E-Business Suite Release 11i users at the end of this month, July 31, 2009.

    ==> Is the above statement true for those having 11i EBS extended support? Could you please clarify.


  • Steven Chan Tuesday, July 28, 2009

    Hello, OptimisticDBA,

    Yes, this statement is true for those having 11i EBS extended support. JInitiator's desupport date is independent of EBS 11i's support windows.



  • Jennifer Chen Monday, September 14, 2009

    Hi Steven,

    Our overall experience of migrating to the native Sun JRE plug-in was very positive because we had different organizations managing users' desktops and application servers. The coordination needed to deploy a newer JRE version is now much easier than the coordination required for upgrading JInitiator/managing certdb file, etc.

    I have exchanged a few emails with you on the Forms Mouse Focus issue that we encountered after upgrading to the "next generation Java" in 1.6.0_10 and higher. After reviewing the note highlighted in this article along with the notes they refer to, we applied the latest MLR form-focused patch at the time, followed up with users, and the frequency of the problem was significantly reduced (occurred twice within 6 weeks reportedly, e.g.)...

    In note 760250.1, it states: "Generate product JAR files'. It will be best to use the Force option to make sure all JAR files are refreshed". I would suggest adding this in the patch README file in the future because running adadmin by default:

    Do you wish to force regeneration of all jar files? [No]

    I have seen consultants/DBAs usually just pick default. When we apply the form focused patch, we review README, not necessarily note 760250.1. I meant to provide the feedback sooner, but checked the note: 290807.1 and found out the newer form focus patch is available again. I have asked Metalink if we can subscribe to notes that require our actions and are relevant to our installations and am waiting for a confirmation from Metalink.

    Hope this helps.


  • Steven Chan Wednesday, September 16, 2009

    Hi, Jennifer,

    This is very helpful. Thanks very much for taking the time to summarize your experiences here.

    Our patch READMEs are automatically-generated, but I'll look into how we can emphasize the JAR file refresh recommendation in our EBS JRE installation documentation. Great tip!



  • Andy Katz Wednesday, October 21, 2009


    Nice to meet you in person at OOW last week.

    Sandra V. (our DBA) and I upgraded our EBS to JRE following note 290807.1.

    However, previous versions of this note (and note 393931.1 for r12) mentioned Static vs Non-Static provisioning. The current release of the note 290807.1 for 11i users no longer has this Appendix.

    It appears that we are stuck with a static provisioning model in 11i, based on our test installation. The test PC had JRE1.6.0.15 loaded. First time login into a forms session following the update forced me to download the JRE1.6.0.16 plugin (the version we loaded into the web server per the Metalink note). This behavior occurs whether using Firefox 3.5 or IE 8.

    Is it true that static/non-static provisioning is no longer supported in 11i? Can you shed any light on this?

    Best regards,

    Andy Katz

  • Steven Chan Wednesday, October 21, 2009

    Hi, Andy,

    It was good to see you at OpenWorld last week.

    I'm not sure I understand your question about our documentation. Both Notes still include an Appendix A, "Static vs. Non-Static Version and Set Up Options" sections. These have not been removed, and static versioning is still supported.

    If you can't see them in Metalink, I'd suggest using a different browser such as Firefox. Some versions of IE truncate long Metalink Notes for mysterious reasons.



  • Andy Katz Wednesday, October 21, 2009


    Well, what do you know? This is odd:

    IE8, using My Oracle Support: can log in, search for 290807.1, click on the link and the frame opens, but remains blank.

    IE8, same scenario, using "Compatibility View" feature: doc doesn't load at all.

    IE8, using "Return to Classic Metalink": doc shows, WITH the Appendices as you described.

    Firefox 3.5.3: My Oracle Support, frame with doc loads, but clicking on APPENDICES link has no effect. Manually scrolling through the document: no appendices headings, although some of the appendices data is there (I found Appdx B info, but no Appdx A stuff at all).

    Thank you for pointing this out--I guess to make non-static work, I would best load a lower version of the JRE into the web server (as long as it's not any lower than the 1.6.x family that's on most of our desktops), not the latest/greatest called for in the document.



  • Steven Chan Thursday, October 22, 2009

    Hi, Andy,

    Weird. Browser + Flash oddities are the bane of my existence. I know it might be a bit of a pain, but I'm pretty sure that our My Oracle Support team would be interested in trying to fix the browser+MOS issues that you encountered. If you're willing to work through that, it would be great if you could log a Service Request to get one of our My Oracle Support developers engaged.

    Good luck with your JRE deployments. Please drop me a line with an update on how that goes for you.



  • Andy Katz Monday, October 26, 2009


    Opened SR 7773673.993 as you suggested. Will let you know how it works out.

    As for the deployment, apparently some of the client-side issues for Firefox are patched, but only if apps is on ATGRUP6 or better, which is a whole other project Sandra and I are working on. Her thinking is to tack the JRE project to the ATG RUP update. My thinking is that I could do the JRE update and just have users consolidated on a single browser (IE, v7 or 8) as it allows non-static provisioning out of the box, so we don't have issues of client-side updating of the Java component.



  • Steven Chan Tuesday, October 27, 2009

    Hi, Andy,

    Someone on our My Oracle Support team has confirmed that the "Note truncation issue" is a known problem with IE8. This theoretically will be fixed with the upcoming refresh of My Oracle Support early next month. We'll see.

    Good luck with your ATG RUP upgrade, too. I'd be interested in hearing how that goes.



  • Larry L Wednesday, October 28, 2009

    I'm having problems with a JRE upgrade and wondering if you can help. The environment is: 3 servers - 1 concurrent processing node, 1 admin/forms node, and 1 web node. Before the upgrade, everything worked perfectly. After the upgrade to 1.6.0_16, the forms won't open. I click on a link that should open a form, but it does nothing. I did this upgrade a month ago and it worked fine - the only difference then was that the forms server was on the web server node. This time they are separate. Any ideas?