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.

Oracle jinitiator download windows xp