Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Problem: Can both JRE and JInitiator used for e-Business suite and how?
Solution:
You make 1 default (JRE or Jiniator) and use the other one via the config parameter in the Forms launch URL.
It is recommended that either JRE or a single version of JInitiator is used to access a single Oracle E-Business Suite instance.
Note: JRE1.6.0_10 and higher uses 'patch-in-place' mode when installling higher releases by default. This means that the new install will patch into the same directory that the old version used, overwriting it. To maintain multiple versions with these releases requires install using 'static' mode'. For further information please see the Java Runtime Environment Windows Installation for JavaSE 6u10 link in the plug-ins release notes.
There may be occasions where it is desirable to test and compare changes in functionality or security across different plug-in versions in a test system. Users may access the same Oracle E-Business Suite instance using different JRE client plug-in versions from separate desktop clients with certain exceptions as outlined below.
Discoverer 4i Users
Discoverer 4i users cannot use multiple JRE plug-in versions to access the same E-Business Suite instance. Only the default plug-in version set for that particular Oracle E-Business Suite instance can be used.
Workflow Users
Workflow users running Oracle E-Business Suite 11i with 11i.ATG_PF.H.RUP3 (patch 4334965) and earlier cannot use multiple JRE plug-in versions to access the workflow applet in the same Oracle E-Business Suite environment. In earlier releases the JRE plug-in version is called from the WF_RESOURCES table which only holds the values for the default JRE plug-in version for that particular environment.
Note: This will only affect Workflow users when accessing any area of the product that connects through the applet i.e. if viewing a 'Status Diagram' through 'Status Monitor'. This will not affect users simply initiating a workflow through an HTML product as this would not use the JRE plug-in.
Workflow users running Oracle E-Business Suite 11i with 11i.ATG_PF.H.RUP4 (patch 4676589) or higher may access the same Oracle E-Business Suite instance using different JRE client plug-in versions from separate desktop clients. After this release the WF_RESOURCES table is no longer used, instead the java plug-in version is called from the appsweb.cfg file on the application server.
JRE and JInitiator plug-in versions can coexist and also be run simultaneously on the same desktop client, if All of the following conditions are true:
* Internet Explorer is being used
* Each JRE/JInitiator instance is started in a separate Internet Explorer session
Note: The mixing of different plug-in streams in this way should not be used on production systems as JRE fixes may not always be backward compatible with the old JInitiator technology. Java 1.3 which JInitiator 1.3.x is built upon is also no longer supported by Sun.
Firefox Browser
If using a Firefox browser, it is not possible to run multiple JRE/JInitiator versions simultaneously from the same desktop client. These browsers use a single cookie session which restricts usage to a single Java version per desktop client at a time. To access environments using different JRE/JInitiator versions from the same desktop client, the previous browser session must be completely closed down and a new one started before running another JRE/JInitiator version. You may still access the same Oracle E-Business Suite environment simultaneously using different JRE/JInitiator versions, but only by using separate desktop clients.(Each desktop client would use a specific JRE/JInitiator version).
Adding Additional Java Plug-in Versions
The txkSetPlugin script outlined in Apply the Interoperability Patch section above, is only run for the version of JRE/JInitiator that you wish to have as your default Plug-in.To add additional JRE/JInitiator versions, follow the steps below.
Adding a JRE Version
Using JRE 1.5.0_13 as an example.
1. Copy the j2se15013.exe file to your $OA_HTML directory to allow user download of the plug-in at runtime. (The sun_plugin_url parameter below denotes the plug-in file name and download directory).
2. Take a backup copy of your original $FND_TOP/admin/template/appsweb.cfg file.
3. Add the following information under [myExtensions] at the bottom of your $FND_TOP/admin/template/appsweb.cfg file.
(substitute the environment values as appropriate to your own environment. The connectMode and serverPort settings can be copied from your 'appsweb' file as required.)
[J15013]
connectMode=socket
serverPort=9001
sun_plugin_classid=clsid:CAFEEFAC-0015-0000-0013-ABCDEFFEDCBA
sun_plugin_version=1.5.0_13
sun_plugin_url=http://ap123.us.oracle.com:8001/OA_HTML/j2se15013.exe
sun_plugin_mimetype=application/x-java-applet;jpi-version=1.5.0_13
sun_plugin_legacy_lifecycle=false
plugin=jdk
;
4. Enter the forms URL against the ICX: Forms Launcher profile at user level for the appropriate E-Business Suite user. (If required, you may set up a new user through the System Administrator Responsibility for this). In this example, logging in as this user will cause JRE 1.5.0_13 to be used as the plug-in instead of the default version.
The name you used in the update above under step 3, ie [J15013] must be referenced as the 'config' parameter like the example below:
http://ap123.us.oracle.com:8001/dev60cgi/f60cgi?config=J15013
5. Run autoconfig to filter the changes through to the runtime version of appsweb.cfg.
Adding a Jinit Version
Using jinit 1.3.1.30 as an example.
1. Copy the jinit13130.exe file to your $OA_HTML directory to allow user download of the plug-in at runtime. (The jinit_name parameter below denotes the plug-in file name and download directory).
2. Take a backup copy of your original $FND_TOP/admin/template/appsweb.cfg file.
3. Add the following information under [myExtensions] at the bottom of your $FND_TOP/admin/template/appsweb.cfg file.
(substitute the environment values as appropriate to your own environment. The connectMode and serverPort settings can be copied from your 'appsweb' file as required.)
Example 1 using socket mode:-
[J13130]
connectMode=socket
serverPort=9001
jinit_name=jinit13130.exe
jinit_classid=clsid:CAFECAFE-0013-0001-0030-ABCDEFABCDEF
jinit_ver_name=Version=1,3,1,30
jinit_mimetype=application/x-jinit-applet;version=1.3.1.30
plugin=jinit
;
Example 2 using Formservlet mode:-
[J13130]
serverURL=/forms/formservlet
jinit_name=jinit13130.exe
jinit_classid=clsid:CAFECAFE-0013-0001-0030-ABCDEFABCDEF
jinit_ver_name=Version=1,3,1,30
jinit_mimetype=application/x-jinit-applet;version=1.3.1.30
plugin=jinit
;
4. Enter the forms URL against the ICX: Forms Launcher profile at user level for the appropriate E-Business Suite user. (If required, you may set up a new user through the System Administrator Responsibility for this). In this example, logging in as this user will cause JInitiator 1.3.1.30 to be used as the plug-in instead of the default version.
The name you used in the update above ie [J13130] must be referenced as the 'config' parameter as below:
http://ap123.us.oracle.com:8001/dev60cgi/f60cgi?config=J13130
5. Run autoconfig to filter the changes through to the runtime version of appsweb.cfg.
References:
Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i [ID 290807.1]
No comments:
Post a Comment