Common misconceptions about Oracle Forms on the Web

Many developers have misconceptions about Oracle Forms on the Web based on inaccurate data. This page will help you find out the real deal.

I have to re-write my Forms application to run on the Web.
Most Oracle Forms application can be moved to the web with minimal or no changes at all. Only a few features behave differently when you run on the web. These features and the way to address these issues are documented in the Oracle9i Forms Migrating from Client/Server paper.

I need to change my database to run on the Web.
When you move your application to the Web you are still using the same application that can use the same database. So there is no need to change the structure of the database. You can find out if the version of the database you are currently using is supported with the Oracle Forms version you are planning to deploy on the Web on http://metalink.oracle.com.

My Oracle Forms application will run slower on the Web.
The Oracle Forms Web architecture has been highly tuned in the years since it's debut. Most customers experience performance that is just as good, if not better, when running their applications on the Web. One example of where you can expect better performances is when you are storing FMX files on a network file server to simplify application management tasks. This creates a situation where each FMX that the user invokes needs to be downloaded to the client machine to be used by the local runtime. When deploying your forms on the Web, the FMX is not downloaded to the client and only minimal amount of metadata is transferred to the client reducing network traffic and improving performance. You will probably notice other improvements when your application transfers large amounts of data between the database and the Oracle Forms. Read more about Oracle Forms architecture in the Oracle9i Forms Services Overview paper.

Oracle Forms on the Web is not suitable for Wide Area or slow networks.
Oracle Forms on the Web has many built in features to minimizes its network traffic. Using a single Java applet to render any Form is one of the most network efficient solutions for rich and dynamic user interface on the Web. Many customers are running their clients over WANs and even using modems.

Oracle Forms requires big Java downloads
Oracle Forms uses a single Java applet to run Forms on the web. This applet needs to be downloaded to the client's machine only once, and it is cached for subsequent usage. So, after you invoked your first Forms application on the Web and downloaded this applet, you don't need to download Java anymore for any other Forms application that you'll run from that server.

Oracle Forms requires the installation of Jinitator on each client machine
Oracle Forms is certified to run with the native JVM of MS IE. More information on this is in the Oracle9i Forms Client Platform Statement of Direction paper.

Oracle Forms can't work through Firewalls or with SSL encryption
The new Oracle Forms Servlet architecture makes it very simple to work through Firewalls and with SSL encryption by using standard communication protocols. More information can be found in the Oracle9i Forms Services Overview paper

Developers need to learn Java to develop Oracle Forms on the Web.
Developers use the same PL/SQL based skills to develop Oracle Forms on the Web. Developers can use Java to enhance Forms application when running on the Web but this is not a requirement. More on this in the Oracle9i Forms in the Java World paper.

Oracle Forms on the Web can't activate components on the client machine.
Using the Java integration built into Oracle Forms you can actually add components to the form that integrate with the client machine. More on this in the Oracle9i Forms in the Java World paper.