Lucas Jellema – AMIS Services, The NetherlandsTHE FUTURE OF FORMS IS…. FORMS(AND FRIENDS)Oracle Open World 2012
OVERVIEW• What says Oracle?• The Future:   – Why?   – What?   – How?   – When?• Key elements of the Future   – Vision   – ...
20 YEAR HISTORY OF FORMS• 1981/83• 1987• 1990• 1993• 1994• 1996• 2002/2005• 2009• 2011
FORMS 11G IS PART OF FUSIONMIDDLEWARE – PLATFORM FOR INNOVATION
MODERN FORMS• Forms 11gR2 was released recently (October 2011)• Support for Forms and Reports in OVAB was  announced Summe...
WHAT IS HISTORY FOR ONE, MAY STILL BEFUTURE FOR ANOTHER…•   GUI (Graphical User Interface)•   Web•   Extranet, Internet, S...
1998300% JAVA
WHY?
THE WRONG REASONS•   Forms is not Web 2.0•   Forms is no longer/will no longer be supported•   Forms is old•   Development...
2010END USERS ON STRIKE
THE END USER – BACK THEN
THE END USER - NOW
RIGHT REASONS• We (soon) can no longer find (enough) resources  willing and able to work on Forms technology• Forms applic...
2009NEW USERS GROUPS AND NEWCHANNELS
WebCenter                          Spaces 11g                             SOA Suite                                       ...
ALWAYS GOOD REASONS …• For investigating new options for application  development• For updating people skills• For constan...
ADFOracleForms                .Net  APEX                Open               Source
2011VISION FOR ISV
THE DOG-STAR DILEMMA             ?
ACCOUNTING• Any application represents a substantial investment   – The actual lines of code themselves (and the     funct...
THERE IS NO BUSINESS CASE…• For a 1:1 rebuild (or even automated migration) of your  existing Forms application• If it loo...
WHAT YOU SHOULD ALWAYS BE DOING• Work on your vision   – Strategy for the application and its architecture –     derived f...
FORMS FUTURE SCENARIOS•   Evolve/improve/"pimp existing Forms, continue to run as    Forms but with a much more modern loo...
MODERN FORMS – KEY PROOF POINTS• Runs on WebLogic – same platform as strategic  middleware products including ADF/WebCente...
FORMS 11G ARCHITECTURE       CSS                               HTML &                 Forms Applet                        ...
ENTERPRISE MANAGER FUSIONMIDDLEWARE CONTROL• Forms 11g runs on WebLogic Server 11g   – Just like SOA     Suite, UCM, ADF, ...
SERVER PUSH BASED ON AQ INTEGRATION• Form can subscribe on Advanced Queue• WHEN-EVENT-  RAISED trigger           Forms    ...
TWO-WAY JAVASCRIPT API IN FORMSAPPLET• HTML page uses raiseEvent JavaScript method on  Applet Object to pass event with pa...
FORM EMBEDDED IN WEB APPLICATION(ADF, APEX, OSS JAVA; .NET, PHP,…)                          OraFormsFaces
WEB 2.0 LOOK & FEEL – DRIVEN BY CSS• Community Project Forms Look and Feel• PJC based mechanism to style Forms using CSS
COLLECTION OF PJC BASED EXTENSIONS
Common Theme in Forms Evolution:INTEGRATIONBASED ON STANDARDS –WITH TECHNOLOGIES ON EVERY TIERCATERING FOR HYBRID-AND-INTE...
MODERN FORMS SCENARIOS –         FORMS IMPLEMENTING SOAP WEB SERVICE                    !   Forms                Forms    ...
MODERN FORMS SCENARIOS –FORMS IN JEE / WSRP WEB PORTAL               ADF Taskflow                   ADF Faces Page     For...
WRAP FORMS AS WEB SERVICE ANDCREATE NEW USER INTERFACES• Reuse existing Forms – running on Form  Server, unchanged, levera...
RENDER EXISTING FORMSTO DIFFERENT (NEW) PLATFORMS• Reuse existing Forms –render as pure HTML to any  HTML browser –includi...
MIGRATE OR REBUILD SELECTED PIECESFOR NEW USER GROUPS OR CHANNELS• Rebuild: using your technology of choice   – .NET   – S...
BUILD ON NEW TECHNOLOGY STACKSUSING EXISTING DEVELOPER SKILLS• APEX   – Comes even with     (basic) migration tool• Formsp...
HYBRID RESULT• Differences across    – User groups    – Channels and devices    – Functional requirements    – ‘Service Le...
POSSIBLE EVOLUTION• Forms Only• New pages in ADF –  existing Forms embedded• Gradually replace embedded  Forms with pure A...
WHAT YOU SHOULD ALWAYS BE DOING• Work on your vision   – Strategy for the application and its architecture –     derived f...
PEOPLE      threat      Java-nono       opportunity          critical    Classic fear                                    o...
CHERISH & INVOLVE ALL STAKEHOLDERS•   Make project visible•   Involve everyone•   Frequent communication•   Search for add...
DECOUPLING!• Centralize business logic• Rethink notion of  an application   – Break open silos   – Focus on business proce...
FIRST STEPS: SEPARATE APPLICATION ANDDATABASE                         Applicatie                      (User Interface)    ...
FURTHER ON DOWN THE LINE User Interface                       Application                  Email   Workflow               ...
TAKE AWAYS• Plan based on a vision with the application (and  perhaps the enterprise on the whole)• Decide using valid, ra...
THE FUTURE OF FORMS IS….A LANDSCAPE IN WHICH FORMS WILLPROBABLY PLAY AN IMPORTANT ROLEFOR QUITE SOME TIME TO COME –ALONG W...
The Future of Forms... is Forms (and Friends)
The Future of Forms... is Forms (and Friends)
The Future of Forms... is Forms (and Friends)
Upcoming SlideShare
Loading in...5
×

The Future of Forms... is Forms (and Friends)

1,577

Published on

Many organizations run enterprise Oracle Forms applications created in the 90s. They now wonder about the future of their application. This session tells how modernization of the application landscape could take place. The main approaches going forward to be discussed are: modernize the Forms themselves with Forms 11g and 12c, integrate the Forms with Web 2.0 and SOA components, embed the Forms in modern Web 2.0 applications, render the Forms to new devices, wrap the Forms as service and build new multi-channel User Interfaces on top of them and finally migrate or rebuild the functionality on a new technology platform. We will explore the options, discuss the merits, demonstrate the consequences and learn from actual experiences.

Key objectives:
Discuss the status of Oracle Forms, compared to other technologies for application development
Introduce various options for modernizing the application landscape, including demonstrations
Discuss considerations for choosing application architectures/future strategies

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,577
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
63
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • Process
  • Large German retailer1000+ FormsScared by IBM (based on ORCLs statement)Investigating alternativesIn the end: stuck with Forms
  • No business owner or end user ever asked you to ‘please get rid of Forms’. That is never a goal as such.
  • Much more computer literateMore demanding – what he/she gets on the internet and at homeSets the standard for applications at work!Also: from corporate user (who can be trained and drilled) to remote (field) worker/consumer
  • Peter
  • Peter
  • Form can subscribe on Advanced QueueEen WHEN-EVENT-RAISED triggerhandelt het event afIn Forms ServerEvent kan van Servernaar client wordengepushedBinnen max waitForm kan via aanroepvan PL/SQL procedureevents publiceren op AQBijvoorbeeld Form2Form push
  • PeterComment Peter: Should this move up a bit.
  • Lucas (Peter?)
  • Peter
  • Comment Peter: deze drie schrappen?
  • Process
  • The Future of Forms... is Forms (and Friends)

    1. 1. Lucas Jellema – AMIS Services, The NetherlandsTHE FUTURE OF FORMS IS…. FORMS(AND FRIENDS)Oracle Open World 2012
    2. 2. OVERVIEW• What says Oracle?• The Future: – Why? – What? – How? – When?• Key elements of the Future – Vision – Trends and evolution – Continuous preparation – People, people, people• Take aways
    3. 3. 20 YEAR HISTORY OF FORMS• 1981/83• 1987• 1990• 1993• 1994• 1996• 2002/2005• 2009• 2011
    4. 4. FORMS 11G IS PART OF FUSIONMIDDLEWARE – PLATFORM FOR INNOVATION
    5. 5. MODERN FORMS• Forms 11gR2 was released recently (October 2011)• Support for Forms and Reports in OVAB was announced Summer 2012• Note: 12c has been announced. The story may continue beyond that.
    6. 6. WHAT IS HISTORY FOR ONE, MAY STILL BEFUTURE FOR ANOTHER…• GUI (Graphical User Interface)• Web• Extranet, Internet, Self Service• SOA, Integration, B2B• Mobile• BPM and Workflow Management
    7. 7. 1998300% JAVA
    8. 8. WHY?
    9. 9. THE WRONG REASONS• Forms is not Web 2.0• Forms is no longer/will no longer be supported• Forms is old• Development productivity with Forms is not high enough• Our infrastructure cannot run Forms• Forms is not Open Source• Forms does not fit into our enterprise architecture• My end users complain about their productivity• We cannot provide the functionality required of us using Forms
    10. 10. 2010END USERS ON STRIKE
    11. 11. THE END USER – BACK THEN
    12. 12. THE END USER - NOW
    13. 13. RIGHT REASONS• We (soon) can no longer find (enough) resources willing and able to work on Forms technology• Forms applications do not have the visual appeal we need to be competitive• We want to start servicing new (external) user groups• We want to start supporting new channels in addition to intranet/extranet (internet, web service, mobile)
    14. 14. 2009NEW USERS GROUPS AND NEWCHANNELS
    15. 15. WebCenter Spaces 11g SOA Suite 11g ADF 11g UCM 11gWebForms 10g Oracle Service Bus 11g WebLogic 11gIAS/OC4J 10g EBS 11i JDE Cognos Oracle RDBMS 11gR2
    16. 16. ALWAYS GOOD REASONS …• For investigating new options for application development• For updating people skills• For constantly evolving the vision for business, architecture and application• For applying modern software engineering methods and tools• For constantly modernizing your applications (in baby steps) – Note: there is hardly ever a business case for a migration for technical (or FUD) reasons only• For applying the right tool for the right job
    17. 17. ADFOracleForms .Net APEX Open Source
    18. 18. 2011VISION FOR ISV
    19. 19. THE DOG-STAR DILEMMA ?
    20. 20. ACCOUNTING• Any application represents a substantial investment – The actual lines of code themselves (and the functionality they provide) – The acceptance and skills of end users & other parties – The expertise of the development team • As well as architects, analysts, testers, administrators, …• Any replacement will require a similar investment – Note that the original investment has been made over a period of 5 years, 10 years or even longer!• The applications and their underlying technology stack warrant a solid depreciation scheme – For building up the budget to keep evolving
    21. 21. THERE IS NO BUSINESS CASE…• For a 1:1 rebuild (or even automated migration) of your existing Forms application• If it looks like Forms, works like Forms, feels like Forms…• … it might as well be Forms• Business cases revolve around: – New users/customers or channels – New functionality – Retention of customers with improved X, Y and Z – Lower costs for existing functionality
    22. 22. WHAT YOU SHOULD ALWAYS BE DOING• Work on your vision – Strategy for the application and its architecture – derived from the strategy for the company• Stay on top of features of your current tool stack – To at least pick the low hanging fruit
    23. 23. FORMS FUTURE SCENARIOS• Evolve/improve/"pimp existing Forms, continue to run as Forms but with a much more modern look and feel• Integrate in SOA environment - hook up to push- mechanisms, queuing interaction and workflows• Embed in Web 2.0 (UI integration with ADF, .NET or other modern web technologies)• Wrap as web service (publish business logic from Forms & reuse with new User Interfaces or WebServices on top)• Render to new platforms (render Forms as they are to new platforms like HTML browsers and mobile devices)• Migrate to new technology stack and architecture (semi)- automagically migrate/convert Forms to new technology• Migrate to new technology stack and architecture: rebuild functionality in new technology stack - leveraging functionality and experience from current Forms
    24. 24. MODERN FORMS – KEY PROOF POINTS• Runs on WebLogic – same platform as strategic middleware products including ADF/WebCenter, SOA Suite, BPM Suite, UCM, OBIEE and IdM• Managed from Enterprise Manager 11g• Integration with Oracle 11g Access Manager• Support for Database Proxy Users• (Client Side) Pluggable Java Components to add custom functionality and interaction elements to UI• Integration with AQ – to allow for Server-to-Client push• Java Importer – extend Form with middle tier Java• JavaScript bridge – from JavaScript to Form: pass information and events from web page to Form – From Form to JavaScript: pass data and event from Form to web page
    25. 25. FORMS 11G ARCHITECTURE CSS HTML & Forms Applet JavaScript WebLogic Server 11g Form Forms Server runtime = 11g = 10g
    26. 26. ENTERPRISE MANAGER FUSIONMIDDLEWARE CONTROL• Forms 11g runs on WebLogic Server 11g – Just like SOA Suite, UCM, ADF, WebCenter, OSB, OBIEE, Reports, …• Administration is done through Enterprise Manager Fusion Middleware Control – configuration – session monitoring & management – logging – security
    27. 27. SERVER PUSH BASED ON AQ INTEGRATION• Form can subscribe on Advanced Queue• WHEN-EVENT- RAISED trigger Forms Forms Forms deals with event Applet Applet Applet – In Forms Server• Event can be pushed WebLogic Server 11g from Server to client• Form can call PL/SQL Form Form Form session session session procedure to publish events on AQ Forms Server runtime – This enables Form2Form push
    28. 28. TWO-WAY JAVASCRIPT API IN FORMSAPPLET• HTML page uses raiseEvent JavaScript method on Applet Object to pass event with payload to the Form – document.forms_applet.raiseEvent(event_name, payload);• Form receives and processes the event with WHEN- CUSTOM-JAVASCRIPT-EVENT triggers• Form can execute JavaScript snippet in the containing HTML page – Web.Javascript_Eval_Expr ( expr, target) – Web.Javascript_Eval_Function ( expr, target) return varchar2
    29. 29. FORM EMBEDDED IN WEB APPLICATION(ADF, APEX, OSS JAVA; .NET, PHP,…) OraFormsFaces
    30. 30. WEB 2.0 LOOK & FEEL – DRIVEN BY CSS• Community Project Forms Look and Feel• PJC based mechanism to style Forms using CSS
    31. 31. COLLECTION OF PJC BASED EXTENSIONS
    32. 32. Common Theme in Forms Evolution:INTEGRATIONBASED ON STANDARDS –WITH TECHNOLOGIES ON EVERY TIERCATERING FOR HYBRID-AND-INTEGRATED APPLICATIONARCHITECTURE
    33. 33. MODERN FORMS SCENARIOS – FORMS IMPLEMENTING SOAP WEB SERVICE ! Forms Forms Forms Applet Applet Applet ! ? WebLogic Server 11g? ! Form Form Form session session session Forms Server runtimeWebService ! ? SOA SuiteM AQ
    34. 34. MODERN FORMS SCENARIOS –FORMS IN JEE / WSRP WEB PORTAL ADF Taskflow ADF Faces Page Forms JS API af:inlineFrame
    35. 35. WRAP FORMS AS WEB SERVICE ANDCREATE NEW USER INTERFACES• Reuse existing Forms – running on Form Server, unchanged, leveraging all existing business logic, interaction scenarios wrapped as Web Service• OraPlayer WebService Forms Applet “Java” WebLogic Server 11g Form Form session session Forms Server runtime
    36. 36. RENDER EXISTING FORMSTO DIFFERENT (NEW) PLATFORMS• Reuse existing Forms –render as pure HTML to any HTML browser –including on Mobile devices• Yo!Forms and Yo!Server
    37. 37. MIGRATE OR REBUILD SELECTED PIECESFOR NEW USER GROUPS OR CHANNELS• Rebuild: using your technology of choice – .NET – Some Java Open Source Framework – 3rd Party 4GL like technology – ADF (Oracle’s own strategic application development framework)• Or: Migrate (even convert) using tools on offer – Pitss, Ciphersoft, Qafe, JHeadstart, ASP Solutions JHeadstart
    38. 38. BUILD ON NEW TECHNOLOGY STACKSUSING EXISTING DEVELOPER SKILLS• APEX – Comes even with (basic) migration tool• Formspider• Qafe
    39. 39. HYBRID RESULT• Differences across – User groups – Channels and devices – Functional requirements – ‘Service Level’ demands• .. will require various, different technological solutions.• Moderns IT architectures, standards and technologies make hybrid and integrated solutions possible.• This should be your objective too!
    40. 40. POSSIBLE EVOLUTION• Forms Only• New pages in ADF – existing Forms embedded• Gradually replace embedded Forms with pure ADF pages – On top of a Web Service that wraps the orginal Form WebService• Move the ADF-on-top-of-wrapped-Form “Java” pages to a non-Form WebService• Note: replace ADF with .NET and the story is still true!
    41. 41. WHAT YOU SHOULD ALWAYS BE DOING• Work on your vision – Strategy for the application and its architecture – derived from the strategy for the company• Stay on top of features of your current tool stack – To at least pick the low hanging fruit• Prepare for a future with a hybrid environment• Continue to evolve skills of the people involved – You need to have at least some Java, XML, Web Service skills on the team – Continue to upgrade SQL, PLSQL and Forms skills• Design and implement following ‘decoupling’ as architecture principle
    42. 42. PEOPLE threat Java-nono opportunity critical Classic fear open conservative training Consult – on inquisitive uncertainty overwhelmed new trends Remote doubt & experience reluctant Support Introduction Coaching QA/Audit& Demonstration & Inspiration Collaboration confident Training opportunity productive initiative move ahead critical fun at home in Java independent enthusiasm stepping stone participate personal growth
    43. 43. CHERISH & INVOLVE ALL STAKEHOLDERS• Make project visible• Involve everyone• Frequent communication• Search for added value in various dimensions – Functionality, Quality, Cost, Satisfaction for both end users and the IT team Developers Administrators Information analysts Business owner & Sales Customers & End Users
    44. 44. DECOUPLING!• Centralize business logic• Rethink notion of an application – Break open silos – Focus on business process• Create many light weight, specialized user interfaces• Service Orientation• Event Driven Architecture
    45. 45. FIRST STEPS: SEPARATE APPLICATION ANDDATABASE Applicatie (User Interface) Applicatie (User Interface) Data Data
    46. 46. FURTHER ON DOWN THE LINE User Interface Application Email Workflow Engine CMS IM Fax
    47. 47. TAKE AWAYS• Plan based on a vision with the application (and perhaps the enterprise on the whole)• Decide using valid, rational arguments• Reckon with a prolonged (continuous) evolution rather than a big bang switch over• Do not consider automated migration from Forms to <something else>• Hybrid environments are unavoidable – embrace them• Decoupling will help with building the hybrid architecture and helps low-impact optimization – Move data-oriented business logic out of Forms to DB• Moving to Forms 11g (more specifically: to WebLogic Server) is a smart move to a solid foundation• Forms 11g is more modern than many people realize• People are the key to success
    48. 48. THE FUTURE OF FORMS IS….A LANDSCAPE IN WHICH FORMS WILLPROBABLY PLAY AN IMPORTANT ROLEFOR QUITE SOME TIME TO COME –ALONG WITH NEW TECHNOLOGIES TOCATER FOR NEW USER GROUPS, NEWCHANNELS AND NEW FUNCTIONALREQUIREMENTS
    1. ¿Le ha llamado la atención una diapositiva en particular?

      Recortar diapositivas es una manera útil de recopilar información importante para consultarla más tarde.

    ×