Worklight Overview

2011 Worklight, Inc. All rights reserved. The information contained herein is the proprietary and confidential information of Worklight.
Pre Bluewash 2012

IBM WSBP
zhjzhjsh@[Link]

Worklight Introduction
2
Worklight is an open, complete and advanced mobile application
platform for HTML5, hybrid and native apps.
Worklight Vision
Open platform, built around HTML5 & supporting hybrid apps
Focus on new devices and OSs and their unique capabilities
Cater to high-end enterprise needs regarding app capabilities,
delivery, integration, security, scale and management
Handle the entire lifecycle of mobile apps

We do not:
Provide packaged applications
Build applications for our customers
3
Provides the best platform in the market for enterprises to
develop, run and manage smartphone and tablet apps - MEAP
Innovation and Leadership
4
Highlighted in recent MCAP, MEAP Reports
Profiled in MEAP forecast and Mobile Security Report
Awarded strong competency in Smartphone & Tablet apps
Selected as One of eWeeks Product to Watch
Worklight in Top Product Suite for the Enterprise
Names Worklight in Top Ten Startups List
Top 50 Business Technology Companies to Watch
Customer Spotlight ING Direct
5
Customer Spotlight Lotte Card
6
Customer Spotlight Best Western
7
Customer Spotlight Unisys
8
Market Trends
9
Source: IBM, The Essential CIO, 2011
Controlling the growing portfolio of applications
deployed in the wild
Connecting the enterprise back-end services in
a secure and scalable manner
Creating rich, yet cost-effective mobile apps in a
fragmented technological landscape
Mobile Apps Top Challenges
10
WebSphere Mobile Strategy in a Nutshell
The mobile platform is part of a broader multi-channel strategy that will

Extend our SOA platform to mobile based devices using open standards and technologies
targeting the broadest set of devices possible leveraging the skills and infrastructure of our
existing WebSphere customers

- Greg Truty
11
11
Collaborative
Lifecycle
Management
(Rational)
A complete enterprise framework for mobile computing
Application Server
(WebSphere)
Enterprise Apps
SOA & Connectivity
(WebSphere Message Broker, WebSphere MQ (MQTT), WebSphere Cast Iron, WebSphere Services Registry and Repository)
Security Gateway
(WebSphere DataPower, IBM Security Access Manager)
Endpoint
Management
(IBM Endpoint Manager)
WebSphere
Operational Decision
Management
IBM Business Process
Management
Mobile App Platform
(IBM Worklight)
Elastic Caching
(WebSphere eXtreme Scale /
WebSphere DataPower XC10)
12
Worklight Server
Unified notifications, runtime skinning, version management,
security, integration and delivery
Worklight Console
A web-based console for real-time analytics and control of
your mobile apps and infrastructure
Worklight Studio
The most complete, extensible environment with maximum
code reuse and per-device optimization
Worklight Overview
13
Worklight Runtime Components
Extensive libraries and client APIs that expose and interface
with native device functionality

