Mobile Web Services - Colorado Software Summit

Transcription

Colorado Software Summit: October 24 – 29, 2004
© Copyright 2004, IBM Corporation
Mobile Web Services:
Challenges, Issues and Case Study
Peter Haggar
Senior Software Engineer
Emerging Technology
IBM Corporation
Research Triangle Park, NC
[email protected]
Peter Haggar — Mobile Web Services: Challenges, Issues and a Case Study
Page 1
About Me
Practicing Software Engineer for 17+ years
Work with Web Services on mobile devices
Recently deployed Proof of Concept mobile
project for an IBM customer
Also focus on high performance Web
Services
IBM Representative to W3C XML Binary
Characterization Working Group
Please email me with any questions about
this presentation
Page 2
Agenda
Challenges and Issues
¾Functionality
¾Development Tools/Environment
¾Devices
¾Wireless Security
¾Security and Devices
¾Wireless Networks
¾Integration
Hospital Case Study
References
Page 3
Functionality
What functionality do you present on a
mobile device?
¾Depends on requirements AND on device
capabilities
Quickest road to failure is to not be honest
about inherent device limitations
Web Services and mobile devices does not
have to mean invoking web services from
the device
Page 4
Functionality
Extending an existing solution to mobile
¾What function(s) do you provide?
• Subset of existing function
• All existing function
¾Device functionality must be easy to use
¾Map to existing solution
• “Keep the same deficiencies”
Be careful if you provide function on device
that is easier to do on laptop/desktop
Page 5
Functionality
Device functionality is best left to “read-only”
¾Data entry is tedious for most users
• You and I are not most users
Understand your user base
¾Can get frustrated very easily
¾Your device can become a paperweight very
quickly
Page 6
Development Tools/Environment
Java?
¾J2SE
¾J2ME
• Profiles?
C, C++, C#, VB?
Development tools
¾Free or $$
Following are some I’ve used:
Page 7
RIM Blackberry
¾Java
¾Supports J2ME plus RIM extensions
¾Free JDE
• http://www.blackberry.net/developers/na/java/start/index.shtml
Sharp SL-6000
¾Java
¾Supports J2SE
• Download .class files you build on desktop to run on
device
Page 8
Palm
¾C
• Metrowerks CodeWarrior
http://www.metrowerks.com/MW/Develop/Desktop/PalmOS/Professional/Default.htm
¾Java
• IBM WebSphere Studio Device Developer
http://www-306.ibm.com/software/wireless/wsdd/
Page 9
PocketPC
¾Java
• IBM WebSphere Studio Device Developer
9 http://www-306.ibm.com/software/wireless/wsdd/
¾C#, C++, Visual Basic
• Microsoft tools
9 http://www.microsoft.com/windowsmobile/developers/default.mspx
Page 10
Devices

