Replacing JInitiator with Sun JRE in 11i

Transcription

1 E-Business Suite 11i Replacing JInitiator with Sun JRE in 11i Michael Brown Colibri Limited PO Box 1844, Roswell, GA 30077

2 1 DOCUMENT CONTROL MICHAEL BROWN COLIBRI LIMITED VERSION CONTROL & DISTRIBUTION ACCURACY COPYRIGHT ABSTRACT INTRODUCTION PREREQUISITES INSTALLATION AND CONFIGURATION BUT I AM STILL USING DISCOVERER 4I CONCLUSION REFERENCES...10 Page 2 of 10

3 1 DOCUMENT CONTROL This document was prepared by: 1.1 MICHAEL BROWN COLIBRI LIMITED All questions concerning this document should be directed to Michael Brown. 1.2 VERSION CONTROL & DISTRIBUTION Version: Date: Amendment: Distribution: 1 February 27, 2008 Document Created Michael Brown 1.3 ACCURACY COLIBRI endeavors to ensure that the information contained in this document is correct, and whilst every effort is made to ensure the accuracy of such information, we accept no liability for any error or omission in the same. 1.4 COPYRIGHT The information contained in this document is the joint copyright of Michael Brown and COLIBRI LC. The information may be distributed as long as this note is reproduced in its entirety. Page 3 of 10

4 2 ABSTRACT Oracle has certified the use of Sun JRE 1.5 with EBS 11i. However, this is not as straightforward as it sounds if you still require the use of JInitiator (for example with Discoverer 4i). This presentation with review how to convert to use JRE in combination with JInitiator as well as impacts that using both Java environments can have on patching and cloning.. Page 4 of 10

5 3 INTRODUCTION Until recently, users of Oracle Forms had to use Oracle JInitiator as the Java run time engine because Oracle Forms required enhancements to the standard runtime. As of Java 1.5, those enhancements have been incorporated into Sun s standard release. Oracle has made the transition from JInitiator to JRE a fairly painless process until you find that you have a reason that you still need to be using JInitiator (such as the fact that you have never upgraded your Discoverer from 4i). As of February 8, 2008, Oracle has upped the ante for people recent to switching from JInitiator with the announcement that support for JInitiator with 11i ends on July 31, Why should you want to make the change now (or ever, as already pointed out, people are still using Discoverer 4i). Oracle JInitiator has known conflicts with Sun Java2 Standard Edition. If all you are using is the Sun JRE, this problem is eliminated. Managing multiple Java Virtual Machines (JVM) on a desktop can be complex and result in extra work for both the end users and the desktop support team. When you remove JInitiator in favor of the standard Sun JRE, you simplify the support issues. Another reason for setting up the EBS to use the Sun JRE (although one not certified by Oracle) is that you may be able to run the E-Business Suite directly from your server. This can be a huge advantage when you need to troubleshoot an issue. Metalink Note is regularly updated. The prerequisites and procedures described for upgrading your EBS are consistent with the certifications as of February 28, Review the Metalink Note for changes before beginning work on your system. Page 5 of 10

6 4 PREREQUISITES Depending on your client OS, there are different prerequisites for the EBS application tier. Microsoft Windows XP SP2/Microsoft Windows 2000 EBS or later Oracle Developer 6i Patchset 18 ( x) or later Autoconfig enabled Microsoft Windows Vista EBS CU 2 with ATG RUP 4 or EBS CU2 with ATG RUP 4 Oracle Developer 6i Patchset 18 ( x) or later Autoconfig enabled The matrix becomes even more complex when you are forced to look at the version of the browser and the OS. Browser Version Windows Vista Windows XP SP2 Windows 2000 JRE 1.6.0_03 or later JRE 1.6.0_03 or later Internet Explorer 7 Not Certified JRE 1.5.0_12 or later JRE 1.5.0_12 or later JRE 1.6.0_03 or later JRE 1.6.0_03 or later Internet Explorer 6 Not Certified JRE 1.5.0_12 or later JRE 1.5.0_12 or later JRE 1.6.0_03 or later Firefox 2.0.x Not Certified Not Certified JRE 1.5.0_12 or later Firefox 1.5.x Not Certified JRE 1.5.0_12 or later Not Certified Even though JRE 1.5.0_12 is certified, it still has some problems in with Oracle Forms. You should treat JRE 1.5.0_13 as the minimum version to use in a production environment. Since the majority of users are on or higher and using XP, the only prerequisite we will review is the Developer 6i patch. Download Developer 6i Patch 18, , and the interoperability patch, Download the platform dependent patches. For Linux, they are , , , , , plus two interoperatibility patches for Linux and Stop the applications tier processes, especially forms, reports, http and the concurrent managers Install the developer 6i patch (read the special instructions if your install was created with or earlier) Install the additional patches in order being careful to follow the instructions contained in each patch. Relink f60webmx, ar60run, ar60runb and ar60rund using adadmin Apply the interoperability patch Verify the upgrade o Fndforms.jar and fndewt.jar should have been rebuilt o f60gen help=y should show a version of x Restart the applications tier Page 6 of 10

