IBM Worklight - Technical Overview


Published on

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

IBM Worklight - Technical Overview

  1. 1. IBM IDR SPGI – IBM Mobile SolutionsDecember 12th 2012 Worklight Overview © 2012 Worklight, Inc. All rights reserved. The information contained herein is the proprietary and confidential information of Wo rklight.
  2. 2. Worklight Introdcution Worklight is an open, complete and advanced mobile application platform for HTML5, hybrid and native apps.2
  3. 3. Mobile Apps – Top Challenges Creating rich, yet cost-effective mobile apps in a fragmented technological landscape. Multiple apps, building in house, moving away from proprietary langs. Connecting the enterprise back-end services in a secure and scalable manner Controlling the growing portfolio of applications deployed “in the wild”3
  4. 4. Worklight Overview Worklight Studio The most complete, extensible environment with maximum code reuse and per-device optimization Worklight Server Unified notifications, runtime skinning, version management, security, integration and delivery Worklight Runtime Components Extensive libraries and client APIs that expose and interface ← with native device functionality Worklight Console A web-based console for real-time analytics and control of your mobile apps and infrastructure4
  5. 5. Worklight Architecture5
  6. 6. Worklight Application Types Browser Access Web Apps Hybrid Apps - Web Hybrid Web Hybrid Apps - Mixed Hybrid Mixed Native Apps Written in HTML5 HTML5 code and User augments web Platform-specific. JavaScript and Worklight runtime code with native Requires unique CSS3. Quick and libraries packaged language for unique expertise, pricy and cheap to develop, within the app and needs and long to develop. but less powerful executed in a native maximized user Can deliver higher than native. shell. experience. user experience. Mobile Browser Native Shell Native Shell Native Application 1001010101011101001010 Web Code Web Native 0100101011101001001101 0101010100100100101111 Web Code <!DOCTY 1001010 0010011001010101001010 <!DOCTYPE html PUBLIC 1010111 <html> PE html 1010100101010101010101 PUBLIC 0100101 <!DOCTYPE html PUBLIC <! - - created 2003-12-1 0101010 0101011111100000101010 <head><title>XYZ</title created <html> 1010010 1010101001001010101010 <! - - created 2003-12-12 - </head> 2003-12 </p> 0100101 1010001111010100011110 - </body> </html> </body> 1110010 1010011101010111110010 <head><title>XYZ</title> 0110010 </head> </html> 1101111010001011001110 <body> </p> </body> </html> Device APIs Device APIs Device APIs Browser Access Downloadable Downloadable Downloadable6
  7. 7. Downloadable (Native) Apps High-quality user experience and full Application device access. File System Stores (on mobile device) Platform-specific, requires unique Native App expertise, expensive to (Java/Objective-C/C#) develop and maintain. Mobile Operating System7
  8. 8. Web Apps Web Server Written in HTML5 JavaScript and CSS3. Mobile Browser Quick and cheap to develop. Native App (Java/Objective-C/C#) Less powerful than native and limited device access. Mobile Operating System8
  9. 9. Hybrid Apps Combines best of both worlds: Application File System Stores (on mobile device) Primarily written in HTML5, CSS, JS while Native Container allowing full access to device capabilities. HTML, CSS, JavaScript Mobile Operating System9
  10. 10. Worklight Studio Integrated Development Environment (Eclipse Plug-in) Application development using native and/or familiar web technologies: • HTML5 • CSS3 • JavaScript Integrated device SDKs allow direct access from within the IDE to emulators and code debugging utilities10
  11. 11. Integrating Best-in-class Tools Worklight is compatible with prominent HTML5 libraries and tools:11
  12. 12. Preview in Browser12
  13. 13. Incorporated Device SDKs13
  14. 14. Incorporated Device SDKs – Continued14
  15. 15. Apps – Single Shared Codebase Common code placed in primary file Environment optimization code is maintained separately15
  16. 16. Apps – Hybrid Coding – Native and Web Combine HTML5 and native- based pages in the same application Call native code from HTML- based pages Display HTML and native components together on the same page16
  17. 17. Back-end Integration Secure back-end integration. XML-based declarative specification. Multi-source data mashups. Eclipse plug-in supporting auto-complete and validation. Simplified adapter testing . Server-side debugging. Web services and JDBC integration. Access to session data and user properties.17
  18. 18. Back-end Integration – Adapters • Select an adapter to deploy • Right click on it Run As - Deploy Worklight Adapter • The Worklight Studio will archive the adapter code and deploy it onto the Worklight Server • You can see the deployed adapter in the Worklight Console18
  19. 19. Centralized Build Source Code Worklight Repository Build System Integ with RTC19
  20. 20. Dynamic Control of Deployed Apps • Centralized control of all installed applications and adapters • Remotely disable apps by device and version • Customize user messages20
  21. 21. What are Push Notifications? A Push Notification is the ability of a mobile devices to receive messages that are “pushed” from a server Notifications are received regardless of whether the application is currently running or not Notification may take several forms: • Alert – a pop-up text message • Badge – a small badge mark appearing next to the application icon • Sound alert21
  22. 22. Key Elements of Push Notifications Trigger • Behavior-based • Pre-defined • Rule-driven Content type • Universal versus Personalized • Open versus Protected • Lean versus Detailed • Time-sensitive versus Any-time Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi ullamcorper dictum User behavior orci, in iaculis sem faucibus eget. Vivamus non diam id dui volutpat semper. • Read only Lorem ipsum • Read/Write • Act-Outside-the-App Nice to have • Analytics, feedback, etc22
  23. 23. Availability of Mobile Push Notifications Services Apple iOS 3 Google Android 2.2 RIM BlackBerry 5 Microsoft Windows Phone 723
  24. 24. Push Services Management24
  25. 25. Direct Update App Versions relate to the native’s version. In addition, at any time, you can update the web resources within the App. This is useful for production Apps, but also reduces the development and testing overhead associated with re- installing the native App on a device or simulator. New web resources are packaged in .wlapp files and deployed to the server. An App accessing the server will find the new resources and refresh itself. Admins can also lock a version to prevent updating its web resources25
  26. 26. Direct Update – On-device Logic 1. Web resources packaged with app to ensure initial Native Shell offline availability 1 Download 2. Web resources transferred to Pre-packaged resources apps cache storage App Store 3. App checks for updates 2 Transfer • On startup • On foreground 3 Check for updates 4. Updated web resources Cached downloaded when necessary Worklight Web resources Server resources 4 Update web resource26
  27. 27. Runtime Skinning – Use Cases Skins provide support for multiple Different form factors in a single executable Screen Sizes file for devices of the same OS family. Skins are sub-variant of an Different environment. Screen Densities Packaged together in one App. Different Decision on which skin to use is done automatically at runtime. Input Method Support for HTML527
  28. 28. Direct Update - Distribution V1.0 Native Shell Web Code Web Updated Web Resources Worklight Server Resources for V1.0 <!DOCTYPE html PUBLIC <html> <! - - created 2011-12-1 <head><title>XYZ </title Worklight </head> </body> </html> Studio Maintains recent web resources Updated Web for native apps V1.0 and V1.1 Resources for V1.1 V1.1 Native Shell Develop: Web Code • Native app <!DOCTYPE html • Web resources PUBLIC Native + Web <html> Application Stores (*) <! - - created Download 2011-12-1 <head><title>XYZ Resources </title </head> </body> </html> (*) During development cycles, testers automatically get recent web resources via internal distribution mechanisms and not application stores.28
  29. 29. Securing Mobile Apps Protecting data on the Enforcing security device updates Secure challenge- App Jailbreak and Encrypted Offline Remote response on authenticity malware Direct update offline cache authentication disable startup testing detection SSL with Shell as Authentication Data Using device Proven server Code organizational integration protection id as 2nd platform identity obfuscation sandbox framework realms factor security verification Streamlining Providing robust Application Corporate security authentication and Security processes authorization29
  30. 30. Current Online Software Distribution Download 30-day evaluation version Documentation and wizards inside Studio Full documentation available online, Support via portal, forum, e-mail including over 40 online training modules30
  31. 31. Need Skills? Technical Overview Preparation Marketing Selling Resources This roadmap will guide you through the stages of building and taking your mobile solution to the market. Provides an overview, resources to learn more and actions you can take to help you succeed. Get access to our IBM roadmaps, the easiest way to get enabled: IBM Roadmap for Mobile Enterprise31
  32. 32. For More Information Resource Location 30-day Software Trial Online Training Documentation Product Resources Webinars Additional Info info@worklight.com32
  33. 33. Get Social with us @ibmmobile IBM ISV Mobility SPGI Group @iicbarcelona @dW_Spain @IBMTivoli_es @WebSphere_ES @IBMSoftware_es33
  34. 34. 34