Your SlideShare is downloading. ×
0
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
WebSphere as a platform for mobile apps
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

WebSphere as a platform for mobile apps

1,465

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
1,465
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
30
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. WebSphere as a platform for mobile appsHenrik SjöstrandWebSphere Technical SalesIBM Software Group, Swedenhenrik@se.ibm.com
  • 2. JavaScript Frameworks for Rich Internet Applications IBM invests in the Dojo framework. Why Dojo? • Open source project • Comprehensive feature set • Commercial-friendly licensing • Globalization and accessibility support (WAI-ARIA) • Well architected http://dojotoolkit.org/ • Active user communityAlternatives: jQuery, YUI, Ext JS, MooTools, Prototype, script.aculo.us, DWR and others... but often more targeted at spicing up a web page
  • 3. So what does a Dojo application look like?
  • 4. Mobile: Different Approach for Different Requirements Web Mobile Web Hybrid Mobile Native Mobile Application Application Application Application Characteristics Desktop and mobile using open Mobile only using open web Mobile only, app runs on the Mobile only, developed using web (HTML, JavaScript) client (HTML5, JavaScript) client device, but leverages open web native languages or transcode programming models programming models (HTML5, JS) via JavaScript to native via MAP tools bridge Limited to no device-specific Off-line capabilities Native appearance and functionality Native device capabilities device capabilities, performance (GPS, camera, contacts) Mimic native appearance Mobile Browser Execution AppStore download and install Traditional Trade-offs (without MEAP/MAP) Richness of Mobile Presentation / Services Portability (cross-device reuse) Maintenance Cost (TCO)5
  • 5. Mobile: Different Approach for Different Requirements Web Mobile Web Hybrid Mobile Native Mobile Application Application Application Application a, Characteristics v t native languages or a Desktop and mobile using open Mobile only using open web Mobile only, app runs on the Mobile only, developed using web (HTML, JavaScript) client (HTML5, JavaScript) client device, but leverages open web to native via , J transcode h programming models programming models (HTML5, JS) via JavaScript bridge + ig + MAPLtools Limited to no device-specific functionality Off-line capabilities Native device capabilities (GPS, camera, contacts) /C lver Native appearance and device capabilities, performance C i Mimic native appearance S Mobile Browser Execution AppStore download and install Traditional Trade-offs (without MEAP/MAP) Richness of Mobile Presentation / Services Portability (cross-device reuse) Maintenance Cost (TCO)6
  • 6. Mobile: Different Approach for Different Requirements Web Mobile Web Hybrid Mobile Native Mobile Application Application Application Application a, Characteristics + Desktop and mobile using open Mobile only using open web Mobile only, app runs on the native languages or a v t Mobile only, developed using L web (HTML, JavaScript) client (HTML5, JavaScript) client device, but leverages open web to native via , J transcode ig h M jo programming models programming models (HTML5, JS) via JavaScript bridge + + MAPLtools HT Do /C lver Limited to no device-specific Off-line capabilities Native appearance and functionality Native device capabilities device capabilities, performance (GPS, camera, contacts) C i Mimic native appearance S Mobile Browser Execution AppStore download and install Traditional Trade-offs (without MEAP/MAP) Richness of Mobile Presentation / Services Portability (cross-device reuse) Maintenance Cost (TCO)7
  • 7. Mobile: Different Approach for Different Requirements Web Mobile Web Hybrid Mobile Native Mobile Application Application Application Application a, Characteristics + Desktop and mobile using open 5 ile + Mobile only using open web Mobile only, app runs on the native languages or a v t Mobile only, developed using L web (HTML, JavaScript) client L (HTML5, JavaScript) client device, but leverages open web to native via , J transcode h M jo M ob ig programming models programming models (HTML5, JS) via JavaScript bridge + + MAPLtools HT Do HT jo M /C lver Limited to no device-specific Off-line capabilities Native appearance and functionality Native device capabilities device capabilities, performance (GPS, camera, contacts) C i Do S Mimic native appearance Mobile Browser Execution AppStore download and install Traditional Trade-offs (without MEAP/MAP) Richness of Mobile Presentation / Services Portability (cross-device reuse) Maintenance Cost (TCO)8
  • 8. dojox.mobile widgets (iPhone & Android themes) Heading with a back button Round Rectangle List Round Rectangle List Edge-to-Edge List (Variable Height) Edge-To-Edge List List with Buttons Tab Container Edge-To-Edge List in a Tab
  • 9. Advanced dojox.mobile widgets
  • 10. 11 Web 2.0 & Mobile Feature Pack for WebSphere With WAS V6.1 & 7.0 Web 2.0 Web Web 2.0 OSGi Apps Java EJB 3.0 Services CEA XML SCA & Mobile & Mobile & JPA 2.0 Batch J2EE 1.4 WAS V6.1 Web Java EE 5 EJB 3.0 Services WAS V7 With WAS V8 Web 2.0 & Mobile Dynamic Scripting CEA XML SCA OSGi Apps Java Java EE 6 WAS V8 & JPA 2.0 Batch No additional cost. Supported by IBM.
  • 11. Development Tooling In Rational Application Developer12
  • 12. Mobile: Different Approach for Different Requirements Web Mobile Web Hybrid Mobile Native Mobile Application Application Application Application a, Characteristics + Desktop and mobile using open 5 ile + Mobile only using open web Mobile only, app runs on the native languages or a v t Mobile only, developed using L web (HTML, JavaScript) client L (HTML5, JavaScript) client device, but leverages open web to native via , J transcode h M jo M ob ig programming models programming models (HTML5, JS) via JavaScript bridge + + MAPLtools HT Do HT jo M /C lver Limited to no device-specific Off-line capabilities Native appearance and functionality Native device capabilities device capabilities, performance (GPS, camera, contacts) C i Do S Mimic native appearance Mobile Browser Execution AppStore download and install Traditional Trade-offs (without MEAP/MAP) Richness of Mobile Presentation / Services Portability (cross-device reuse) Maintenance Cost (TCO)13
  • 13. Mobile: Different Approach for Different Requirements Web Mobile Web Hybrid Mobile Native Mobile Application Application Application Application a, Characteristics + Desktop and mobile using open 5 ile + Mobile only using open web + 5 ile Mobile only, app runs on the native languages or a v t Mobile only, developed using L web (HTML, JavaScript) client L (HTML5, JavaScript) client L device, but leverages open web Mbridgeob a (HTML5, JS) via JavaScriptp to native via , J transcode h M jo M ob ig programming models programming models + MAPLtools HT Do Limited to no device-specific functionality HT jo M Off-line capabilities HT jo M neG Native device capabilities + /C lver Native appearance and device capabilities, performance C i Do Pho (GPS, camera, contacts) Do S Mimic native appearance + Mobile Browser Execution AppStore download and install Traditional Trade-offs (without MEAP/MAP) Richness of Mobile Presentation / Services Portability (cross-device reuse) Maintenance Cost (TCO)14
  • 14. Mobile – End-to-End Devices Infrastructure
  • 15. IBM WebSphere ® Typical Three-Tier Server-side Architecture Web Server Tier App Server Tier Database Tier © 2011 IBM Corporation
  • 16. IBM WebSphere ® Solving the overloaded DB’s and response time issue eXtreme Scale & DataPower XC10 Web Server Tier App Server Tier Elastic Data Grid Database Tier DataPower XC10 for simple data oriented scenarios: • HTTP Session Replication • Elastic Dynacache • Web Side Cache eXtreme Scale for maximum flexibility covering data and application oriented scenarios © 2011 IBM Corporation
  • 17. IBM WebSphere ® Maximizing resource utilization and availability Virtual Enterprise & IBM Workload Deployer Web Server Tier App Server Tier Database Tier Virtual Enterprise On Demand Routers © 2011 IBM Corporation
  • 18. IBM WebSphere ® Solving the security issues with Web 2.0 & Mobile Apps DataPower XS40 & XI50 DMZ Web Server Tier App Server Tier Elastic Data Grid Database Tier © 2011 IBM Corporation
  • 19. IBM WebSphere ®IBM Mobile Technology Preview The IBM mobile technology preview will provide customers with early access to IBM’s mobile capabilities and demonstrate our approach to mobile application design, distribution, and management Device and Server Infrastructure Demonstrations, Samples, & Capabilities Documentation Support for Android Demonstrations & Samples Mobile Server Capabilities •Mysurance – Provides a showcase hybrid on WAS v8.5 Alpha Liberty application that demonstrates all capabilities in an end-to-end insurance scenario •Dojo Showcase – Highlights the full SOA & Connectivity breadth of Dojo capabilities •Hybrid Showcase – Demonstrates Existing Back Ends integration with all available native device Server runtime functions •Acts as central point for •Simple Notifications Client – IllustratesClient runtime notification functionality and development integration to back-ends•Provides a container for developing techniqueshybrid applications, written in HTML •Hosts key capabilities such asand JavaScript, that deliver a user registry and notificationscompelling touch-based user •Runs on IBM’s Liberty runtimeexperience and have full access to Management Concepts •Customers will be able tonative device functions integrate and extend existing To be demoed•Customers will be able to rapidly applications and services todevelop, package, and distribute maximize existing investments Application Managementmobile applications through internaland external app stores by Notification capability •Centralizes control over your mobileleveraging existing skills and assets •Delivers notifications to users apps including policy-based access, through maintained connection versioning, updating, tracking, and between client and server wipe/remove •Customers will be able to •Customers will be able to distribute engage users with notifications of apps to employees and control access to time sensitive information or those apps and their enterprise data actions to take © 2011 IBM Corporation
  • 20. IBM WebSphere ®WebSphere – Edge to Edge Application Optimization © 2011 IBM Corporation
  • 21. Thank you!
  • 22. Cross platform mobile apps with WebSphereHenrik SjöstrandWebSphere Technical SalesIBM Software Group, Swedenhenrik@se.ibm.com

×