This content has been marked as final. Show 3 replies
I guess you are using oracle 6i forms with 10g forms in that case
Nothing to worrya about migrating from 10g system to 11g.
Your all code in fmb and rdf will remains same. The Web2.0 interface uses applet to shows your fmb forms inside this applet container and works fines as works in 6i form. So after migrating you can also continue with developing forms and reports as earlier with very few changes in your forms and report . So overall your business logic and packages/views/pll will remain same.
Only you have to configure the new Application Server to run the Web2.0 interface and on client side the Jinitiator will automatically iintall on first run to support java environment for Applet.
So go ahead with migrating if above the case.
Please Don't forget to mark this post as correct/helpful. This will help in replying many others too.
Edited by: Askdineshsinghminhas on Jan 10, 2013 7:24 AM
Edited by: Askdineshsinghminhas on Jan 11, 2013 5:43 AM
Sorry i think you misunderstand.
We know this process will be straightforward
BUT are looking at moving away from forms at some point to jdev. So are trying to housekeep our forms in this miogration.
We are wodnering whether to seperate all our logic and how best to do this.
We have started to shift all code into the database but are we best actually creating services and moving the code outside the database.Why do you want to move things outside of the database? Is there a reason to do so? There is nowhere written that webservices must not call stored procedures, and the only thing you would acomplish by that is that stored procedures called from forms need to call the webservice instead which will add an additional layer of complexity.
Leave things in the database where it makes sense and use those stored procedures in your webservices, by that you'd have
forms => stored procedure
something else => webservice => stored procedure