14
Worklight Architecture
Worklight Differentiation
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 3
rd
-party components and libraries vs. closed platform
Avoid vendor lock-in
HTML5 as core development technology
Leverage existing web development skills in IT
15
Downloadable (Native) Apps
16
Application
Stores
File System
(on mobile device)
Native App
(Java/Objective-C/C#)
Mobile Operating System
High-quality user
experience and full
device access.

Platform-specific,
requires unique
expertise, expensive to
develop and maintain.
Web Server
Web Apps
17
Mobile Browser
Native App
(Java/Objective-C/C#)
Mobile Operating System
Written in HTML5
JavaScript and CSS3.
Quick and cheap to
develop.

Less powerful than
native and limited device
access.
Hybrid Apps
18
Application
Stores
File System
(on mobile device)
Native Container
HTML, CSS, JavaScript
Mobile Operating System
Combines best of both
worlds:

Primarily written in
HTML5, CSS, JS while
allowing full access to
device capabilities.
Worklight Shell Approach
19
Trusted App
Repository
File System
(on mobile device)
Native Container (Shell)
with custom functionality for
performance and security
HTML, CSS, JavaScript
Mobile Operating System
Allows development of
downloadable apps
without any knowledge
of native development
languages.

Dedicated teams with
native expertise can
provide custom native
capabilities and security
functions to app
developers.
20
Worklight Studio
Eclipse-based IDE
Combining native and standard web
technologies in one multiplatform app
Environment-specific optimization
3rd-party libraries integration
Device SDK integration
Back-end connectivity utilities

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 utilities






Worklight Studio
21
Single Shared Codebase
22

Common code placed
in primary file

Environment optimization
code is maintained separately



Incorporated Device SDKs
23
Integrating Best-in-class Tools
Worklight is compatible with prominent HTML5 libraries and tools:
24
Runtime Skinning Use Cases
Different
Screen Sizes
Different
Input Method
Different
Screen Densities
Support
for HTML5
25

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
Hybrid Coding Native and Web
26
Write the majority of the code in
reusable web languages
Maximize user experience and achieve
unique functionality with native code
Hybrid Coding Why Mix Native and Web?
27
The Shell-based Application
28
Shell Team
Security configurations
and audits
Authentication
Mobile expertise
Inner App Team
Business logic
Develop the UI
Data integration
Reducing the barriers of mobile development, making it ubiquitous across
the organization, by compartmentalizing skill-sets and responsibilities
Distributed App
Shell fed by repository
Shell fused with app
Shell packaged with
directory
App Stores
Server
App Stores
Architecture of the Shell-based Application
Architecture
The Shell consists of native and web code
Inner app consists of web code only
Native access
The Shell provides JavaScript access to native device
capabilities
Sandbox
The Shell can restrict inner apps from accessing
unsanctioned native and JavaScript functions
Customization
The Shell can include custom native and web libraries
and APIs, branding resources, authentication, and
integration components
API restrictions are also customizable
Diversity
Company may distribute multiple shells for different
trust levels, authentication types, corporate
departments, etc.
29
Customizable Native Shell Code
Device APIs
Mobile Browser
Customizable
Web Shell Code
Inner
Application
Web Code
30
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
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


Back-end Integration
31
Direct Update On-device Logic
Worklight
Server
Native Shell
Pre-packaged
resources
1 Download
4
Update web
resource
App Store
Web
resources
Cached
resources
1. Web resources packaged
with app to ensure initial
offline availability
2. Web resources transferred to
app's cache storage
3. App checks for updates
On startup
On foreground
4. Updated web resources
downloaded when necessary
2 Transfer
3
Check for
updates
32
Unified Push Notifications
Back-end
System
Back-end
System
Back-end
System
Back-end
System
Polling
Adapters
Message-
based
Adapters
Unified
Push API
Notification
State
Database
User-
Device
Database
iOS
Dispatcher
Android
Dispatcher
BlackBerry
Dispatcher
Windows
Phone
Dispatcher
SMS
Dispatcher
Apple Push
Servers
(APN)
Google
Push
Servers
(C2DM)
RIM Push
Servers
Microsoft
Push
Servers
SMS/MMS
Brokers
Administrative Console
Worklight
Client-side
Push Services
Worklight
Client-side
Push Services
Worklight
Client-side
Push Services
Worklight
Client-side
Push Services
iOS
Push API
Android
Push API
BlackBerry
Push API
Windows
Push API
Broker API
34
Centralized Build
35
Worklight
Build System
Source Code
Repository
Integ with RTC
36
Device Runtime Components
Framework for server integration:
Secure server connectivity
Authentication
Remote disable & notification
Push registration
Dynamic page loading & caching (soon)
Event reporting for analytics & audit
Cross-platform compatibility layer
Runtime Skinning
Secure encrypted storage
37
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
Dynamic Control of Deployed Apps
Centralized control of all installed applications and adapters
Remotely disable apps by device and version
Customize user messages
38
Push Services Management
39
Data Collection and Analytics
40
41
Enforcing security
updates
Remote
disable
Direct update
Providing robust
authentication and
authorization
Authentication
integration
framework
Data
protection
realms
Coupling
device id with
user id
Streamlining
Corporate security
processes
Mobile
platform as a
trust factor
Application
Security
Code
obfuscation
SSL with
server
identity
verification
Proven
platform
security
Security Features
Jailbreak and
malware
detection
App
authenticity
testing
Protecting data on the
device
Encrypted
offline cache
Offline
authentication
Secure challenge-
response on
startup
For More Information
42
Resource Location
30-day Software Trial [Link]/download
Online Training [Link]/download/get-started
Documentation [Link]/download/documentation
Product Resources [Link]/resources/product-resources
Webinars [Link]/resources/webinars-and-tools
Additional Info info@[Link]
Appendix
Competitive Reference
45
Very costly
development
and ongoing
maintenance
Long time to
market
Requires specific
knowledge and
skills that are not
transferable across
environments
Application
delivery limited to
application stores
No cross-platform
compatibility
Lacking complete
IDE functionality
No optimization
capabilities
Lacking
management and
middleware
capabilities
Does not address
enterprise security
requirements
No advanced
features, e.g.
Runtime Skinning,
Unified Push,
Remote Disable

Application
typically presents
lowest common
denominator
Does not address
unique business
and IT
requirements
Rarely provides
sufficient
middleware and
management
capabilities
Typically very
expensive for high
user volume
Typically legacy
solutions limiting
modern device
support
Often proprietary
interpreters and
scripting languages
Less agile
development
Weak or no
support for HTML5
Lacking 3
rd
-party
compatibility
Often focused on
packaged apps and
services
Native
Development
Open Source
Frameworks
Pre-packaged
Mobile Apps
Other Mobile App
Platforms
Environment Requirements
46
Function Development Environment Production Environment
Operating
Systems
Windows 7, Vista or XP (32
or 64 bit)
Mac OS X 10.6.X (64 bit)
Widows Server 2008, 64 bit
Red Hat Enterprise Linux (REHL)
version 4 SP3 or later (SP4
recommended), 64 bit
Database MySQL 5.0.22 or later (5.0.67
recommended)
MySQL 5.0.22 or later (5.0.67
recommended)
Oracle 10g ([Link].0)
Development
Environment
Eclipse for JEE Developers,
version Helios
NA
The Server can be clustered for high availability and linear scalability. In such cases, a
load-balancer is required. Any commercial load-balancer, hardware or software, that
supports sticky sessions can be used. The load-balancer can optionally act as a reverse
proxy and SSL accelerator, depending on the technical needs of the environment.