SOA design patterns and mobile at SOA Architect summit. Application architectures and mobile trends in the industry.

1. SOA Design Patterns and Mobile
2013 IBM SOA Architect Summit
Sreeni Pamidala
Lead Architect, SWG Lab Services for Mobile
spamidala@us.ibm.com

2. IBM’s statements regarding its plans, directions, and intent are subject to change or
withdrawal without notice at IBM’s sole discretion. Information regarding potential
future products is intended to outline our general product direction and it should not be
relied on in making a purchasing decision. The information mentioned regarding
potential future products is not a commitment, promise, or legal obligation to deliver
any material, code or functionality. Information about potential future products may not
be incorporated into any contract. The development, release, and timing of any future
features or functionality described for our products remains at our sole discretion.

3. 3
Agenda
Mobile Application Trends
Mobile Application Architecture
Integration with Other SOA Components
Pattern Based Engineering and Common Mobile
Application Patterns
IBM Worklight Features that Enable Each of the
Above Architectures

4. Host/Mainframe
Client/Server
Web/Desktop
Mobile/Wireless/Cloud
Mobile is different:
•Transformational business models
•Faster lifecycles
•More iterative
•Requires open standards
Mobile is a significant evolution of enterprise computing

5. Mobile Application Trends
5
Simplicity
•Higher expectations of user experience
•built-for-purpose, do-one-thing-really-really-well apps
Speed (time to market)
•New app/function available as soon as the business identifies the need.
•More frequent releases and updates with more urgent time-to-market demands
•Little training needed for current web developers.
Integration
•Integrate with existing enterprise capabilities and external service providers
•No green field development
Multi-Platform
•Able to adapt to changes in prevalent technologies, switch as needed.
•Not tied to a proprietary, single-vendor strategy.
Security
•Safe and secure apps

6. The Mobile Lifecycle
• Strong demand by LoB
• Higher expectations of user experience with mobile apps
• Lack of best practices guidance on how to deliver mobile applications
• More direct involvement from users/stakeholders in design
• Native programming models are not portable across devices.
• Highly fragmented set of mobile devices and platforms
• Very large number of configurations of devices, platforms, carriers, etc. to
test
• Mobile landscape evolves at a much faster pace
• More frequent releases and updates for apps with more urgent time-to-
market demands

7. But also brings business and IT challenges
Top Mobile Adoption Concerns:
1. Security/privacy (53%)
2. Cost of developing for multiple
mobile platforms (52%)
3. Integrating cloud services to mobile
devices (51%)
Source: 2011 IBM Tech Trends Report
https://www.ibm.com/developerworks/mydeveloperworks/blogs/techtrends/entry/home?lang=en
Enterprise Business Model Changes
• New business opportunities based upon geo location
• Anytime, anywhere business transactions
• Importance of social business interactions
App Development Lifecycle Complexity
• Complexity of multiple device platforms with
fragmented Web, native, and hybrid model landscape
• Connecting the enterprise back-end services in a
secure and scalable manner
• Unique mobile requirements (user interface,
connected/disconnected use, version upgrades, etc.)
Mobile Security and Management
• Protection of privacy and confidential information
• Use of client-owned smartphones and tablets
• Visibility, Security & Management of mobile platform
requirements

8. 8
Go to 'View > Header and Footer' to
change this footer text to the event title
Agenda
Mobile Application Trends
Mobile Application Architecture
Integration with Other SOA Components
Pattern Based Engineering and Common Mobile
Application Patterns
IBM Worklight Features that Enable Each of the
Above Architectures

9. Mobile and Web Application Development Types
Mobile Browser ExecutionMobile Browser Execution
TraditionalTrade-offs
(withoutMEAP/MAP)
Characteristics
Maintenance Cost (TCO)
Portability (cross-device reuse)
Richness of Mobile Presentation / Services
Web
Application
Desktop and mobile
using open web
(HTML, JavaScript)
client
programming models
Limited to no device-
specific functionality
AppStore download and installAppStore download and install
Native Mobile
Application
Mobile only,
developed using
native languages or
transcode to native
via MAP tools
Native appearance
and
device capabilities,
performance
Mobile Web
Application
Mobile only using
open web (HTML5,
JavaScript) client
programming models
Off-line capabilities
Hybrid/Hybrid Mix
Mobile Application
Mobile only, app runs on
the device, but leverages
open web (HTML5, JS)
via JavaScript bridge
Native device capabilities
(GPS, camera, contacts)
Mimic native appearance
Hybrid mix can have web
code with native for
things like navigation for
maximizing user
experience

