Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Using WSO2 as a Mobile Services Platform


Published on

Published in: Technology, Business
  • Be the first to comment

Using WSO2 as a Mobile Services Platform

  1. 1. Using WSO2 as a MobileServices PlatformbySimon BiltonHead of Professional ServicesGödel Technologies Europe LtdIn association with Transport for London
  2. 2. In this session …..• How Transport for London use WSO2 ESB as the main platform for mobile services• Focus on “What” rather than “How” – I will be discussing the high level solution rather than the intimate details of the code we have developed• Real world experiences – some of the issues we found and overcame• Meet the developer(s) afterwards
  3. 3. 30 seconds of corporate backgroundSoftware Development OrganisationEstablished in 2005HQ in Manchester, EnglandDevelopment Centre in Minsk, BelarusApproximately 80 staffRepresented at WSO2Con 2011 by Simon Bilton, Head ofProfessional Services and Vladimir Klevko, Senior Developer
  4. 4. About Transport for LondonTransport for London (TfL) is the government body responsiblefor most aspects of the transport system in Greater London inthe UKExamples of the transport modes and services operated by TFL: • London Underground also known as the Tube • Surface Bus Network • Journey Planner and Travel Alerts • Near Field Radio pre-payment card (Oyster) • Cabwise SMS (Text) for TAXI Information Services
  5. 5. Journey Planner ServicesJourney Planner delivers travel information to the public viaWeb and WAP channels and associated content deliveryplatforms with over 95 million trip requests per month from4 million unique users.Journey Planner has year on year growth of over 20 % andremains one of core internet services in promoting easy oftransport planning across London.TfL WAP portals delivers 100,000 trip requests per monthwith a year on year growth rate of 10%.Travel Alerts sends out 950,000 email alerts and 900,000SMS alerts each month advising of transport problems.
  6. 6. Transport for London’s Vision for a MobileServices Platform• Consolidation of mobile messaging services across TfL• Extension of personalised services within Journey Planner• Upgrading Current Mobile & Wireless Services• Introduction of rich-client applications to the Mobile Journey Planner Services Portfolio• Introduction of enhanced Real Time Information Services• Building a foundation platform to allow quick and efficient integration of current and future TfL services• Building of other travel related services for the community, such as bicycle lane information
  7. 7. The Challenges• Build a scalable, reliable foundation platform• Promote reusability of all system components• Extend the personalisation from 200,000 travel alerts users up to 5 million mobile and web users• Integrate real time services• Meet the demands of 4 million users and 95 million journey resolutions per month• Deliver over 1 million SMS and email alerts per month now, with a growth rate of 20% per year• Allow easy integration of new services in the future
  8. 8. The Core Design• TfL mandated that the solution should be designed and built using Service Oriented Architecture principles• Use a high performance Enterprise Service Bus• Enforce strong governance and architectural principles• Establish a single point of integration for current and future TfL services• Define and re-use infrastructure, software and processes
  9. 9. Design Benefits Benefit Benefit to TfL TfL’s Customer Benefit Cost Reduction Reduced physical infrastructure Quality of service through focussed investment Reduced Complexity “Building Block” services Transparent technology Virtualised environment with Consistent delivery of management dashboard service and information Better Customer Encourage use of TfL transport “One view” of the Experience Increased customer satisfaction information Personalised, not generic Reduced Risk Common capabilities and Technology change has no services interoperate from negative impact inception Greater Control Strong governance and Confidence in the vision of architecture ensure change is TfL as a public service driven by the business Commercial Opportunity Defined and controllable Low cost, high quality interfaces enables monetisation service of services Rich, diverse information on demand
  10. 10. Extensible and Scalable Service Interfaces & SDKGovernance & Architecture model Multimodal Service Orchestration Transport Sector Verticals Timetables Parking/Congestion National Coaches Regional Buses Stops & POI Common Services Management Network Rail Monitoring Reporting Logistics Eurostar Incidents ATOC TfL Journeys Location Personalization Payments TFL Common Capabilities Why think outside of the box when the box can think for itself ?
  11. 11. Now the techie bits!
  12. 12. Schematic of Legacy Services
  13. 13. Schematic of ESB Solution
  14. 14. High Level Infrastructure Design
  15. 15. Network and Firewall Segmentation
  16. 16. Core Components• 2 x WSO2 ESB Nodes as Load Balanced Cluster Common configuration files on shared storage Running identical services on both nodes• 2 x Application Servers as Load Balanced Cluster• 2 x Message Broker Servers as Master-Slave Cluster• 2 x WSO2 BAM servers in Active-Passive mode
  17. 17. Physical Layout
  18. 18. WSO2 ESB Physical Build
  19. 19. WSO2 BAM Physical Build
  20. 20. WSO2 ESB Interfaces26 proxy services are deployed on ESB which provide thefollowing functionality across the whole solution:• Journey Planning Services (including Travel Alerts services)• Address, Geolocation and LBS Lookup Services• Mobile Application Building Services• Incident Command System (ICS) Services• Utility and Intelligent Router Services• Cabwise service
  21. 21. Utility Service• Used to receive and send SMS and emails• Email sent via SMTP relay servers using load balancing algorithm• SMS text messages sent and received on different channels using SMPP gateway*• Highly re-usable, can be called directly or used in conjunction with Intelligent Router service* SMPP=Short Message Peer to Peer Protocol
  22. 22. Intelligent Router Service• Used to route messages based on user configurable parameters such as:  SMS short-code and keyword  Email address and subject• Incorporates profanity and abuse filters• Functional Requirement: Operators must be able to easily add or modify the parameters without changing application• Uses fixed or flex keywords
  23. 23. Cabwise• Send a text to short-code 60835 with valid keyword such as “home” or “cab” or a valid postcode• Message received and processed by Intelligent Router• Calls Location Based service to locate user’s geo-position (Latitude/Longtitude)• Performs database lookup for two nearest licensed taxi firms• Sends reply SMS to user with phone numbers of taxi firms• (Premium SMS message – so TfL costs are covered)
  24. 24. Challenges we facedRequired huge amount of co-operation between all parties (3main suppliers plus 4 or more sub-contracted agents)Interdependencies between most suppliersManaged infrastructure environment was a pain! • Dual network cards in servers a particular nuisance for bindingsBugs or lack of functionality in WSO2 ESBLimited documentation on WSO2 ESB and WSO2 BAM to assistwith deploymentAlthough not a Godel deliverable, the migration of existingusers was a major issue
  25. 25. Open Source to the Rescue!Due to the Open Source nature of WSO2 we were able tochange or fix the shortcomings of some of the code such as: • Added several message builders to meet requirements • Start up failure on underlying service unavailability was fixed. Unavailable proxy service is replaced with the fake service returning valid SOAP fault • Ability to re-deploy proxy services on the fly was added • A fix was implemented to address the issue with WSDL not being returned when many concurrent requests were being sent • 202 (Accepted) response was replaced with valid SOAP fault as all proxy services are synchronous
  26. 26. Thank you for listening!- Any Questions?- See Vladimir !!
  27. 27. TfL TriviaNumber of individual passengers carried on theyear: Distance travelled by each Tube train each Tubeeach year: Length of Network:123,600km / 76,800 miles 402km/249 miles 28 million
  28. 28. More Trivia … Busiest stations: Total number of escalators: During the three-hour morning peak, Londons busiest Tube station is: Deepest lift shaft: Waterloo with 51,100 people entering 41255.2m/181ftHampstead - The busiest station in terms of passengers each year is: Victoria with 76 million