Non-connected
Bluetooth
802.11b
Cellular
For any serious application
¾802.11b
¾Cellular
Page 11
Devices
802.11b
¾Palm Tungsten C (integrated)
¾Sharp SL-6000 (integrated)
¾PocketPC (various) (integrated or card)
Cellular
¾RIM Blackberry (integrated)
¾Sharp SL-6000 (requires cellular card)
¾PocketPC (various) – requires cellular card
¾Palm Tungsten W (integrated)
Page 12
Devices
Don’t just choose a device due to its
characteristics
¾Take into account:
• Development environment
• Development language
• Usability and capability
• Available accessories
• Available expansion hardware and software
• Wireless Security model supported
Page 13
Devices
Dual mode devices are starting to emerge
¾802.11 and Cellular
You can do this today with an 802.11b
integrated device and add a cellular CF card
¾Need WECM for seamless roaming
Page 14
Devices – Pros/Cons
Palm Powered Devices
¾OS is still single-threaded
¾Lots of aftermarket apps and accessories
¾Large user base
PocketPC
¾Multithreaded OS
¾Lots of aftermarket apps and accessories
¾Large user base
¾Familiar look and feel to Windows
Page 15
Devices
Sharp SL-6000
¾Runs embedded Linux – Multithreaded
¾Full VGA screen
¾Currently not a lot of aftermarket apps and
accessories
¾Currently small user base
RIM Blackberry
¾Java only device
¾Niche market with good penetration
¾Screens are weakness (not even ½ VGA)
Page 16
Wireless Security
Depending on the application, different
aspects need to be considered
For 802.11b
¾For an enterprise, WEP doesn’t cut it
¾LEAP is solid enough for most applications
¾There are other wireless security protocols
• 802.11i
9 Recently approved and provides solid security
• Many are not yet provided for handhelds
Page 17
Wireless Security
For Cellular
¾Some devices provide no security by default
• Palm Tungsten W
9 However, can use VPN software
¾RIM Blackberry has good security story
• Everything is Triple DES encrypted from device to BES
server
For 802.11b and Cellular
¾IBM’s WebSphere Everyplace Connection
Manager (WECM)
• http://www-1.ibm.com/industries/wireless/doc/content/solution/278603104.html
Page 18
Wireless Security
WECM
¾Provides excellent security
¾Provides seamless roaming between LAN and
WAN networks
• Roam between 802.11b to Cellular
¾Picks up lost connections… where you left off
Page 19
Security and Devices
Palm Tungsten C
¾WEP – out of the box
¾LEAP – 3rd party add-on
• http://www.mtghouse.com
¾WECM – IBM add-on
Sharp SL-6000
¾LEAP – 3rd party add-on
• http://www.mtghouse.com
Page 20
Security and Devices
PocketPC devices with Windows Mobile 2003
¾LEAP – out of the box
RIM Blackberry
¾Triple DES encryption from device to BES server
– out of the box
Page 21
Security and Devices –
Sharp SL-6000
Does not support alphanumeric power-on
passwords
Opera Browser
¾Good HTML and JavaScript support
¾Very configurable
¾Can control browser cache
¾Supports separate browser password
Page 22
PocketPC
Supports alphanumeric power-on passwords
PocketIE Browser
¾Good HTML and Javascript support
¾Browser has almost no configuration options
• Very weak
• No options to clear cache
• No separate browser password
Page 23
Palm
Supports alphanumeric power-on passwords
Browser issues
¾Not as robust as Opera or as versatile as
PocketIE
Page 24
Wireless Networks
Cellular
¾GSM, CDMA, TDMA, iDEN, etc.
¾Pros: Wide coverage area
¾Cons: Slow and expensive
802.11
¾802.11, 802.11a, 802.11b, 802.11g
¾b very pervasive… g getting there
¾Pros: Fast and cheap
¾Cons: Narrow coverage area
Page 25
Wireless Networks
Broadband cellular networks are emerging
Verizon
¾300 - 500kbps
• Currently – Washington DC and San Diego areas only
Page 26
Integration
Often you want to integrate with existing
enterprise solution
¾Accomplished easiest with standards-based
approach
• Web Services
¾“Yes, but I thought web services were fat
and slow... how can I do that on a
handheld?”
Page 27
Integration
Two approaches
¾Invoke web services from handheld
¾Leave the web services on the server
Web Services from handheld
¾IBM’s Web Services Toolkit for Mobile devices
• Free: http://www.alphaworks.ibm.com/tech/wstkmd
¾Provides ability to invoke web services from
variety of handhelds
Page 28
Integration
Performance is acceptable on 802.11 LANs
¾Can be sluggish on cellular WANs
¾However, this is due to the network, not the
Web Services
Also consider how much code you want on
the device
¾Put Web Services on server and provide a
browser based solution
• No device coding
• More portable
• Limited to browser UI, however
Page 29
Case Study
Hospital with an existing clinical information
system
¾J2EE web application
¾WepSphere on IBM 390 backed up by DB2
Browser based application used by
physicians to
¾view/update patient information
¾Write prescriptions, track problems, etc.
¾99% originally written by IBM
¾In use for 2.5 years
Page 30
Case Study
Allows physicians to query and update
various information:
¾Demographics
¾General Problems
¾Labs
¾Medications
¾Insurance
¾Schedules
• Physician and Clinic
Page 31
Page 32
Page 33
Page 34
Page 35
Page 36
Existing Architecture
Locked Down
Station
Wired
Wireless
Desktop
Laptop
IBM 390
802.11b
via
Cisco
LEAP
WebSphere
Stored Procedure
Manager
DB2
Page 37
History
Hospital wants a mobile solution for
physicians
Have tried:
¾Wireless Toshiba Tablets
¾Were considering Thinkpads on a cart
Perfect opportunity to prove Web Services
utilization and handhelds
Page 38
History
November 2003
¾ First meeting with key hospital decision makers
• Director of Medical Infomatics, CIO, IT Director, and staff
Showed demo of what was possible using various
devices
¾ Collected initial requirements
December 2003
¾ Proposed Architecture to meet requirements
¾ Received the go-ahead to build solution
Page 39
History
January 2004
¾ Proof of Concept (POC) requirements review meeting
February 2004
¾ Begin POC implementation
June 2004
¾ POC Launch (6/11)
¾ POC to run for period of 2-3 weeks for each participant
Page 40
Device Functionality
Requirements for POC
Log in and authentication
Query patient data
¾ Demographics
¾ General Problems
¾ Medications
General queries
¾
¾
¾
¾
Personal patient list
Physician Schedule (current day)
Clinic Schedule (current day)
Hospital Census
Prescribe medications and Print prescriptions
Asynchronous Lab Result notification
Page 41
General Requirements
No client code
¾Unrealistic based on one requirement
Use any device
¾Unrealistic
No horizontal scroll bars
Read-only device interface
¾Data input is very tedious
Page 42
Challenges
Solution must be easy to use
¾ Follow existing web application usage model but
presentable on handheld
HIPAA
Wireless security
¾ Was no LEAP client for Sharp Zaurus device
Device security
¾ Passwords and browser cache

