Info required on Jheadstart

Question

Hello All,
We need to migrate an application developed in oracle Forms to J2EE migration using Oracle-ADF. Major functionalities developed
using Oracle forms and Java Swing.
We need some input regarding
1)Pro and cons of Jheadstart as a migration tool.
2)Licence details
3)Support on new releases of tool
4)Any link where we can download the trial version and do an evaluation ( Compartible with Jdeveloper 11.1.1.4.0.)
5)Is there any user training provided in Oracle for Jheadstart
6)For purchase provide the contact details/link
Regards,
Lokanath Giri

Answer 1

Lokanath.
I suggest you start with going to the Jheadstart product center at
http://www.oracle.com/technetwork/developer-tools/jheadstart/overview/index.html
You can download the evaluation version there, or through JDeveloper -> Help -> Check for Updates -> Open Source and Partner Extensions Update Center.
There is also a link to the FAQ there:
http://www.oracle.com/technetwork/developer-tools/jheadstart/jheadstart-faq-085254.html
There is a Jheadstart course available that we schedule on request.
Regarding Question 1, in general, people tend to underestimate the effort involved in migrating from Forms to ADF.
Migration tools like the JHeadstart Forms2ADF Generator can be of help, but are by no means a silver bullet.
When does JHeadstart save time
The amount of work that can be saved by using the JHeadstart Forms2ADF Generator (JFG) very much depends on the structure of the Oracle Forms application at hand. The JHeadstart Forms2ADF Generator provides most savings for forms that have the following characteristics:
* Standard-Forms data retrieval and data manipulation through blocks based on database tables, with master-detail relations defined between the block
* Complex user interface, many (stacked) canvasses, many tabs, many list of values, and other display types
* PL/SQL logic mostly limited to user interface dynamics: conditionally showing/hiding user interface items, and conditionally changing the properties of user interface items. While JHeadstart does not convert PL/SQL logic, this type of logic is easily implemented in the ADF application because JHeadstart provides many declarative property settings to implement this behavior.
PL.SQL Logic
JHeadstart has made the deliberate choice to not automatically convert the PL/SQL logic to Java. The reasons for this are:
* It is impossible to automate the migration of a two-tier architecture (logic in Forms or in the database) to a three tier Model-View-Controller architecture as is common in JEE web applications, including ADF-based applications.
* The architecture of the converted application should be identical to the best-practice architecture of an ADF application that is build from scratch. If the architecture is the same, the same skill set can be used to maintain both migrated applications and ADF applications build from scratch. In addition, by going for a best practice architecture, the application is more flexible, and can be maintained easier at lower cost.
* When using the JHeadstart Forms2ADF Generator, you get this best-practice ADF architecture that is identical to ADF/JHeadstart applications that are built from scratch.
Other Forms2ADF Considerations
And even if it turns out the JFG adds a lot of value, there are many other questions you should ask yourself before embarking on a Foms2ADF project.
For example:
* Apart from technical reasons like old Forms verisons no longer supported, are there real business reasons and business benefits for migrating that justify the migration effort?
* To what extent is the application still meeting functional requirements?
* Are there issues with stability and end user friendliness?
* Old forms applications are typical "window-on-data" screens, you see the structure of the datamodel through the layout of the screens. Modern web 2.0 composite applications are more task-oriented with good support for human workflow. You should consider to what extent it wants to leverage all these new user interfaces capabilities that come with ADF Faces and WebCenter.
* How does the application fits in the overall IT landscape? What interfaces to other systems exist, what (old/obsolete?) technology is used to implement those interfaces?
* What about batch functionality and reporting facilities?
* May be part of the functionality of the current system can be replaced with standard off-the-shelf software?
* How sound, well structured and future proof is the underlying datamodel?
* To what extent are you looking at service-orientated architectures? Whats the SOA maturity level of your organisation?
* Above questions help to answer the key question: how desirable and benficial is it to migrate an old monolitic forms application 1:1 to a monolitic ADF aplication? How does that fit in overall IT strategy?
* Organisational isues: who will migrate the system, who will maintain the system? Is outsourcing considered? etc.
Next Steps
We offer a Forms2ADF assessment service in which we migrate a number of sample forms selected by the customer to assess the added value of the JFG, and we discuss all of the above questions
For example, I did one Forms2ADF assessment where it turned out that JFG added litlle or no value, but we were still able to convince the customer of the combined power of ADF and JHeadstart in (re-)building ADF apps from scratch.
You also might want to take a look at some presentations I did on this topic, and some online demo's:
* Guidelines for moving from Oracle Forms to Oracle ADF and SOA: http://www.slideshare.net/stevendavelaar/forms2-adfsoa-ukoug
* JHeadstart Forms2ADF Generator – Migrating from Oracle Forms to a Best-Practice ADF application: http://www.slideshare.net/stevendavelaar/jhs11-forms2-adfukoug
* 3 online demo's of forms2adf conversion process: http://www.oracle.com/technetwork/developer-tools/jheadstart/overview/index.html
Hope this helps,
Steven Davelaar,
JHeadstart Team.