Oracle's Forms Strategy - Does it exist? ODTUG 2005 Wrap Up (part 1) 20188367001

Oracle's Forms Strategy – Does it exist? ODTUG 2005 Wrap Up (part 1)

I do not understand Oracle’s strategy with regard to Oracle Forms. If such a thing really exists. Oracle has made it very clear that Development Tools are only considered ‘enablers of run time licenses’. So Oracle only sells us development tools – probably far below cost price – to keep us buying Oracle RDBMS and AppServer licenses. And the development tools are hanging around anyway because Oracle Apps needs them to develop the E Business Suite.

It is perfectly possible to develop applications using JDeveloper and deploy them on any Application Server. AMIS has been deploying application built using JDeveloper in web servers and application servers like Tomcat and WebSphere. And these applications can make use of any JDBC Driver enabled database, such as MySQL, DB2 or SQLServer. So clearly, hooking us onto JDeveloper is by no means a guarantee for selling run time licenses.

On the other hand, anyone building applications using Oracle Forms is certain to use the Oracle RDBMS for deployment. And with WebForms also the Oracle Application Server for middle tier infrastructure. So the easiest way to continue selling licenses it to make darned sure that existing Forms customers are not cut loose from Forms, moving to JDeveloper and essentially being free to choose any Application Server and any Database.

All Oracle would have to do for this, is send out a clear message. That it is and stays committed to Oracle Forms. That Oracle Apps will use Forms for quite some time to come. That investments in new functionality will continue to be made – even if these are small investments.

And it should not certify partner solutions for migrating away from Oracle Forms, especially if such a migration is to an far more uncertain architecture. It is quite unclear whether certification of partners like Churchill, NIOS and CipherSoft suggests that Oracle actually endorses these solutions, actually actively recommends its Forms customers to move away from Forms.

In my opinion, organizations currently using Forms, having the skills available, that are going to develop intra-net applications for intensive use, should definitely go on using Oracle Forms.

Forms is not a very suitable tool for developing internet web applications. Forms is not ideal for self-service style applications, that are only very infrequently used by relatively unskilled end-users. In those instances, build an HTML user interface on top of a Java middle tier. That is where ADF and JDeveloper typically come in.

It seems unlikely, especially given the uncertainty surrounding Forms, that any new customers will start using Forms, although I have heard stories about companies doing some exactly that in the recent past. And I would say: why not? The benefits of tight integration with the database, the very high development productivity, the leveraging of existing server side SQL and PL/SQL skills combined with the administrative benefits of web-deployment as well as the recent integration option with J2EE applications make Forms still a strong candidate in many development tools selections. The Development Tools race that was recently held in The Netherlands saw the classic Oracle tool stack – Designer and Forms – finish in second place, well ahead of Java and especially .Net based solutions. (the number one by the way was Magic).

Forms to J2EE migration tools, such as Churchill’s JAutomator and Ciphersoft, do not seem to be getting a lot of traction. I would say: if you do not like Forms, do not migrate to something that exactly looks like Forms – even though it is J2EE technology, it is definitely not architectured and maintainable the way a typical J2EE application would or should be. The only reason I could think of doing it like this is when upper management for some reason wants to get off Oracle technology fast! If you like your Forms, do not migrate! If you do not like Forms anymore, do not migrate using a tool that will give you something very similar to Forms.

Forms will be around for many years, if only because of the Oracle Apps base. A quick inventarization of the current status and ongoing developments within Apps – investigations into ADF, merger with PeopleSoft, evaluation of People Tools and building of Fusion Vision – suggests that it will take up to 5-7 years before there might be an Apps release without any Forms technology. Then support for Apps releases that contain Oracle Forms will run at least until four years after that. So I do not think Forms is really going to fade away before 2015 or so.

Forms 10gR2 will see some improvements: a JavaScript API for calling into a Form and a JVM pooling mechanism that makes it much more feasible to implement Java callouts on the middle tier. That means that integration of Forms with J2EE APIs is becoming much more of a reality. The JVMs will be preloaded, so any Form Instance requiring a JVM for doing some Java integration can get hold of it instantly. Note that there will be a substantial memory footprint associated with these JVMs.


  1. Manjit Kumar July 5, 2007
  2. Rajanikanth December 28, 2005
  3. Lucas Jellema December 15, 2005
  4. Grant Ronald October 9, 2005
  5. Ashish Ranjan October 5, 2005
  6. Grant Ronald August 2, 2005
  7. Grant Ronald July 13, 2005
  8. Grant Ronald June 28, 2005