Migrating Oracle Forms Applications to J2EE

27th July 2005

Oracle Forms Migration to J2EE

For a full statement on the migration of Oracle Forms to J2EE read the Oracle Forms Migration to Java Statement of Direction.

Frequently Asked Questions

  1. Do I have to move to Java because Forms is de-supported?

    No. There may be many reasons to move to a Java platform but this should not be one of them. Oracle has clearly documented the commitment to continue to develop, enhance and support Oracle Forms.

  2. Is Oracle telling me I must migrate my Forms applications to Java?

    No. The J2EE platform provides many opportunities you may want to consider. If you decide to use J2EE technologies you can do so while also integrating with your existing Forms applications. If you decide that you want all your applications in J2EE, or you need to move some existing Forms application to J2EE, then migration is one of a number of options.

  3. Should I migrate my Forms application to a Java Client application because client/server is de-supported?

    Not necessarily. While Oracle Forms is now a Web deploy only release, upgrade of client/server Forms to Forms on the web is a reasonably straightforward enough effort which many customers (including Oracle's own E-Business suite) have successfully achieved.

  4. Oracle has desupported Forms client/server but my application must run client/server

    If moving your client/server application to the web is not an option, and you require client/server or character mode deployment, then migration to J2EE technologies would give you the ability to deploy in a way that Oracle Forms no longer supports. In this case migration to J2EE may be worth considering.

  5. All our future development projects will be on J2EE. Should I migrate my existing Forms applications?

    If your business is moving to the J2EE stack you will be building up a pool of Java resources. It may make sense to move existing applications to J2EE to leverage these resources and to facilitate the integration with other systems. However, Forms has many features for easy integration with J2EE applications and you may consider maintaining existing Forms application and using these "hooks" to interface with your new J2EE applications.

  6. I need quicker startup times. Should I migrate to J2EE and build a Java Client UI?

    When you run ANY Forms application on the Web, a small number of class files are downloaded to the client. These class files are responsible for rendering the UI. Any subsequent evocation of a Forms application from that client will reuse the cached class files - thus, they are only downloaded once. When you run a Swing/J2EE application you will also have to download class files for that application. Depending on the deployment of your Swing/J2EE application, this download could in fact be the complete application. Running a different Swing/J2EE application will involve another download. Carefully consider the performance impacts of all solutions under consideration.

  7. I want to deploy my Forms application on the Web, do I need to move to Java?

    No. A Forms application can run client/server or on the Web using the same source code. Forms can be deployed on the Internet through firewalls and proxies.

  8. Should I migrate my Forms application to Java so I can have an HTML or mobile UI?

    There are many advantages to running with a lightweight HTML UI, as well as some limitations. If the requirements of your applications dictate a lightweight HTML UI then you might consider exposing some of your application in this way. You then have the choice of rewriting/migrating some of your applications to J2EE and integrating with the remaining Forms. Or you may consider rewriting/migrating all the Forms.

  9. Will it be more cost effective to migrate all my Forms application to J2EE or stay with Forms?

    The cost of writing, maintaining and deploying an application has many factors: cost of developers, runtime license, support etc. etc. Migration has both a cost and effect and should be fully factored before making a decision.

Back to the Oracle Forms Migration to Java Statement of Direction.