Device battery life
Manage expectations
Hospital Cisco network configuration
Printing
Page 43
Cisco Network Configuration
Cisco APs are set by default to only allow
Cisco hardware to authenticate
We used non-Cisco LEAP clients
Had to change authentication type on all APs
to
¾Accept Open Authentication
Page 44
Page 45
Deployed Architecture
Blended Architecture
¾Use a thin client on device only for functional
requirements that can’t be met with the browser
¾Use the browser for all other functional
requirements
This puts the most code on the server and
the least code on the device
¾Meets all functional requirements
Page 46
Code on device to support asynchronous Lab
Result notification only
No code on the device for everything else
¾Browser based access for all other functionality
¾All other UI provided by server JSPs and Portlets
Page 47
Utilize Web Services
Web Services Front End (WSFE)
¾ Future integration point for any other entities
• Key point
¾ Can be expanded to be the front end to clinical
information system or other systems they want to
expose services from
Utilize WebSphere Everyplace Access (WEA) on
server only
¾ WebSphere Portal
Existing hospital architecture and components do
not change
Page 48
Deployed Architecture with Portal
and Web Services Front End
Locked Down
Station
Wireless
Desktop
Laptop
IBM 390
Wired
802.11b
via
Cisco
LEAP
WEA/WebSphere
Portal
Mobile Portlets
Mobile Portlets
Mobile Portlets
WebSphere
Stored Procedure
Manager
Web Services
Front End
Mobile Devices –
Browser and custom client code
getDemographics
getGeneralProblems
getMedications
getCensus
printPrescription
DB2
etc.
Page 49
Web Services Front End
Allows you to expose services in a nonproprietary manner
Can expose clinical information system or
other system functionality
Allows integration with business partners,
present and future
Page 50
Architecture Advantages
Best of both worlds
¾Minimal client code
¾Maximum functionality
Utilizes Web Services
¾Device does not invoke web services
¾Portlets invoke web services in WSFE
¾Code on device is invoked with web services
Page 51
POC can be accomplished with no disruption
to the existing system
¾Installation
¾Development
¾Testing
¾Pilot
Page 52
Solution is an add-on, not a replacement
All POC components are on a separate
machine
¾WebSphere Everyplace Access (WEA)
• Which contains Portal Server
¾WSFE
This machine queries the production
database
Page 53
Devices Used
New Sharp Zaurus SL-6000
¾ Embedix OS (Linux)
¾ Intel 400 Mhz XScale processor
¾ 64 meg or RAM
¾ Integrated 802.11b wireless radio
¾ Full VGA screen (Portrait and Landscape)
¾ Voice recorder
¾ CFII, IrDA, SD, USB
¾ Opera browser
¾ Jeode JVM
¾ QWERTY keyboard
Page 54
Devices Used
HP IPAQ h4355 PocketPC
¾Intel 400 MHz XScale processor
¾64 meg RAM
¾Integrated 802.11b, Bluetooth, IrDA
¾SD Slot
¾Voice Recorder
¾½ VGA screen
¾QWERTY keyboard
Page 55
Solution tested with Sharp SL-6000,
PocketPC H4355, and Palm Tungsten C
¾Palm eliminated due to browser issues
Device portability because:
¾Mostly browser based
¾Java for piece that is not
Page 56
Proof of Concept
Began 6/11/04
4 Physicians took part
¾Each loaned a Sharp device (two also got the
PocketPC)
¾We met with each one for training
Device is “out of the box” except:
¾Web Services Toolkit for Mobile Devices
component
¾Our custom notification client
¾LEAP client from MeetingHouse for Sharp device
Page 57
Demo
Page 58
Products/Technologies Used
WebSphere Everyplace Access 4.3 (WEA)
¾Integrated Portal Server
Web Services Toolkit for Mobile Devices
Device notification technology
¾Client and Server components
Page 59
Future Possibilities
Use WSFE to expose interfaces to other
systems
Deploy other devices
¾Palm Tungsten C
¾Others…
Use Portlets for full solution
¾Not just mobile piece
Page 60
Follow-On Architecture
Locked Down
Station
Wired
WEA/WebSphere
Portal
IBM 390
Mobile Portlets Portlets
Wireless
Desktop
Laptop
802.11b
via
Cisco
LEAP
WebSphere
Web Services
Front End
getDemographics
Pharmacy
Mobile Devices –
Browser and custom client code
Other Health
Care Facilities
getGeneralProblems
getMedications
getCensus
printPrescription
etc
Stored Procedure
Manager
?
DB2
Page 61
Issues and Concerns
Device Battery life
Device Browser anomalies
Hospital network issues
We don’t control any
Page 62
References
http://www.blackberry.net/developers/na/java/start/index.shtml –
Blackberry JDE

http://www.metrowerks.com/MW/Develop/Desktop/PalmOS/Professional/Default.htm
–
Metrowerks CodeWarrior
http://www-306.ibm.com/software/wireless/wsdd/ – WebSphere Studio
Device Developer
http://www.microsoft.com/windowsmobile/developers/default.mspx –
Microsoft page for mobile developers
http://www-1.ibm.com/industries/wireless/doc/content/solution/278603104.html –
IBM’s WebSphere Everyplace Connection Manager
http://www.mtghouse.com – LEAP clients from Meeting House
http://www.alphaworks.ibm.com/tech/wstkmd – IBM’s Web Services
Toolkit for Mobile Devices
Page 63