10. Client Application Architecture
• Frameworks only take you so far.
• Build out architecture.
• Enterprise jQuery solutions different projects.
• How do they work together?
Support for each?
• MVC
• JavaScriptMVC
• Backbone
• SproutCore
• Knockout,etc…
• Templates
• jQuery-tmpl
• Mustache
• Dust
• Etc…
• Module Communications
• jQuery.pubsub
• PubSubJS
• Components
• OpenSocial

11. Classic Web vs Web 2.0 Architecture

12. IBM MobileFirst Platform
IBM Worklight
IBM Rational Test Workbench
IBM Mobile Application Platform Management
• Automated testing for high quality mobile
apps (planned beta in 1Q)
• Streamlined deployment for private
clouds on PureApplication System
• Single sign-on across multiple apps on a
device
• Latest versions of all major mobile OS’s
(iOS, Android, Windows, and BlackBerry)
For clients that need to:
Quickly develop and deploy high quality
mobile apps across multiple platforms
Seamlessly connect rich mobile
applications to enterprise data and
services
IBM MobileFirst Platform offers:
Native, web, or hybrid app development
Tools to build & test high quality apps for many
devices
Management, security, continuous delivery &
distribution of apps
Easy connectivity to existing data & services
for mobile usage
On-premises or managed service delivery
Available Today!

13. Worklight Console
Hybrid Application Version
Management
Push Notifications
Reporting & Analytics
Worklight architecture
Worklight
Application Center
Native Application Version
Management
Application Feedback
Application Client App
Worklight Server
Authentication
JSON
Translation
Server-side
App Code
Adapter Library
Client-side
App Resources
Direct Update
Mobile
Web Apps
Unified Push
Notifications
StatsAggregation
EnterpriseBackEnd
andCloudServices
Device Runtime
Cross Platform
Compatibility Layer
Server Integration
Layer
Encrypted Storage
Runtime Skinning
Reporting for
Statistics/Diagnosis
ApplicationCode
←
Worklight Studio
HTML5, Hybrid, and
Native Coding
Optimization
Framework
Integrated Device SDKs
3rd-Party Library
Integration
BuildEngine
iOS
SDK
Android
SDK
Blackberry
SDK
Windows
SDK
PublicandPrivateAppStores
13

14. Cross-platform code base
Common elements stored in the
common folder
– HTML, Javascript, CSS
– Worklight API usage
– 3rd party tools usage
Named Environment directories
(android, blackberry, iphone, etc…)
– Generated as Environments are added to
the project
– Platform-specific code
Environment-specific user
optimizations
– Over-ride default behaviors & styles
– Behavior and branding changes
14

15. 15
Go to 'View > Header and Footer' to
change this footer text to the event title
Agenda
Mobile Application Trends
Mobile Application Architecture
Integration with Other SOA Components
Pattern Based Engineering and Common Mobile
Application Patterns
IBM Worklight Features that Enable Each of the
Above Architectures

16. Typical Web Application Deployment Architecture
A – Web App
D – Client Device
N – Network
I/i – Internet/intranet
WAS – WebSphere Application
Server
EBE – Existing Back End
I – Internet Service

17. Mobile Application Deployment Architecture
A – Mobile App
D – Mobile Device
N – Network
I/i – Internet/intranet
WL – WorkLight Server
EBE – Existing Back End
I – Internet Service

18. SOA Reference Architecture Services

19. Simple topology of a hybrid mobile application with Worklight
Pattern: Application Server, Adapter Pattern
Roles and tools: Mobile Client UI developer
vs. server side developer, vs. adapter
developer

20. Mobile Integration into the Enterprise SOA
Enterprise
Back-end
Worklight
Security Authentication Scalability

21. 21
Go to 'View > Header and Footer' to
change this footer text to the event title
Agenda
Mobile Application Trends
Mobile Application Architecture
Integration with Other SOA Components
Pattern Based Engineering and Common Mobile
Application Patterns
IBM Worklight Features that Enable Each of the
Above Architectures

22. DataPower Gateway
Pattern: Reverse proxies typically front Worklight runtimes and follow the gateway pattern
Purpose: Protecting WL from the Internet, XML firewall, terminate SSL, AAA services, PEP
Product Mapping: DataPower®, or IBM Security Access Manager
Roles and Tools: Administrators configure QoS

23. Gteway AAA Services

24. Adapter Pattern
An Adapter is a transport layer used by the
Worklight Platform to connect to various back-
end systems.
• Executed on Worklight server
• Implemented in Javascript by default (can be custom-
coded in Java)
• Simple client-side Javascript invocation model
through Worklight client API
Adapters are used for:
• Retrieving information
• Performing actions
Out of the box Adapter support:
• SQL Adapter
• HTTP Adapter (supports both
REST and SOAP)
• CastIron Adapter (optimized for HTTP data exchange
with CastIron integration appliance)
• JMS Adapter
Query
Update
data
Data/Result
as JSON
Invoke
adapter
procedure
SQL HTTP-WS HTTP-REST
Response
1
2 3
4
Caching Mechanism
CAST IRON JMS

