XMAP - XPages Migration: Approach & Plan
•Descargar como PPT, PDF•
3 recomendaciones•2,946 vistas
An unique approach developed by Maarga Systems in XPages Migration. The webinar presented by Venkatesh - CEO of Maarga deals with technology trends that's pushing the adoption of XPages development and how migration can be done from old Lotus Note applications. XMAP - XPages Migration: Approach and Plan is a successful methodology that Maarga propounds in this area.
Recomendados
Más contenido relacionado
Destacado
Destacado (17)
Más de Maarga Systems
Más de Maarga Systems (12)
Último
Último (20)
XMAP - XPages Migration: Approach & Plan
- 2. What is XPages Business Case Why Xpages? Go Mobile Enhance User Experience XMAP: Xpages Migration – Approach & Plan Assess Prioritize Construct Implementation Considerations Skilling your team Support readiness Q&A
- 3. What is your organization doing about XPages? Nothing Exploring Piloting Full Steam NA
- 6. Web Application Development Framework Addresses Known Limitations of Domino A Better Web Development Experience Based on Java Server Faces (JSF) Designed for Web 2.0 Leverages Domino/Web Developer Skills Enable Enterprise Scale Applications
- 8. XMAP: XPages Migration – Approach & Plan
- 9. The Mobile (post PC) Era Social Business Smart Systems – Contextual Predictive Analytics Revolution in UX In Memory Applications Cloud Everywhere (Iaas, PaaS, SaaS)
- 10. Cost to go live - 8% of TCO 92% after going live Rip & Replace disruptive Reverse Engineering Complex
- 12. Executive Summary Recommendations
- 13. One Time Costs Benefits Hardware, Software User Productivity Consulting Innovation (Revenue) Migration Reduction in Support Tools Support Spurt IT Training User Training Ongoing Costs Maintenance Support
- 15. Repeat Controls, Nested Repeat Controls Styling Theming AJAX, Partial Refresh Custom UI Controls Internationalization
- 16. Ready to go (8.5.3 Upgrade Pack 1 has XPages Extension Library) Sencha/Touch Frameworks Native Mobile Applications Write Once Run Anywhere Custom Develop for each platform
- 17. Mix and match data sources Get complex data into views Make Dashboards available on Mobile Devices
- 18. What are your users demanding? 1. Mobile Interfaces 2. Slicker UI 3. Better Usability 4. Better Performance 5. Dashboard Views
- 19. XMAP – XPages Migration: Approach & Plan
- 22. Finance Marketing Sales Manufacturing Distribution Promotion Price Demand Demand Budgeting MRP Planning Simulation Planning Account Promotion Sales Force Inventory Shipping Receivables management Management management Accounts Production Package Payable management Tracking General Ledger Loss Product Costing Management Supplier Raw Material Interfaces Procurement Fixed Asset Management Payroll Promotion CRM Inventory Cash Effectivemness Satisfaction management management Benchmarking Financial Pipeline Report Reports Salles Lead Balance Sheet Tracking
- 23. CRM Opportunity Time & Engagement Mgmt Mgmt Expense Contact Mgmt Contact Mgmt Billing Detail Accounting Sales Orders Fee Schedules GL AP Forecasting / Pipeline Approval Workflow AR AM Telemarketing IC _ knowledge Project Definitions Payroll Lead Sharing Mgmt Project Schedules Project Customer Acccounting Alliance Mgmt Support Mgmt MS Project Dashboard Resource Mgmt Candidate Mgmt Practice Mgmt Staffing, Tracking, Resume Mgmt Sales MGT. Availability Manager Mod Job Orders Skill Training IT Support Requisitions Career Helpdesk Development Exchange Website Intranet Company HR Forms Directory Workflow
- 25. HIGH Business Importance LOW System Adequacy HIGH LOW
- 28. Couple of Apps The WOW Factor Touch, Feel the end product Basis for Business Case Excite Influential Users Observe, Analyze, Apply
- 29. Use of Automated Migration Tools Program Management Get Users Involved Re-skill Developers Global Delivery Capabilities
- 30. Migration to 8.5.x Incremental vs. Big Bang Coexistence
- 32. XMAP – XPages Migration : Approach & Plan
- 33. Multiple Developers Reuse Web Skills Types of Developers Traditional Lotus Developers Java Developers
- 34. Reuse existing Skills Mapping SSJS to LotusScript/@Formula Architectural Differences Resources
- 35. Training your L1 Helpdesk L2 Support – What skills your team needs to brush up on Supporting Web App vs. Notes App – the considerations
- 37. Pedestal #524 Meet XPages Developers, Architects Listen to some real stories See some sample work
Notas del editor
- What is your organization doing about XPages? Nothing. We are sticking with Status Quo Exploring. We are just getting familiar with what the technology is and how to migrate. Piloting. We are doing a pilot migration of some applications Full Steam. We have gone and committed significant resources to XPages NA - Please choose this if you are an SI, or if you don't have Notes Applications
- Meet Geroge IT Director Around 1000 users Mixed feelings about his Notes infrastructure Has 10 critical systems running on Notes, among the nearly 1000 DBs in his infrastructure Loves Notes for security, replication & backward compatibility Takes flak from users on usability, mobile access George’s Challenge 10 years worth of data in Lotus Notes databases. Business Logic in applications difficult to reverse engineer Notes Databases functional, but lacking in pizzaz – dashboards, mobile access etc. Some vocal and powerful opponents to Notes apps in his organization. Does not have the bandwidth to redo the apps Not sure which way to go
- From Cool Tools … Cool Pages … XPages Visual Web page construction Advanced UI controls Drag and drop development Instant Application Development XML markup with source Full control of HTML Presentation using CSS Business logic using JavaScript Leverages existing NSF assets Web agents, formulas, security, … XPages Value Proposition Provide a better Web development experience to Domino developers Can be used to incrementally enhance an existing application or write a brand new one Fully integrated within Domino Designer Decreases the time for writing Web Applications Solves problems expressed by the Domino community Known limitations are addressed UI/Data separation, HTML generation control, Server state, Localization, Extensibility, … Fully integrated with Domino Web server Designed for Web 2.0 Based on an extended version of Java Server Faces (JSF) Advanced set of controls Web pager, Section, Tabbed Panel, … Advanced View layouts using repeated sections Native support for Ajax behaviors Partial refresh, available to every event Typeahead Comes with the Dojo JavaScript library Natively leverages Dojo widgets (RichText, Date/Time picker, … ) Gives easy access to Dojo modules and widgets Leverages Domino/Web Developer Skills Leverages the existing design elements (Forms, Views, Agents, … ) Forms carry the document schema (data definition) and some business logic (computed fields, … ) Views used to query the Domino store Agents can be called using the back-end API JavaScript is used as the main scripting language JavaScript used on the client and on the server Simple actions are also provided for common tasks Leverages and exposes the back-end API JavaScript accessors on top of the Java back-end API JavaScript has been extended to support @Functions() Complete Control of the Rendering Look and Feel is driven uniquely by CSS Full support for CSS classes or inline styles Uses CSS file resources Support Themes for skinning an application Predefined styles for controls A theme can be defined locally, in an NSF, or globally 2 themes provided out of the box HTML tags/attributes can be embedded within XPages Enables Enterprise Scale Applications Extensible architecture Custom controls An XPage can call any Java code/library JSF config files can be used to provide custom options Extended data access capability Applications can access data located in multiple NSF databases Multiple documents/views can be displayed on the same page Built-in localization and internationalization support Support String localization and dedicated pages per locale Automatic support for user time zone
- Business Case Executive Summary Summarize Feasibility Justification Need Recommendation Drivers Purpose Drivers Problem Statement Aims/Objectives Intended Use (audience and timing) Organizational Changes required Critical Success Factors Methods Alternative Solutions and data Primary Alternatives considered – Staying Put with Notes Client Apps, Current Paradigm of Web Apps, Xpages, Migrating out of Lotus Notes Any comparable projects Benchmark models Estimation approach used ( ballpark, parametric MPP etc) Scope / Approach Scope - In/Out Timeframe and resources availability Constraints in alternatives considered Financial Analysis Evaluate investment effectiveness Compare alternate solutions Benefits 'Costs Expected primary cost areas Impact Benefits Costs Analysis of alternate solutions Risks and Contingencies Key parameters that impact the decision Contingent actions Risk Parameters (financial, Operational, Cultural, Market) Recommendation Conclusion Specific actions taken to manage uncertainities throughout the project Main Topic
- Learnability How easy is it for users to accomplish basic tasks the first time they encounter the design? Efficiency Once users have learned the design, how quickly can they perform tasks? Memorability When users return to the design after a period of not using it, how easily can they re establish proficiency? Errors How many errors do users make, how severe are these errors, and how easily can they recover from the errors? Satisfaction How pleasant is it to use the design
- Before jumping into assessing your Lotus Portfolio, pause. Have you done this? Business architecture: Major business activities, functions, and their supporting processes. Information architecture: Information f lows, data entity relationships, and enabling tools Application architecture: Software programs that automate and support business processes Technical architecture: The computing infrastructure (i.e., systems software, hardware, network) that supports the information and application architectures.
- In this case, the company has dozens of applications supporting the business. The applications have been categorized along two axes. The first is by major functional area, such as finance, manufacturing, and marketing. For most companies, the applications should be categorized into fewer than a dozen business-unit or functional categories. The second axis segments the systems by the three primary functions that the application might provide: 1. Planning and control: Systems that aid in operational planning, configuration of business systems, and general control of the business. 2. Operations: Transaction-driven business applications; for example, accounting, order entry, manufacturing planning, inventory control, warehouse management. 3. Reporting and analysis: Applications that primarily aggregate data from the planning and operations systems to produce reports and analysis, which are used to operate the business.
- After the full inventory of applications is categorized, the team analyzes how the applications interface with each other and with external applications. This analysis includes understanding the business event or calendar which drives application interfaces, as well as the communication content, method, and protocol. An application architecture diagram that illustrates the current interfaces between the applications discovered in the application portfolio process is shown in Exhibit 8.4. Several key items are depicted, including: • The application or application submodule and its primary functions. • Interfaces between the applications or modules. • Notation of the platform/third-party software that runs the application Peoplesoft, Lotus Notes, Microsoft
- Parameters Number of Users Frequency of Use Criticality Tools Catalog.nsf Custom Scripts Third Party Tools GBS Domain Patrol
- First, the team must assess the current system’s adequacy. If no major modifications are made to the current application, how long can the business continue to use it? Develop a scale to assess system adequacy (e.g., 1 to 10) based on criteria set by the business community (e.g., Low = Next 3 to 6 months, Medium = Next 6 to 24 months, High = Next 2 to 4 years). The second piece of the analysis is to determine the relative value of the application to the business. Chapter 15 outlines several methods for determining the business value of a project or application and highlights the variables that the team may want to consider. After the current system adequacy and potential business value of the system have been determined, the options can be plotted as depicted in Exhibit 8.7. If the business importance of the application is low, then the application should receive little or no new funding or attention. All applications with low business importance are candidates for retirement. In the case where the system adequacy is low, the team should add projects to the project inventory that show the cost savings or other value generated by decommissioning the system. For low-value, high-system adequacy systems, the team should adjust service levels and resource focus to minimize new investment or effort in
- WOW FACTOR Take a signifcant app Add mobility Add Location Awareness Add mobility for approval Completely upgrade user experience Beef up the server, because all processing happening on server .. if you are looking at working off of the server, and moving out of the client
- 500 Error Handling Server Related vs. Client Errors Following a defined process of updates to applications on server
- Got equipped – Knowledge is Power Decided to use IT department budget for Assessment, Prioritization & Pilot Got a couple of enthusiastic application owners signed up for a phased rollout Became a Hero!