However, if you run a shop like ours, where multiple users could possible have multiple versions of Java, and updating the Java version on the Application server is not an option, there is a fix in MOS 393931.1 that will help.
Under the Known Issues section, and then under the Forms Launch Issues heading, is the following helpful piece of information:
3. Different Users run different JRE Releases from Multiple JRE Streams
Here you will find the setting for your appsweb.cfg file that will tell the Application Server to not attempt to install Java if the client PC has ANY version of Java installed. Simple replace the setting as indicated in the document, and the client PCs will pick up the information the next time they attempt to access Oracle Forms.
Of course, since appsweb.cfg is a file that is rewritten by autoconfig, this setting will need to be changed in the autoconfig process in order that it be rewritten properly should you need to autoconfig your EBS instance.
This part, which is covered in MOS 387859.1, is documented well for how to actually change the setting...but not for where to FIND the file containing the setting to be changed. I guess it should have occurred to me, a relative DBA newbie, that the file required is the Context file. It didn't occur to me, so I did it the old fashioned way - I opened $ADMIN_SCRIPTS_HOME/adautocfg.sh and looked inside to find the file.
Of course, there it was right near the top:
CTX_FILE="<$INST_TOP>/appl/admin/<SID>_<SERVER_NAME>.xml
No comments:
Post a Comment