25. Cloud Integration via Cast Iron
Pattern – Enterprise Service Bus, elastic cloud
Purpose: “elastic client” apps integrate with location transparency - on premise or in
“elastic” public or private clouds
Product mapping: The Cast Iron adapter provides OOTB integration with all cloud-
based, hardware appliance or hypervisor editions of IBM WebSphere Cast Iron.
Roles and tools: Integration developers build integration flows in WebSphere Cast Iron
Studio, with orchestrations mad up of a number of configurable activities
Worklight Cast Iron Adapter

26. Integration via Message Broker
Pattern – Enterprise Service Bus, Pattern Based Engineering
Purpose: integrate applications using a variety of common patterns
Product mapping: WebSphere Message Broker provides OOTB pattern integration
toolkit for rapid application development.
Roles and tools: Integration developers instantiates integration patterns in WMB Studio.
It generates adapters, and integration flows made up of a number of configurable nodes

27. Mobile Service Enablement Pattern
27
Creates a mobile-ready interface around a Message Broker service
– Services are a first class artifact in Message Broker alongside applications and libraries
– Builds an adapter to integrate Worklight and Message Broker services
– Inbound data from the mobile application is sent to Worklight as JSON/HTTP
–Makes it very simple to mobile enable a Message Broker service!
– The adapter passes the inbound request straight through to the service
– Pattern adds an HTTP/JSON message flow (binding) to the service project

28. Resource Oriented Architecture
Create
– POST /MyRESTService/ -- create a new item
Read
– GET /MyRESTService/ -- list all items
– GET /MyRESTService/count -- get number of items
– GET /MyRESTService/# -- get item by #
Update
– PUT /MyRESTService/# -- update an item by #
Delete
– DELETE /MyRESTService/ -- delete all items
– DELETE /MyRESTService/# -- delete item by #

29. Resource Handler Pattern
29
Resource oriented architecture is a well known implementation pattern
– Provides a common set of functions (CRUD – Create Read Update and Delete)
– This pattern provides an adapter which implements CRUD operations
– A Message Broker service is generated with subflows for each operation
– The service integrates security authorization and authentication (LDAP)
– Operations optionally integrate with the Message Broker Global Cache (WXS)

30. IBM MobileFirst Management
*Planned availability in 1Q 2013
For Clients That Need To:
Implement BYOD with confidence
Manage secure sensitive data, regardless
of the device
Handle multi-platform complexities
with ease
IBM MobileFirst Management Offers:
Unified management across devices
Option to wipe corporate data
Configuration & enforcement of password
policies, encryption, VPN access & camera use
Streamlined workflow between
development & operations with an
integrated Enterprise App Store
On-premises or managed service delivery
IBM Endpoint Manager for Mobile Devices
IBM Enterprise Services Managed Mobility
IBM Mobile and Wireless Network Management
Available Today!
• Latest versions of all major mobile OS’s
(iOS, Android, Windows, and BlackBerry)
• Defense-grade encryption
thru FIPS 140-2 compliance*
• Automatically grant or deny email access
based on device compliance
• Ease admin by setting and reporting
IBM Notes Traveler security policies

31. Device Management w/ IBM Endpoint Manager
For devices that must be managed as enterprise assets or must be controlled
across applications, IEM provides:
Safeguard of enterprise data
Flexible management
Maintained compliance
Unified infrastructure

32. A comprehensive suite of mobile solutions for
social business - with device-appropriate
interfaces for Smartphones and tablets including:
Apple®, Android, Research In Motion®
BlackBerry®, Nokia
In 2011: 44 collaboration software releases
• IBM Lotus Notes Traveler -- push email,
calendar, contacts
• Real-time collaboration – IBM Sametime IM
chat and online meetings or via IBM SmartCloud
for Social Business
• IBM Connections social software for access to
your professional network
• IBM Lotus Symphony Viewers for viewing
business documents
• App dev software for HTML-based mobile
apps and sites – IBM Lotus Domino XPages
and IBM WebSphere Portal Mobile Experience
Extending desktop social collaboration to mobile devices

