Migrate Oracle Forms to Apex
A number of the Apex community are getting excited about the release of the Forms to Apex convertor and its fair to say many Forms customers are interested in this idea of conversion to a familiar PL/SQL world so I thought it might be in the community spirit to help the community understand how to approach a project of conversion and outline a list of questions that you probably need to fully understand and have answered, before embarking down the conversion road - look on it like a list of interview questions to get past the resume gloss ;o)
So pop pickers, here are our top 20 questions...you may want to add your own..
1) Am I considering conversion for the "right" reasons?
a) Am I aware of Oracle's statement of direction on application development tools and specifically Oracle Forms?
b) Am I sure that Apex is the right environment for my application development?
c) Am I aware of Oracle's strategic enterprise application development platform for their Fusion applications (JDeveloper/ADF/SOA etc)?
2) What are my expectations for a Forms application being converted to Apex?
a) Do I want it to look and behave like Forms?
a1) Will I be getting the best out of Apex in that case?
b) Do I want it to look and behave like a "typical" Apex application?
b1) Do I need to retrain my end users?
3) Will the conversion take into account architectural differences between Forms and Apex
a) How much rearchitecure is involved in converting a stateful Forms application to a stateless Apex application?
a1) How will the converter help in in this task?
a2) What would be the estimate of time/cost for a typical 100
Form application?
b) Do I need to take into account different in the UI technologies
including layout and application flow?
b1) How will the converter help in in this task?
b2) If our users are used to manipulating multiple windows/forms can we still support that behaviour?
b3) What would be the estimate of time/cost for a typical 100 Form application?
4) Will my Forms triggers be converted to Apex equivalents?
5) Will my PLLs be converted?
6) What will happen to Forms built-ins like Set_Block_Property, Set_Item_Property?
7) Will the converter refactor my code into UI specific and data specific layers
a) How will it distinguish Forms code and triggers that are both UI and data action
8) Will my blocks based on stored procedures be converted?
9) Will menus be converted?
a) How should I best implement a typical complex Forms menu hierarchy?
b) How should I implement Forms menu security?
10) Will my popup menus be converted?
a) Will other skills be required to support this behaviour in Apex?
11) Will object libraries be converted?
a) How will I maintain consistent look and feel as I did with object libraries?
b) How will I build reusable libraries of components as I did with object libraries?
c) Will any of the above require me to know skills other than PL/SQL?
12) Are there any Forms specific features that won't convert, for example, Query By Example?
13) How are control block converted?
14) How shall I approach team development and sharing of common objects like reference forms, PLLs, MMBs and OLB.
15) How "free" is Apex? Will I NEVER pay to run my Apex applications or will this be tied to database processor/user license?
16) How do I handle reporting?
a) Should I convert Oracle Reports or can I still call them from my converted application?
17) Show me references of customers who have used this convertor and how they addressed the above points.
18) Will my data entry operators still have the same instant validation model?
a) Will my validation triggers be converted automatically?
b) How will field level validation be implemented in Apex?
19) Will my data entry operators be abe to use the same "hot key" combinations?
a) Will this be converted automatically?
b) How will this be implemented in Apex?
20) How do I implemented client side integration with things like client side printers, scanners, barcode readers (Webutil like integration)?
Of course, these are just a sample of the questions you should be asking - you may want to post your own questions here and I can add to this list.
Comments:
Really nice list for those attempting a Forms to Apex conversion. However, there are a couple of questions.
Seems like the Forms group and the Apex group within Oracle are fighting each other and your list tends to show that, although I see it myself as a wake up call for those who might be tempted to jump in without fully understanding why they want to to turn to Apex. Point 15 is the most troublesome for me as you seem to imply there are costs involved with Apex. The last time I attended an Oracle presentation, Oracle sales representatives did mention it was all FREE.
Point 3 and especially the100-Form mark needs not be. At that point, we are no longer in the departmental range and it is a waste of time to even consider moving to Apex. Better may be to move to java-platform if people want to throw out their Forms app.
Point 16 is the most interesting one for enterprise applications and the most fun to deal with for those attempting migration. That is a costly process even for a Forms to forms conversion.
But all in all, I think anyone planning a Forms to Apex conversion should print out your list and hand it to management.
(BTW point 16 is one of the easiest to solve in APEX because starting a report is just calling an URL, and APEX is very good at that ;-) ).
Regarding point 16 - yes it is easy to call but maybe you would like to answer: sure you can call a URL but if you are converting your Forms, why keep your Reports? If you want to keep them in Reports then its a quick check and thats good news - but if you don't, what are the options???
Thanks for your comment
However, I did want to "balance" the "excitement" with some practical down to earth advice on how to approach.
Regarding point 15 - you'll need to ask the Apex experts - but there is "free" and there is "free" - and there is the old saying that there is no such thing as a free lunch (and I kinda hope so since Oracle pays my salary - I'm hoping Oracle are trying to run at a profit!)
Regarding the "100 form mark" - again you are right - but there are still some customers who are thinking that if they are considering converting they might go the full hog.
Thanks for your comments - my goal is just to help guide and educate people on the process involved. I'm sure if we can get this list "out there" that surely can only be good for the community.
Thanks
Grant
In my time I've seen some weird and wonderful JavaBeans plugged into Forms, things that just wouldn't convert to the Apex world (nor web world for that matter) but are pivotal for the business application at hand. IMHO most Forms applications of any reasonable size typically have some of these providing important functionality and would be extremelly important to consider in any Forms to X conversion/migration tool.
Cheers,
CM.
I don't understand the point of "hafed" above why APEX isn't even being considered for a 100-Form application, and why "it's a waste of time to even consider moving to APEX". That's not a huge application, and customers have written applications in APEX more than 10 times larger than that. What's so special about the arbitrary 100-Form mark?
Regarding point #15 of "15) How "free" is Apex? Will I NEVER pay to run my Apex applications or will this be tied to database processor/user license?", APEX is not "free", nor has it ever been free. It is a no-cost feature of the Oracle database - if you are licensed and supported for the Oracle database, you are licensed and supported for Oracle Application Express. The cost of APEX is not tied to any processor/user license. There has never been an intent to charge for APEX, and there are none being discussed or planned. It is super-extraordinarily unlikely in my lifetime. #15 is plain and simple FUD with no basis in reality.
And I'll offer you a point #21:
21) If I decide to choose to move from Forms to another technology, will there be *any* similarity between the skills of my current Forms developers and the skills required for the new technology? Or will I be essentially starting from scratch? How long will it take to train them? How much will it cost? How much reuse of my server-side PL/SQL will be possible? Does the new technology embrace the Oracle database, like Oracle Forms?
Regarding point 15 - I'm not questioning if Apex is free - the question I am offering that people should ask is by putting my application processing into the database - will this impact the total cost I will have to pay for running that application as opposed to if that application was not deployed in the database. There is no FUD about it - that is simply a question you need to ask - and frankly if you are not asking hard questions about your licensing cost I'd be pretty worried.
You last point is very valid as well - from the ADF/JDev side of the house, because much of the development effort comes from the "Forms" side of Oracle's development teams, ADF provides alot of familiar concepts for Forms developers. Apex, on the other hand, has the advantage of being based on PL/SQL scripting language - there are plus and minus points.
With Hafed' comment, my interpretation of his point (and hence my answer) was not that numerically, Apex can't have 100s of screens, of course it can, but a "typical" Forms application tends to be implementing a huge number of business process where as an Apex application, "typically" is less so (and don't think that means it doesn't or it's less advanced than Forms - but the typical sweet spot for the applications lies in different areas of application complexity)
Thanks for your comments.
Grant
I then misinterpreted point #15, as I'm sure many customers would from the original wording. It's really no different than asking customers to consider how "free" JDeveloper or PHP or Eclipse is. Perhaps it can be better stated as:
15) What will be the total cost to run an equivalent application using the new technology?
And with respect to this question of additional cost on the database, the stateless nature of HTTP (and APEX), presented as a possible negative in 3(a) can actually be a benefit for a large number of applications, requiring *less* overall database resources than equivalent applications on other technologies.
Similarly I'm not looking to present stateless as a negative - simply to highlight the fact that it is different and these differences need to be addressed (some might be positive some might be negative - again, I am not trying to prejudice - simply to alert people to the differences).
Some of have the luxury of working with much of this technology for years - others are less fortunate and wouldn't even be aware of the differences or be confused by the FUD - hence, wanting to create a checklist to help in formulate a development plan.
Thanks for your comment
Over-selling capabilities and under-selling the conversion effort required is definitively not in anyone's best interests, especially the customer's. Microsoft does a great marketing job of selling people on how easy moving to .NET will be. Reality for customers who do choose that path is anything but, as I have heard of several such projects that have failed miserably.
Historically Oracle had one main development tool - Oracle Forms. Now we have several options for those developing with the Oracle Database of which ADF and APEX are the two most popular. Fundamentally ADF and APEX are positioned very differently and have different "sweet spots". Providing different tools ensures that Oracle can best meet any development requirements.
Eventhough APEX is a "no-cost" feature of the Oracle Database, APEX is a strategic tool for Oracle that is responsible for both indirect and direct revenue.
Regards,
David
I think your list is very useful and you are absolutely right you need to understand what a conversion means.
As you know, I'm also pro APEX and I agree ofcourse with the points that Joel, David and Roel said before.
Joel recommended one more question. I also want to add one:
22) In times where business changes so quickly, how fast can you full-fill your business need with your technology?
Another comment I want to make is, that you can use both Forms and APEX (or another technology) together. In a number of projects our customer had everything in Forms. But a part of their application had to be more open en preferable web based. We gave them APEX and they loved it very much. The truth is that after that initial project, they wanted us to take over other existing functionalities of the Forms application. And the plan is to convert the whole, but we told them it would take time to do (we are speaking of 100+ Forms). But there is no hurry as the existing Forms are still fine.
I think it's important to guide your customer to a new technology, as it means the way of working might be different.
Thanks,
Dimitri
A good list indeed. I'd be much more worried by someone facing a migration/conversion who didn't ask questions than one who asked questions (no matter what those questions are).
As Joel pointed out, #15 is commonly quoted FUD, it does amaze me that some people are more worried by the fact that APEX is no-extra cost than if you actually had to pay extra for it. Do these same people worry that Oracle will start charging for extra for PL/SQL too? (that was not intended to be taken seriously by the way!).
I would actually reword #15 as this -
15) Given that APEX is a no-cost feature of the database, does Oracle have any precedent for then making it an extra-cost feature? (In other words, has a similar Oracle product ever gone from no-cost to extra-cost).
I would also add an extra question -
22) Is it possible, given the way my existing Forms application is architected that I can actually save money overall if I migrate to APEX?
Or...perhaps more generically -
22) - If I migrate to APEX, will my overall running costs -
22.1) Increase.
22.2) Decrease.
22.3) Roughly stay the same.
John.
Do I need to convert everything at once?
a. Can I run both systems side by side?
b. Can I let existing forms die out in their regular end of life, and do new development in Apex?
c. Will a side by side implementation ease the transition?
Nice post. I remember a similar discussion about forms conversion/migration when a preview of Apex 3.2 was presented ( http://dgielis.blogspot.com/2008/09/preview-oracle-apex-32-forms-migration.html ). Now the forms conversion functionality is available I must say I was happily suprised when I noticed the "project management" functionality of the converter.
About the list: this is really helpfull, but I am sure the list can be extended when you have actually gone through a 100+ forms conversion process (so please do ;-).
I agree with Dimitri to advise companies to use both Forms and Apex next to each other. In this way, both end users and developers can get used to the differences between both technologies, which will help if you decide to start a conversion project.
Peter
1. How can I do massive parallel development? Is there support for multi level development, eg. moving excerpt of my development from development to test to production and in case of failures back.
2. Same question for versioning, this is essential if you are forced by law to build your application to every day of the last 10 years. This should be possible on your basic excerpts to avoid massive disc space comsumption.
3. Is there a way of supported migration of your application to next release and does your environment will exist after next hype. We had developed an UIX (and this was named a quasi standard too) application in the past and every oracle partner we have asked in the past, says we have to redevelop this in new technology, as there is no migration path after UIX died. Same we had in Interconnect as the sap adapter was changed from manufacturer actional to iWay. Did not see such things in forms the last 12 years, except some partial function redevelopment after migration from c/s to web.
Thanks for your input.
I am seeing a number of applications being developed with APEX and those are applications targeted more toward departmental levels, kind of replacing Microsoft Access type applications.
I am not saying that APEX is not suited for applications with 100+ forms. I believe the tool is perfectly capable for those apps. However, I believe that if you are in that range with an already ESTABLISHED Forms app and that you are planning a migration, then an ADF path might be a better choice.
At any rate, it all comes down to what the team is really comfortable with and whether it is Forms 10g-11g/APEX or ADF, a migration plan has to be devised against hard numbers (based on something similar to Grant's list).
John Scott rewrote #15 as this:
Given that APEX is a no-cost feature of the database, does Oracle have any precedent for then making it an extra-cost feature? (In other words, has a similar Oracle product ever gone from no-cost to extra-cost).
Actually, this was the case when moving from C/S Forms 6i to the web. In good old C/S days, we could deploy our application to our customers with no extra cost. Now we have to sell the application server and install/maintain the bastard. While I'm a big fan of both Forms and APEX technology, I had more trust in Oracle the company before they pulled that stunt.
If one is about to make a strategic tool decision it's wise to think about the vendor's long-term roadmap for that product, both from a financial and a technological point of view.
Your last point is interesting as well. When people ask me about the viability of Java/ADF/SOA etc I'm inclined to point to the fact that since its the wagon Oracle have hitched their business applications to, there is a comfort in that.
Thanks for your comment
Another important question could be: "Since it is Web Technology, are all common Browsers supported?"
My question is specifically pointing to IE6, which still has about 25% market share and a lot of big companies still use IE6 and can't/won't upgrade to IE7/8.
I don't mean to bash ADF with this one, but - in my eyes - it is very important to be aware of what a tool decision implies.
Source: www.oracle.com/technology/products/jdev/htdocs/jdeveloper11gfaq.html
Peter
Regards,
Venu
replica watches paypal
rolex replica paypal
replica watch paypal
| UGG Boots On Sale
| UGGS On Sale
| Australian UGG Boots
UGG Bailey Button Boots
| UGG Bailey Button
| Bailey Button Boots
|cheap UGG Bailey Button
Ugg Classic Argyle Knit Boots
| Ugg Classic Argyle Knit
| Classic Argyle Knit Boots
| cheap Ugg Classic Argyle Knit
UGG Classic Cardy Boots
| UGG Classic Cardy
| Classic Cardy Boots
|cheap UGG Classic Cardy
UGG Classic Crochet Boots
| UGG Classic Crochet
| Classic Crochet Boots
|cheap UGG Classic Crochet
UGG Classic Flower boots
| Classic Flower boots
| UGG Classic Flower
| cheap UGG Classic Flower boots
UGG Classic Leopard Boots
| Classic Leopard Boots
| UGG Classic Leopard
| cheap UGG Classic Leopard Boots
UGG Classic Mini Boots
| UGG Classic Mini
| Classic Mini Boots
| cheap UGG Classic Mini
UGG Classic Paisley Boots
| UGG Classic Paisley
| Classic Paisley Boots
| cheap UGG Classic Paisley
UGG Classic Short Boots
| UGG Classic Short
| Classic Short Boots
| cheap UGG Classic Short
UGG Classic Tall Boots
| UGG Classic Tall
| Classic Tall Boots
| cheap UGG Classic Tall
UGG Esley wedge boots
| UGG Esley wedge
| Esley wedge boots
| cheap UGG Esley wedge
UGG Infant's Erin Baby Boots
| UGG Infant's Erin Baby
| Infant's Erin Baby Boots
| cheap UGG Infant's Erin Baby
UGG Langley Boots
| UGG Langley
| Langley Boots
| cheap UGG Langley Boots
UGG Lo Pro Button Boots
| UGG Lo Pro Button
| Lo Pro Button Boots
| cheap UGG Lo Pro Button
UGG Locarno Boots
| UGG Locarno
| Locarno Boots
| cheap UGG Locarno Boots
UGG Mayfaire boots
| UGG Mayfaire
| Mayfaire boots
| Cheap UGG Mayfaire
UGG Nightfall Boots
| UGG Nightfall
| Nightfall Boots
| cheap UGG Nightfall
UGG Rainier Eskimo Boots
| UGG Rainier Eskimo
| Rainier Eskimo Boots
| cheap UGG Rainier Eskimo
UGG Sundance II Boots
| UGG Sundance II
| Sundance II Boots
| cheap UGG Sundance II
UGG Ultimate Bind Boots
| UGG Ultimate Bind
| Ultimate Bind Boots
| cheap UGG Ultimate Bind
UGG Ultra Short Boots
| UGG Ultra Short
| Ultra Short Boots
| cheap UGG Ultra Short
UGG Ultra Tall Boots
| UGG Ultra Tall
| Ultra Tall Boots
| cheap Ultra Tall Boots
UGG Suede Boots
| Suede Boots
| UGG Suede
| cheap Suede Boots
UGG upside Boots
| UGG upside
| upside Boots
| cheap upside Boots
UGG Roxy Tall Boots
| UGG Roxy Tall
| Roxy Tall Boots
| cheap Roxy Tall Boots
UGG seline Boots
| UGG seline
| seline Boots
| cheap seline Boots
UGG Women's Corinth Boots in Cocoa
| UGG Women's Corinth
| Women's Corinth Boots in Cocoa
| cheap Women's Corinth Boots in Cocoa
UGG Liberty Boots
| UGG Liberty
| Liberty Boots
| cheap Liberty Boots
UGG Highkoo Boots
| UGG Highkoo
| Highkoo Boots
| cheap Highkoo Boots
UGG Knightsbridge Boots
| UGG Knightsbridge
| Knightsbridge Boots
| cheap Knightsbridge Boots
UGG Bomber Jacket Boots
| UGG Bomber Jacket
| Bomber Jacket Boots
| cheap Bomber Jacket Boots
UGG
| UGG Boots
| UGGs on sale
| Cheap UGG Boots
Ugg News
Find ugg boots günstig?!UGG boots Sale ,Enjoy free shipping + bargain sale now!UGG Classic Short,100% Authentic UGG Australia Boots!ALL of UGG Classic Cardy are the cheapest and best for you!Enjoy yourself of shoping in Find Cheap Sheepskin UGG Boots billig IN UGG Boots Shop!
Yes,you are right,and you known that As a pursuer for the most stylish , you have no excuse anymore if you don't have a pair of UGG boots or a pair of Adidas shoes.Our Ugg boots including UGG Classic mini ,UGG deuschland,UGG Ultra Short, UGG Classic tall,UGG Ultra Tall,UGG Sundance II
gucci handbags for sale
Balenciaga bags
louis vuitton bag
louis vuitton handbag for cheap
ghd very cheap
ugg boots for cheap
china Wholesale
丝印器材
Thank you for the author's hard write, ugg boots
sale in 2010 change you image, here is some good Website for
uggs, another you can see this any more:
uggs sale,
ugg boots sale,
I very much like this article
gucci shoes,
cheap uggs,
mbt shoes,
ugg boots,
and so on.
Shop authentic Air Force One Shoes / 1 Shoes, including Nike Air Force 1 Premium, Nike Air Force 1 Supreme, Air Force One Retro Court and ike Air Force 1 low. Shoes like Nike Air Force One 25t, Air Jordan Shoes, Bathing Apes Bapes, Greedy Genius Shoes, Reebok, Pumas, Adidas, and many other Nike Air Force One Transparen. Since Air Force Ones are limited shoes, Nike Air Force One Low shoes does not authorize online sales, but there are a few places where you can still score a great deal on authentic Air Force One Light-up shoes. Air Force Ones Shoes from Nike are a must. Custom Air Force One Bird's Nest, or Original Air Force 1s can be found here. Our Nike Air Forces 1 Shoes come in.
Asics Shoes running shoes and sports apparel. Find stores, get a training program for your next marathon, learn more about Onitsuka tiger Mexico 66 and Onitsuka tiger Midrunner. Shopping is the best place to comparison shop for Onitsuka tiger Mini Compare products, compare prices, read reviews and merchant ratings.
Ghdszone.com - ghd straighteners cheap have design to make up your dreams to have easy manageable, straight and smooth hair in few minutes just with cheap ghd straighteners. Nice GHD Straighteners and CHI Straighteners products on sale now.
ugg boots sale,
uggs,
gucci handbags,
cheap jordan shoes,
Hope that everyone can derive what you want:
uggs sale,
ugg boots sale,
cheap mbt shoes.
Leave a comment: