
Originally Posted by
nan21eu
Before answering your questions here are some hints :
To migrate an app from Oracle Forms to 3 tier web app the development team will have to learn a language and a framework for both the client side and the server side anyway:
- Client side: javascript + framework (Extjs or some other javascript library ) or some other plugin based browser technologies
- Server-side: java + framework(s) (whatever you'd choose from the millions of available choices) or php + some framework(s) : as i see from your first post these are your preferences
It's not an overnight task, it takes some time of course and how fast it is depends on technology plus willingness of each and every person in the team to adapt to the changes.
However, from my past experiences the main challenge for your team will be to think in web 2.0, replace the sequential integrated thinking as they are used to with Forms with the asynchronous service oriented thinking required by such an architecture.
In my humble opinion you should find an architect who built similar project(s) and is able to be a technical lead. I don't know your project, but most of the time, large enterprise Forms based applications hide lots of tricky business logic in the client and the solution is not always obvious, especially for those who are new in this area.
The answers:
1) , 2) see above
3) for reports DNet doesn't offer anything special except a built-in export function for each data-source, there are very good report engines (BIRT, Jasper, Crystal reports, even your Oracle Report Server reports can be used as they are etc) and called by the url from data-control/frame context
4) whatever way you go, i recommend to get a good architect before start such a work
5) the DNet framework doesn't have anything special, for anybody who's comfortable with Extjs samples DNet is just a piece of cake. For the server side also pure plain java / spring / eclipselink experience is enough.
However, the entire server-side part could be replaced with another implementation in php / java / groovy / ruby or whatever else and should work the same. In this kind of projects usually the business logic is in database packages ( hopefully not in client-side program units ) and the server side is just a simple dispatcher which delegates the work to the database packages. - So, depends on the chosen technology(ies)
6) the implemented business features, the documentation, send your questions on the mailing lists