1 / 16

DMS 2.0

DMS 2.0. Jdeveloper Plan. Vision Statement. To migrate our DMS system from Oracle Forms to Java EE. Also, to build the skills in-house to maintain and build new system after the migration is completed. Migration Objectives. Use industry standard technologies.

beverly-johns
Download Presentation

DMS 2.0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DMS 2.0 Jdeveloper Plan

  2. Vision Statement To migrate our DMS system from Oracle Forms to Java EE. Also, to build the skills in-house to maintain and build new system after the migration is completed.

  3. Migration Objectives • Use industry standard technologies. • Leverage existing staff’s knowledge base. • Mix mentoring and training into Development. • Retain the Oracle DBMS. • Modernize the user interface.

  4. Technology Decision • As an Oracle shop, we naturally gravitated toward an Oracle product. We were especially impressed by the amount of support that Oracle has provided to the Oracle Forms and PL/SQL expert who is transitioning to this new world. • Which Technology Realm? • Which Development Tool? • Which Technology Stack? • Which Persistence Layer? • Which additional Frameworks to help migration?

  5. Which Technology Realm? • Decision: Java EE • Industry Standard. • Oracle is focusing on it. • Available anywhere, any time.

  6. Which Development Tool? • Decision: Jdeveloper11g • Template Driven • Reason: • Contains Oracle Application Development Framework(ADF). • Optimized for Oracle Databases. • Standard Oracle Development Tool. • Relatively familiar environment for Forms Developer.

  7. Which Technology Stack? • Decision: Oracle ADF frameworks • Reasons: • Strong support in Jdeveloper. • Declarative programming • More familiar to PL/SQL and Forms developers. • Oracle supports them • Vendor support vs. community support. • Oracle is using them for Fusion Apps.

  8. Which Persistence Layer? • Decision: ADF BC • Reasons: • ADF BC is better suited for Oracle DB than EJB. • Easier than EJB and TopLink for traditional Oracle Developers. • Simple to develop – less Java code. • Highly-evolved.

  9. Which View/Controller Layers? • Decision: 11g ADF Faces/JSF • Reasons: • Oracle is using in Fusion Apps. • Excellent support in Jdeveloper. • ADF Faces. • Oracle supported.

  10. Which Add’l Frameworks? • OraFormsFaces • Toolkit to embed Forms in a Web Application to co-exist with Java apps. • JHeadstart • Extension for Template – based automation of ADF development.

  11. The Team • Leverage existing Staff PL/SQL knowledge. • Building infrastructure for a Template based approach is key. • All Staff has a minimum of 7+ years in Oracle Development. • Adopting Jdeveloper and ADF would be a more natural transition for Form Developers.

  12. Market Summary • Main benefit is having Oracle and community to support your investment into Java. • The migration will allow us to open the door to a Rich Internet Application experience and not be locked into a close Framework as Oracle Forms has been in the past. • Plus future is secure with Fusion Apps being on same Technology Stack.

  13. Opportunities • Migrating the DMS system in 3+ years to Java. • Transitioning the Staff to Java in 2 years. • Establish New Development Methodology. • Bring Web 2.0 technology into DMS 2.0 • Enhanced the User Web experience with Dashboards. • Look into Mobile Technology for DMS 2.0.

  14. Business Concept • Migrate into a Rich Internet Application with current DMS functionality. • Explore Web 2.0 capabilities into future DMS 2.0 system. • Provide faster updates and enhancements thru Web deployment. • Integrate new services and existing process into DMS for a more homogenous system.

  15. Resource Requirements • List requirements for the following resources: • 4 Developers, 1 Java Developer, 1 Architect, 1 DBA, and 1 Unix Admin. • Jdeveloper, Subversion, TOAD, Testing Tool, etc. • Provide Training, books, and Java Mentoring. • Migration Tools to speed up conversion of system. • Consulting Services for resource shortage.

  16. Risks and Rewards • Risks is 3 years after an aggressive schedule. • We will manage it by evaluating Migration paths, Skills of Staff, and Project Modules complexities. • Choosing Oracle Jdeveloper and ADF will provide the support and Technology to succeed now and in the future. • We should be left with a maintainable and current supported system by staying with Oracle Technology.

More Related