Copyright 2014 PITSS GmbH

Transcription

1

2 About PITSS Managing and Modernizing Oracle Forms and Reports Worldwide pitss.com/us/our-customers/

3 Some ADF, APEX,.NET Migration Projects with PITSS.CON Organisation/ Project US AAR Corporation/ Forms + ADF + ADF Mobile US Metronics/ Forms 11g + ADF US Department of Justice ATF Forms to ADF US PowerSouth Energy Coop./ADF Mobile DE Volkswagen/ Forms3 to ADF11g +.NET US Oracle Retek/ Forms to ADF US DTE Energy/ Forms11g + ADF DE Education Provider/ Forms11g + APEX US Boeing UK Airas Intersoft/ Designer to Java EE US Health Care Provider/ Forms6i to ADF11g Motivation for Change Integration, Mobile Modern user interface Oracle strategy Rapid Implementation of Mobile Applications (ios, Android) Same Weblogic environment as Forms Java - a strategic direction for VW Oracle strategy Integrates very well with Forms Complements Forms limitations Reducing the license costs Oracle strategy Complexity (ex: MDDD Oracle Assoc.)

4 Client About the Application Modernizing Mobile Forms INPs Challenges: Big Forms application that needs to run on supported platforms Forms 11g upgrade project was a nice PITSS.CON 12 routine.. So I ll tell you about the mobile part: Desktop Forms applet Mobile Win CE Barcode Scanners Forms 3.0 Part of modules need to run on legacy hardware: Windows CE 5.0 barcode scanners of various types Forms 11g does not run on Win CE 5 devices Maintaining the old INPs only for the mobile devices was not an option DB App. Server Forms 11g FMBs, PLLs, OLBs

5 Client Project Start for Modernizing the Mobile Forms Modules Requirements/ Challenges Same excellent performance Hot-Key functionality Support for new and old devices Support for Win CE 5.0 operating system Architecture to minimize future migration efforts Modern user interface Kiosk/ App Mode Functional extensions And Minimal time budget: 2 months Maximum quality DB App. Server Desktop Forms 11g Forms applet FMBs, PLLs, OLBs Mobile Win CE Barcode Scanners Forms 3.0

6 Our Technology Options for the UI Oracle ADF 11g Mobile Overview HTML5 and Java-based mobile application development framework that enables developers to build and extend enterprise applications for ios and Android from a single code base. Based on a hybrid mobile architecture, ADF Mobile supports access to native device services, enables offline applications and protects enterprise investments from future technology shifts. Oracle ADF Mobile is part of Oracle ADF, the strategic, standards based framework for Oracle Fusion... Our options for Mobile Application Development - Oracle ADF Faces Rich Client Components - Oracle ADF Mobile Browser compatibility!!

7 Oracle ADF 11g Supported Mobile Browsers and Features Browser JavaScript Support CSS Support PPR Support BlackBerry version 4.6 and later Yes Yes Yes Blackberry versions 4.2 through 4.5 Microsoft Windows Mobile 5 Microsoft Windows Mobile 6 Apple iphone Safari Nokia s60 series Plain HTML (Opera Mini, Opera Mobile and Skyfire) No Yes No Yes Yes Yes (with nuances) Yes Yes Yes Yes Yes Yes Yes Yes No No Yes No

8 Our Technology Options for the UI - The Win CE JavaScript Problem Top Issues ADF Mobile Browser needs JavaScript for function keys. JavaScript browser not available for Windows CE 5.0 ADF Mobile not supported for Windows CE 5.0 The research process took 2 weeks!!! => 6 weeks left for migration!!

9 Client Our Technology Options for the UI The Solution Thin client Key-Functions Full-screen (Kiosk) Modern UI Compatible with existing devices DB Application Server Desktop Forms applet Shared Security Mobile Win CE Web Services.NET Thick (90%) ADF + DB Preserve DB Communicate with the rest of the Forms application Model Layer contains View Objects and Methods (Business Logic) exposed as Web Services Forms 11g FMBs, PLLs, OLBs ADF Business Components View Objects Business Logic to DB Methods

