Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (19)
Destaque
Semelhante a Worklight 5.0 Webinar 7 12 V2
Semelhante a Worklight 5.0 Webinar 7 12 V2 (20)
Worklight 5.0 Webinar 7 12 V2
- 1. Sean Ramsey, Mobile Sales Specialist seanram@us.ibm.com 614.420.0048 IBM Worklight: Powering Your Mobile Strategy © 2009 IBM Corporation
- 2. IBM Mobile Enterprise Agenda Introduction of Speaker/ Mobile Experience Mobile Adoption IBM's Mobile Foundation What is Worklight • Value prop • Client Example in app store • Components Differentiators Qualifying Criteria Open QA 2 © 2012 IBM Corporation
- 3. IBM Mobile Enterprise Mobile Apps – New Opportunities & Scale Challenge Mobile transaction volumes will rise from $1.6B in 2010 to almost $12B in 2014. Gartner In a recent survey, 72% of responding organizations stated they will deploy 1-5 mobile apps in the upcoming year. 18% said 6-10. MicroStrategy More firms are turning to apps to enhance the way customers interact with their products and services — and even boost their bottom lines. Wall Street Journal MicroStrategy Survey 3 © 2012 IBM Corporation
- 4. IBM Mobile Enterprise Polling Question #1 How many mobile apps will you have by the end of 2012? a. 0 b. 1-5 c. 5-10 d. More than 10 4 © 2012 IBM Corporation
- 5. IBM Mobile Enterprise IBM Mobile Foundation Development Firewall or Security Gateway Lifecycle Tools IBM End Point IBM Worklight Manager for Mobile Devices CastIron Hypervisor Edition Elastic Caching Mobile threats and IBM Mobile Foundation security SOA & Connectivity (Messaging, ESBs, Cloud Integration, Governance) Business Decision Social Analytics Process Management Management Software Enterprise Apps 5 © 2012 IBM Corporation
- 6. IBM Mobile Enterprise What Is Worklight Worklight is an open, complete and advanced mobile application platform for HTML5, hybrid and native apps. 6 © 2012 IBM Corporation
- 7. IBM Mobile Enterprise Hybrid Coding – Why Mix Native and Web? Write the majority of the code in reusable web languages Maximize user experience and achieve unique functionality with native code 7 © 2012 IBM Corporation
- 8. •What data isn't needed? •What is the context? IBM Mobile Enterprise Stated Another Way! Platform ement enter FOR INTERNAL USE ONLY - DO NOT DISTRIBUTE OUTSIDE OF RICOH 2 8 © 2012 IBM Corporation
- 9. IBM Mobile Enterprise Worklight Studio Development Models 9 © 2012 IBM Corporation
- 10. IBM Presentation Template Full Version Customer Story: ING Direct US B2C: Flexible client-side app architecture to re-use mobile website content © 2009 IBM Corporation
- 11. Unlimited Application Capabilities • Full access to device features • Integration of 3rd-party libraries, both JavaScript and native • Application store ready • A variety of application types: • Downloadable apps • Mobile Web apps • Desktop gadgets and Web widgets 11 © 2012 IBM Corporation
- 12. IBM Mobile Enterprise Polling Question #2 How do you primarily plan on fulfilling your mobile strategy? a. In house development b. Outsourcing custom app development c. Buying mobile app point solutions 12 © 2012 IBM Corporation
- 13. IBM Worklight Overview Components of the IBM Worklight Mobile Platform Worklight Studio Complete, extensible environment with maximum code reuse and per-device optimization Worklight Server Unified notifications, runtime skins, version management, security, integration and delivery 1001010101011 Worklight Runtime Components 1010010100100 1010111010010 0110101010101 0010010010111 1001001100101 Extensive libraries and client APIs that expose and interface 0101001010100 with native device functionality Worklight Console A web-based console for real-time analytics and control of your mobile apps and infrastructure © 2012 IBM Corporation
- 14. IBM Worklight Overview Worklight Studio © 2012 IBM Corporation
- 15. IBM Worklight Overview Single Shared Codebase © 2012 IBM Corporation
- 16. IBM Mobile Enterprise 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 page 16 © 2012 IBM Corporation 16
- 17. Enhanced shell development Customizable Native Shell Code With IBM Worklight studio 5.0, organizations can now Mobile Browser develop custom shells that include corporate services, such as authentication and security services, integration services, and branding. Inner Application Web Code Web developers can then use sanctioned shells to develop the business logic of the application using only HTML5. Customizable Web Shell Code Device APIs Ease of Development Control and Governance © 2012 IBM Corporation
- 18. IBM Worklight Overview Direct Update – On Device Logic © 2012 IBM Corporation
- 19. IBM Mobile Enterprise Polling Question #3 What channels will you need to take utilize for your mobile strategy (both internal and external)? a. iOS only b. Android only c. Win 7 or Blackberry d. Mobile Web only e. Some or all of the above 19 © 2012 IBM Corporation
- 20. Worklight Server IBM Worklight Overview Worklight Server • Distribution of mobile web apps • Enterprise connectivity: • Secure client/server connectivity • Direct access to enterprise back-end data and transaction capabilities • Authentication enforcement • Client control: • Application version management and remote disabling • Direct update of application code • Unified Push Notifications • Aggregation of usage statistics 25 25 © 2012 IBM Corporation © 2012 IBM Corporation
- 21. IBM Worklight Overview Backend Integration © 2012 IBM Corporation
- 22. Worklight Console IBM Worklight Overview Worklight Console • Application Version Management • Push management • Usage reports and analytics • Reports of custom application events • Configurable audit log • Administrative dashboards for: • Deployed applications • Installed adapters • Push notifications • Data export to BI enterprise systems 31 © 2012 IBM Corporation © 2012 IBM Corporation
- 23. Extended out-of-the-box reports IBM Worklight V5.0 contains a new set of reports, tracking adoption and use of mobile apps and devices. These reports replace the previously available reports and are accessible over Eclipse using the BIRT plug-in. Daily visits per app Daily hits per app Total visits per app New detected devices per app Total unique devices – per server (cluster) These BIRT reports are customizable and extensible. The data-warehouse supporting these new reports is also documented, such that any standard reporting or Business Intelligence tool can be used to create additional, custom reports per the needs of the organization. © 2012 IBM Corporation
- 24. Application Management Console Device specific versions are uncoupled Supports multiple versions on the same platform © 2012 IBM Corporation
- 25. Securing Mobile Apps Protecting data on the Enforcing security device updates Secure Jailbreak Encrypted App Offline challenge- and Remote Direct offline authenticity authentication response on malware disable update cache testing startup detection Authenticati SSL with Shell as Data Using Proven server on Code organization protection device id as platform identity integration obfuscation al sandbox framework realms 2nd factor security verification Streamlining Providing robust Application Corporate security authentication and Security processes authorization © 2012 IBM Corporation
- 26. Application center The IBM Worklight Application Center was created to streamline testing processes of apps by enabling dev teams to share apps with testers, designers, sample users, product managers, and any other stakeholders. Testers can download the apps to their devices using a special mobile client application and provide feedback on directly from their devices. Developers can then gather this feedback and consider it in future dev cycles. © 2012 IBM Corporation
- 27. Application center – On-device feedback © 2012 IBM Corporation
- 28. IBM Mobile Enterprise Worklight Differentiators Richest functionality in the market • Fully address high-end enterprise requirements: security, scalability, integration, cross-platform, unlimited mobile app capabilities Extremely easy to implement and learn • No Worklight involvement needed vs. heavy professional services required by competitors • Few days to full productivity vs. months with competing products Open, standards-based platform • Customers can use 3rd-party components and libraries vs. closed platform • Avoid vendor lock-in HTML5 as core development technology • Leverage existing web development skills in IT 28 © 2012 IBM Corporation
- 29. IBM Mobile Enterprise Qualifying Criteria Worklight’s vision is to provide the best platform in the market for enterprises to develop, run and manage smartphone and tablet apps • Self-Sufficiency: Open platform, built around HTML5 & supporting hybrid apps • Not Legacy (ie WinCE): Focus on new devices and OS’s and their unique capabilities • Multiple Apps: Cater to high-end enterprise needs regarding app capabilities, delivery, integration, security, scale and management • Strategic Platform: Handle the entire lifecycle of mobile apps We do not: • Provide packaged applications • Build applications for our customers (Partners, GBS…) 29 © 2012 IBM Corporation
- 30. IBM Mobile Enterprise Open QA • Product Library: • http://www-01.ibm.com/software/mobile-solutions/worklight/library/ • Getting Started Guide Modules and Samples, Product Documentation • Worklight Overview: • http://www-01.ibm.com/software/mobile-solutions/worklight/ • Worklight v5 Overview White Paper; ftp://public.dhe.ibm.com/software/pdf/mobile- solutions/worklight/WSW14181USEN.pdf • Worklight on developerWorks: • https://www.ibm.com/developerworks/mobile/worklight • Forums: http://www.ibm.com/developerworks/forums/category.jspa?categoryID=512 • Blogs: https://www.ibm.com/developerworks/mydeveloperworks/blogs/worklight/?lang=en • Passport Advantage: • http://www-01.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm • Worklight Education • IEA modules: http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.worklight/ plugin_coverpage.html • Worklight Support: • http://www.ibm.com/support/entry/portal/overview/software/other_software/IBM_Mobile_Foundati on 30 © 2012 IBM Corporation
Notas do Editor
- Now how do we do this.There are 4 components to the Worklight platform which you will see in a few minutes – Worklight Studio, an eclipse-based IDE plugin where apps are built and optimized if relevant for different devices. This is also where backend adapters are build to acces enterprise systemsThe Worklight Server – truly the heart of the technology , fully compatible with WebSphere Application Server 7 and higher – the Server is the gateway between the apps and the enterprise providing advanced capabilities such as unified push notifications, runtime skins and more The Worklight Runtime Components – a set of libraries and client APIs that enable access to native device features using web coding, and here we incorporate PhoneGap. This also enables encrypted on-device storage and moreAnd finally the Console – where administrators can track users downloads and activities as well as manage the mobile infrastructure and app versions. Now with that let me hand it over to Dustin to talk about this at greater depth.
- The shell-based development approach to hybrid apps helps organizations to better rely on the web skills they already have, thus reducing the barriers of mobile development, making it ubiquitous across the organization, by compartmentalizing skill-sets and responsibilities. Furthermore, it also helps organizations to speed up and simplify corporate governance processes.Most often, enterprises employ multiple development teams with different skills and expertise. The Shell approach allows such companies to reduce the internal barriers of mobile development, making it ubiquities across the organization by compartmentalizing skill-sets and responsibilities. Worklight’s Shell approach breaks down the development of the app into two portions: an external shell and an inner application.The shell consists of a customizable container that provides JavaScript access to the native capabilities of the device. A devoted team of expert developers are responsible for its branding, security configurations, audits and authentication frameworks.The team can create a variety of shells, each carrying different policies and branding, forcing inner apps running within each shell to automatically comply with its parameters. Such parameters could include restriction of access to data, use of certain APIs, different branding and more.With corporate policies enforced by the shell, the inner apps can be easily built by departmental development teams using nothing but web languages. Such teams are only required to focus on the user interface, the business logic and, potentially, data integration. Distribution of the application or applications can be achieved by three different channels:An inner app can be fused into a shell by the centralized build server and uploaded to a private or public application store, while new app versions are sent and updated directly on the end-user device.A shell can be packaged with a directory of corporate-sanctioned applications, allowing the user to choose a different inner app according to his or her needs.A shell can be distributed empty to the user who will then access a repository of applications stored on the Server.