33. Extending Pub/Sub with Push Notification Services
33
Worklight supports asynchronous push notifications to mobile applications
– Push notifications have a measurable impact on the success of mobile applications
– There are many IT challenges in supporting push notifications (devices, delivery etc)
–Push notifications are applicable across many industry verticals
– Healthcare, retail, travel, transportation, government, insurance and more!
–All the major mobile platforms support push notification services
– Apple iOS 3, Google Android 2.2, RIM Blackberry 5 and Windows Phone 7
–Pending notifications are written to a WebSphere MQ queue by a
provider application
– Need to subscribe to the notifications and arrange delivery to the mobile notification
server

34. Worklight Push Notification from WebSphere MQ
34
Creates a push notification adapter from a WebSphere MQ queue
– Generates a web service implementation which is deployed to Message Broker
– Builds a Worklight integration adapter which polls for pending notifications
– Pending notifications are written to a WebSphere MQ queue by a provider application
– The adapter converts the notifications into JSON and arranges delivery to the mobile

35. Integration w/ Portal Server
WebSphere Portal supports
– HTML5, CSS and JavaScript
– Integration w/ applications, content, authentication, roles, personalization
– Multi-channel experience support
A natural choice to integrate with the capabilities that Worklight provides

36. Native Container
Device Cap
Web Content
Native Container
Web Content
Device Capabilities
Mobile experiences that are built using both native code and web technologies
WebSphere Portal
UI, application(s),
content,
Portal services
(roles, personalization,
customization,
navigation),
back-end access
IBM Worklight
Access to devices
capabilities
(camera, contacts,etc...)
App Store Presence
Application management
(validity, updates, etc.)
Mobile Notifications
Portal/Worklight Mobile App
Enterprise applications and services
(including IBM Connections and social services)

37. Extending BPM to Mobile via Web APIs
IBM BPM v8 key use case: mobile task management
– Users can launch, view, and complete business process tasks
Extensive REST APIs & examples enable customized integration of IBM BPM content
into your own mobile experiences
– Expanded REST/JSON API for mobile application development
– Both Process Portal and Mobile App use this API

38. 38
Go to 'View > Header and Footer' to
change this footer text to the event title
Agenda
Mobile Application Trends
Mobile Application Architecture
Integration with Other SOA Components
Pattern Based Engineering and Common Mobile
Application Patterns
IBM Worklight Features that Enable Each of the
Above Architectures

39. 39
Tivoli
Security
Rational
Lifecycle
The IBM Mobile Platform and SOA
SOA design principles in mobile application architecture leverage the combined power of the IBM
Mobile Platform and SOA Foundation
(i.e., what you need to build and effectively incorporate mobile apps with your SOA)
IBM Mobile Platform
Enterprise Apps
SOA & Connectivity
Worklight Mobile
Platform
Elastic Caching
Security Gateway
Mobile Device
Management
Analytics
Decision
Management
Portal
Analytics
Business
Process
Management
Connectivity
MQTT, Broker,
CastIron

40. Mobile is an enterprise priority that helps transform your business and is
driving key client initiatives
IBM has extensive capabilities in this space with additional new and
enhanced offerings including:
• Worklight: an open, complete, and advanced mobile application platform for HTML, hybrid, and
native applications
• IBM Endpoint Manager for Mobile Devices: unified endpoint management, with integrated
mobile security
• Tie in to your SOA : security gateway, ESB integration, elastic cloud, REST and WEB API
pattern
40
IBM delivers a comprehensive end-to-end mobile solution

41. 1. Discover IBM’s mobile capabilities, the use cases our capabilities solve, and jointly explore
how a deeper dive could drive value for you:
• On Ramp to Mobile Workshop (1 day)
2. If you are just starting your mobile adoption:
• Mobile Discovery Workshop (1-3 days)
• Review specific business pains and trends to create mobile strategy & plan for next steps
• Mobile Quick Win Pilot (3-10 weeks)
• Build a first instance of a mobile application to experience business value and create
organizational buy-in
3. When you are ready to scale within a LoB or across the enterprise:
• IBM Mobile Strategy Accelerator (Multi-week engagement)
• Understand how to most effectively integrate mobile capabilities.
• Results in a roadmap that optimizes mobile transformation opportunities and accelerates time to
market.
• Mobile Infrastructure Strategy & Planning (Multi-week engagement)
• Assess current environment, define infrastructure strategy and build technology and services
roadmap
• Managed Mobile: Endpoint and Application Platform Management (ongoing)
• Provide managed services to secure your mobile endpoints and for your mobile application
platform environment
Services to support your Mobile Adoption

42. Thank You
Merci
Grazie
Gracias
Obrigado
Danke
Japanese
French
Russian
German
Italian
Spanish
Portuguese
Arabic
Traditional Chinese
Simplified Chinese
Hindi
Romanian
Korean
Multumesc
Turkish
Teşekkür ederim
English
Благодаря
Bulgarian