10 Client The Solution: Forms & ADF Server +.NET Client.NET: Compact Framework 2.0 SP 2.0 Web Services JAX-WS Login/ Authentication ADF: JDeveloper Weblogic: ADF Runtime Database: Oracle 11g Packages created from Forms functionality Without unused objects Grouping redundancies for easier maintenance Cleaned from any global variables and global transactions => connection sharing DB Application Server Desktop Forms 11g Forms applet FMBs, PLLs, OLBs Shared Security Mobile Win CE ADF Business Components View Objects Business Logic to DB Web Services.NET Methods

11 The 6-weeks Migration Work Biggest Challenges: TIME = Meeting the end April deadline INTEGRATION = Making technologies work together Our solutions for managing time : Make accurate estimations Avoid surprises, at least the bad ones How: analyze in detail to know exactly what to do, use analysis tools But avoid paralysis by analysis Have and follow a clear process plan

12 PITSS.CON Forms Modernization Process Any Forms version Analysis Phase 1: Forms Preparation SOA SOA SOA Cleaning Unused Obj., Redundancies Business Logic to Database Phase 2: 11g Upgrade Forms 11g Forms11g Upgrade & Test SOA Phase 3: Migration SOA Phase 4: Application Fine-tuning Phase 5 ADF ADF Architecture & Estimation ADF 11g Migration Model Layer Fine-tuning User Interface Enhancing UI Business Logic Redesign Integration & Test SOA APEX Architecture & Estimation SOA APEX Migration Data Management Fine-tuning User Interface, Navigation, Processes UI Business Logic Redesign Integration & Test APEX Any-GUI Data Management Fine-tuning User Interface, Navigation, Processes UI Business Logic Redesign Integration & Test PITSS.CON Re- Engineering Quality Assurance Documentation Iterations Technology Co-Existence

13 Analysis Tools: FMB Navigation Flow (generated with PITSS.CON) List of Modules: Initial list of FMB modules Modules added at kick-off Modules added after the navigation flow analysis Navigation = Call_form, open_form

14 Making accurate Time Estimations Challenge: How to put numbers behind individual modules? Forms Modules vary in size Modernization tasks vary in complexity among projects Know-how varies among project teams PITSS.CON Complexity Analysis Report Estimating total application complexity Breaking down to individual modules And individual project phases

15 Application Cleaning: PITSS.CON Unused Objects Analysis In average, 30% of Forms objects are unused or redundant What to do with the unused code? A. Leave it there (Never touch a running system) B. Move unused code to database (Out of sight) C. Dare to delete it What we did: deleted unused objects grouped similar code in libraries moved data management to DB Identifying and eliminating unused code from the start saves time and allows us to estimate work accurately. The Java/.NET developer does not need to figure out what to do with that code.

16 Reducing Redundancies Forms Objects/ Business Logic Components Reuse Modularity Moving logic to DB is a good opportunity to consolidate code and avoid repetition. We identified redundancies with PITSS.CON and then consolidated in flexible, parameterized DB functions and procedures. 100% match 70% match 100% match 50% match 70% match 30% match

17 Business Logic to Database: PITSS.CON BL Assistant In typical Forms applications we can move easily 30% of the logic to DB. In this project we moved 90%. Architecture benefits: reduced size, maintenance increasing code reuse Difficulty: separating DML from UI: DML to DB and UI to ADF/.NET

18 Analysis Tools: Data Management Flow (generated with PITSS.CON) Vital analysis for ADF/.NET developers Blocks Functions procedures Time to generate manually: 1 day per FMB module => we implemented it as standard PITSS.CON feature and gained time Triggers DB Tables

19 Client ADF Web Services Architecture JDeveloper Weblogic: ADF Runtime Web services: standard Oracle ADF components Desktop Forms applet Mobile Win CE.NET Challenges: - Connection Pooling - Multiple databases for each WebLogic Server (the server selects the suitable connection depending on device and user) - Database-defined multi-language (shared across different applications and technologies) DB Application Server Forms 11g FMBs, PLLs, OLBs Shared Security ADF Business Components View Objects Business Logic to DB Web Services Methods

20 1: excellent 2: very good 3: ok 4: not ok 5: poor 6: disaster How is the.net application looking like? What do end users think of the application? Look & Feel Performance Quality Maintenance X X X X

21 The classical question: Would we do it again? YES!! Definitively! Stressful? Yes. But clearly the most challenging and interesting project in the last years. Read our Article in DOAG News 06/2013 PITSS Project Team (left to right): Madi Serban, Mathias Waedt, Rastislav Misecka, Bahar Us

22