7 5 INSTALLATION AND CONFIGURATION Assumption: You will be installing a version of JRE 6 Oracle has done us all a favor and developed a common interoperatibility patch for using the Sun JRE. So our first step will be to download patch The next step will be to download the desired version of the Sun JRE from For JRE 6, the full URL is Download the Windows Offline Installation version of Java Runtime Environment (JRE) 6 Update X (where X is the current version). The file that you downloaded will be named something like jre-6_ux-windows-i586-p.exe, you will need to rename it to j2se160x.exe. Copy this file to $COMMON_TOP/util/jinitiator on the applications tier. There is a remaining bug in Developer 6i Patchset 18 that affects the forms focus, so at this point you should download and install patches, and This should be fixed in the upcoming Developer 6i Patchset 19. You now can apply the JRE interoperability patch. After applying the patch driver, we will use the script txksetplugin.sh to tell the EBS which JRE to use by default. To verify your upgrade, make sure that the java console is enabled on the PC you will use for initial testing. When you first launch a form, the java console should open and show you that the Java Plug-in version matches the default version you set on the server with txksetplugin.sh. Here is also where you will see why your desktop support team will not be happy with you at first, everyone will get a security warning the first time they open a form (make sure they know to check Always trust content from this publisher or they may get the warning again). Page 7 of 10

8 6 BUT I AM STILL USING DISCOVERER 4I In order to use Sun JRE, you must be running Discoverer 10g (9.0.4) or higher. Oracle has provided us with a workaround for this problem. We can add multiple versions of JRE and/or JInitiator to the instance. The downside of this is an increase in complexity when using Autoconfig and when cloning. The first step is to revert your installation back to JInitiator since we can configure how forms are launched, but Discoverer 4i must use the default plug-in. You need to run txksetplugin.sh again. Give the version of the JInitiator as the argument, e.g. for JInitiator , you would give the command txksetplugin.sh You can now configure the additional JRE plug-in. You do this by editing the appsweb.cfg template located in $FND_TOP/admin/template, so step 1 is backup the original file. At the bottom of the file, you will find [myextensions], add the new plug-in here. For example, for JRE 1.6.0_03 you would add: [J16003] connectmode=socket serverport=9001 sun_plugin_classid=clsid:cafeefac abcdeffedcba sun_plugin_version=1.6.0_03 sun_plugin_url= sun_plugin_mimetype=application/x-java-applet:jpi-version=1.6.0_03 sun_plugin_legacy_lifecycle=false plugin=jdk ; In order to apply the change, you must run autoconfig. To change the default behavior for forms, edit the site level profile ICX: Forms Launcher and add?config=j16003 to the end of the URL, e.g. Note: every time you run autoconfig, this profile will revert back to the default. To switch it back from the forms (and still be using the Sun JRE), you may wish to also set the profile option at the USER level. To be able to use Discoverer 4i and Forms simultaneously, you must be using IE as your browser. And now you have introduced the next issue. You cannot launch forms from any account that you have set the ICX: Forms Launcher below the SITE level. Those profile options will not be updated during the configuration of the clone, so the URLs will still point at the source of the clone. Also, the template for appsweb.cfg has hard coded hostnames. The correct version of the template should be copied into place (or edited), prior to running adcfgclone.pl for the applications tier. Page 8 of 10

9 7 CONCLUSION As you have seen, converting your EBS 11i install from JInitiator to Sun JRE is a relatively easy and painless process. However, additional steps may need to be added to your cloning process as a result of this upgrade. Page 9 of 10

10 8 REFERENCES Metalink Note , Oracle JInitiator 1.3 for E-Business Suite 11i Forms Version x Metalink Note , Upgrading Sun JRE (Native Plug-in) with Oracle E-Business Suite 11i for Windows Clients Metalink Note , Upgrading Developer 6i with Oracle Applications 11i Page 10 of 10