Click here to load reader
Upload
aamir97
View
6.587
Download
10
Tags:
Embed Size (px)
DESCRIPTION
Citation preview
2.
Contents
3. Why Migrate?
4. Migration Concerns Will the integration with other components, products change? How can I achieve migration without impacting my current customers? How much will it cost? How long will it take? What technology / business benefits will I get after migration? My current application works fine. Why do I need to migrate? Where will I get skills / training for the migration? How will I accommodate the migration effort in my schedule? 5. Migration Requirements
6. Stakeholder Perspectives
7. Stakeholder Perspectives
8. Stakeholder Perspectives (contd.)
9.
Contents
10. J2EE Evolution
11. App Server Market
corporate relationships, and cost 12. App Server Market (contd.)
13. Role of App Server Vendors
14. Contents
15. Upgrade
16. Cross App Server Migration
17. Cross Hardware/OS Migration
18. Cross Software Platform Migration
This can be categorized as a rewrite/re-architecture, and not migration 19.
Contents
20. Application Footprint J2EE APIs Messaging Security/SSO Portal Legacy Reporting Other Internal Applications Workflow External Applications 21. J2EE Migration Considerations
22. J2EE Components and APIs
23. Integration
24. Third Party Vendors
25.
Contents
26. Characteristics of Enterprise Applications
27. Characteristics of Enterprise Applications
28. Large Scale Migration Challenges
29.
Contents
30. Migration Phases 31. J2EE Migration Methodology 32. J2EE Migration Methodology Highlights
33.
Contents
34. Migration Approach Infrastructure Set up Program Management Testing Services Technical Migration Perform unit testing for components Prepare migration strategy Migrate codeto new environment Integration, UAT, stress and regression testing Develop sizing and scheduling estimates Collect Information on Testing processes, Tools Project management, Risk management, Resource management, Knowledge management, Change management and Leadership, Quality & Metrics Management Understand As-Is and To-Be Infrastructure Program Managed Application Server Migration Tracks Perform IDE testing for application Analysis, Planning & Scheduling Code Migration & Deployment Testing and Release Transition and Warranty Deploy codein new environment Define testing strategy & plan Complete DRR request and deployment map Verify availability of target environments Review and Standards Prepare review documents, participate in review check points and work with standards groups, to align the application architectures with technology standards within the organization. 35. Migration Analysis 1 2 3 4 5 6 7 2 3 4 5 7 3 3 2 3 4 5 6 7 2 3 4 7 A B C G D, J E F H N I,L M K Risk Time Activities 1 => Application SMEs not known2 => Migration effort not known 3 => Schedule and functional dependencies not analyzed 4 => Infrastructure requirements not determined 5 => Newfeature benefits not evaluated 6 => Application Characteristics not known 7 => Alignment with standards not assessed Risks A => Identifyapplication stakeholders B => Prepare sizing template C => Feedback and finalization of responses D => Analysis of data collected E => Prepare a feature cost vs. benefit analysis F => Analyze third party tool dependencies H => Analyze integration dependencies I =>L => Prepare Training Plan M => Get Stakeholder buy-in N => Finalize strategy and migration plan Activities A structured approach mitigates the risk of migration and optimally leverages the features of the new platform Migration strategy, planning, & execution 36. Detailed Planning Activities Project Inception Preparation of application inventory and templates Information Gathering Team interviews and data collection Analysis Sizing, estimates. and schedule Prepare and finalize application inventory Refine pre-defined sizing and analysis templates to for enterprise application migration needs Review & Publication Estimates Review, publication and presentation to stakeholders Meet with subject matter experts for each application to capture application characteristics in the templates Analyze and estimate testing and training efforts for the development and production environments Meet with application teams to refine the process for estimating the effort Prepare migration cookbook for WAS migration specific to target environment Produce migration estimates based on dependencies on Java architecture components, 3 rdparty libraries and products, and integration requirements Refine and enhance sizing and effort formulas and factor in each applications business constraints to prepare initial schedule Collect information on existing strategy for individual applications Present migration plan to key stakeholdersFactor in per-application project costs and overall PMO costs Migration Estimates and Analysis Workbook Application characteristics Executive presentation Migration estimates, schedule , Analysis Workbook , andMigration Cookbook Determine the future states for the APIs and third party versions based on enterprise architecturestandards ACTIVITIES TASKS OUTPUT 37. Example - Migration Analysis Workbook Illustrative This workbook constitutes a framework for WAS migration analysis and estimation. It consists of templates to capture the various facets of an enterprise level migration involving applications owned by multiple portfolios/LOBs The contents of this analysisand estimation workbook can be customized for the client, based on the requirements and the scope of the engagement. Worksheets can be added or deleted from this workbook 38. WebSphere Upgrade - Transition 3.5x 2.03 4.0x RecommendedEnterprise Architecture Components maynot be used MQ Development Environment VAJ WSAD Source Code VAJ CVS IDE App Server Versions Run Time Environment Sun Solaris, UNIX APIs Servlets 1.x 2.1 2.2 JSPs 0.9 1.0 1.1 EJBs 1.0 1.1 JDK/JRE 1.2.x 1.3.x 5.1 Recommended JAT Components used MQ Development Environment WSAD 5 Source Code CVS IDE App Server Version Run Time Environment Intel, Linux APIs Servlets 2.3 JSPs 1.2 EJBs MDB 2.0 JDK/JRE 1.4 CURRENT STATE FUTURE STATE J2EE 1.3 UDB 7.x Sybase UDB 8.x Sybase Illustrative 39. Migration Prioritization Technical Complexity Business Criticality Quadrant 4 Technical Index = Low Business Index =Low Quadrant 1 Technical Index = High Business Index = High Quadrant 2 Technical Index = Low Business Index = High Quadrant 3 Technical Index = High Business Index = Low App 1 App 5 App 4 App 3 App 2 App 7 App 6 40. Cost Estimates
Illustrative 41. Migration Schedule Illustrative 42. Contents
43. Migration Aids
44. Migration Frameworks
45.
Contents
46. Migration Best Practices
47. Migration Best Practices (contd.)
48. Thanks Ajit Sagar [email_address] http://www.ajitsagar.javadevelopersjournal.com