- #Oracle 6i for windows 10 install
- #Oracle 6i for windows 10 update
- #Oracle 6i for windows 10 download
There are no optional settings for Jinitiator. Modify the following settings to use a Jinitiator version different from the default if 1.3.1.26. Jpi_mimetype=application/x-java-applet jpi-version=1.6.0 Jpi_mimetype=application/x-java-applet jpi-version=1.6.0_22 #jpi_mimetype=application/x-java-applet jpi-version=1.4.2_06 Jpi_classid=clsid:CAFEEFAC-0016-0000-FFFF-ABCDEFFEDCBA Note the difference between these two settings. # Optional – Generic to any version of JRE 1.6.0. # This setting is specific to JRE 1.6.0_22 # Parameter related to the version of the Java Plugin
#Oracle 6i for windows 10 download
# New – points to the generic ( non-version specific) JRE download web site # (NOTE: you should check this page and possibly change the settings) # Sun's Java Plugin is typically used for non-Windows clients. # Page displayed to users to allow them to download Sun's Java Plugin. Personally, I find this to be the easier solution. You could also expand the existing section and instruct the Forms runtime to use this configuration in the URL. Therefore, to instruct the Forms Runtime to use the JRE without passing a URL query string parameter, it is recommended you change the “baseHTMLinitiator” parameter to point to the Java Plug-In (JPI) html file. Oracle Forms is hardwired (so to speak) to use the Oracle Jinitiator. # System parameter: base HTML file for use with JInitiator client The following settings are all found in the configuration section.
#Oracle 6i for windows 10 update
The following JRE changes instruct the Forms Runtime to use the JRE version 1.6.0 update 22 (1.6.0_22). Modify the following settings to use a JRE version different from the default if 1.4.2. Therefore, you will likely be installing the latest version of the Sun JRE which is Java 6 (1.6.0). Most likely, you will have to update the default settings as you likely do have the Sun JRE installer for 1.4.2 and it is no longer available for download.
#Oracle 6i for windows 10 install
If you decide to use the Sun JRE, again, you will need to install the appropriate version as the Forms Builder ships configured to a specific version of the Sun JRE. If you install the version found in your Oracle DevSuite home directory (\%DEV_SUITE_HOME%\jinit) you should be OK. For example, Oracle Forms 10g R2 (10.1.2.0.2) defaults to using Oracle Jinitiator 1.3.1.22.
Configuration is simply to install the Oracle Jinitiator (make sure you install the right version because each Forms version defaults to different version. By default, Forms Builder is configured to use the Oracle Jinitiator and in most cases this should be sufficient for your needs.
There are two Java Runtimes (JREs) supported by Forms Builder Oracle Jinitiator and the Oracle (Sun) Java Runtime Environment (Sun JRE). These two program items are the “Start OC4J Instance” and “Stop OC4J Instance.” Both are critical to the running of forms from the Forms Builder. In order to run a form from the Forms Builder, Oracle has included two new program items (among others) in Oracle Developer Suite Program group of the installed Oracle Developer Suite 10g. This is a very generic description of what OC4J is and what it does, but it will suffice for the purpose of this document. Forms 10g use the OC4J Forms Servlet to emulate a Forms Service web process on your workstation that allows you to “serve” a web form from the Forms Builder. This is not true it is just a little harder to do now and requires some configuration setup on your workstation to make it work. With the advent of Forms 9i – when Oracle made Forms web deployed only – many developers thought the ability to run a form from the Forms Builder was lost. This was a very nice feature that enabled you to perform incremental development and testing the Forms Debugger utility not to mention the Forms Runtime Diagnostics (FRD).
If you have used Oracle Forms long enough, you will remember the day when you could run a Form locally from the Forms Builder with the Forms Runtime.
0 kommentar(er)
