Category Archives: Customers

Fulfilling Integration Aspirations at the University of Exeter

Integrating 50 software applications in just three months – this is the feat Chakray Consulting UK achieved for the University of Exeter using WSO2’s integration capabilities. A part of the Russell Group, the University of Exeter is renowned for its research intensive agenda. As with any world-class educational institution, the University of Exeter seeks to build winning partnerships with their diverse student base and employees, create an impact with their research and ensure their strategies are future-oriented. Their digital strategy falls within this framework and a university of this scale (over 20,000 students, approximately 4,000 employees and campuses located in multiple locations) has several different systems in operation.

“Integration is strategic, it is always long term,” explains Jack A. Rider, CTO of Chakray Consulting. Accordingly, the university wanted to discard their legacy systems and adopt a cloud framework and service-oriented architecture. The beginning was quite daunting – as there were over 50 third party applications to contend with, and much of the time was spent on meetings alone (around 1,500 hours as shown by a rough calculation). Yet, the project was made easier because the university’s enterprise architects had a precise idea of the architecture they aspired to. Furthermore, Chakray Consulting has developed a solutions accelerator to build WSO2 platforms from code. As the name suggests, it expedites this process.

Selecting a cloud provider raised some issues as well initially – the Zero solution enabled them to create this on-site, Chakray then used AWS, switched to Microsoft Azure and reverted to AWS (without causing any significant changes to the project timelines). The current architecture uses a range of systems – SQL Server, Oracle Database, Git repository and Amazon Aurora to name a few. WSO2’s integration platform was used as the modular design, was absolutely necessary for integration of this scale, engages with continuous integration and automation technologies to enable the Zero solution, and could be used for hybrid and cloud deployments.

Now that the integration has proved successful, Jack is especially thankful for the encouraging leadership extended by the University which, in his opinion, is one of the lesser mentioned aspects of large-scale projects.

Watch Chakray’s presentation for more details of their integration feat.

Explore the WSO2 middleware platform with its offerings in integration, API management, identity and access management, analytics, and IoT.

A Smarter Transport Management System for London with the Help of WSO2

Transport for London (TfL) has a daily challenge – to keep a city of over 8 million people moving around the metropolis. Its magnitude can neither guarantee the transport system will always absorb commuters nor give them a congestion-free experience. It is a place where the smallest of changes would have a massive impact on your journey. Citing an example, Roland Major, a former enterprise architect at TfL, says that a London Underground strike once saw a 3% increase in traffic and a staggering 90 minute increase in journey time. Estimates project a 60% increase in congestion around central London by 2031.

Given all these complications, TfL decided to become more intelligent with technology to reduce commuter times, make the roads safer for pedestrians, cyclists and drivers, and to slow the pace of traffic. Intelligence and data with a purpose are the buzzwords here. “We need better understanding of real-time demand. What insight can we get from our data, and how can we get innovative with all this information?” says Roland. He was actively involved with TfL’s Surface Intelligent Transport System (or SITS), a project that aims to better manage the city’s entire road space of pavements, cycle lanes, and motorways.

SITS’ business proposition is that it can offer billion pounds’ worth benefit to London by identifying delays in the road networks sooner than it is done at present: “We weren’t detecting incidents, and by the time we have detected them, they were already over. With technology, we can see these incidents early. We recognized that the market can do sensible things with our data,” says Roland. For example, within the traffic light system in London, TfL manages an estimated 7,000 junctions around the city and 14,000 magnetometers detect millions of daily events. This data is discarded after analysis; however, if used, TfL realized that the response time to delays improved by 15 minutes.

TfL has a 10 year plan in place, with all the of different required components mapped out. Data analytics form the core of this operational model. Data is obtained from GPS systems and bus routes. The road incidents are logged and used to determine what additional information is needed to understand and manage each leg of commuter journeys. All the data is hosted on the cloud and currently TfL is in the process of adding these components to the framework.

TfL’s transport management system

London’s new road management system relies on WSO2’s API management, integration, identity and access management, and analytics products for the intelligent work needed. These products are deployed on a private cloud managed by WSO2. The starting point – LondonWorks, a registry of all road works and street related events, both planned and current, in the Greater London area. LondonWorks is used to assess road networks, coordinate the various road works to minimize congestion and for inspection, compliance, and monitoring. Maps and forms of type data have been integrated to allow entry of incidents into the system and their identification on the map.

As their model progresses, TfL has ambitious plans for all the data they have streaming in – big data analytics to give them more insights to road movements, which will enable them to give the necessary alerts and empower them with smarter ways to deliver better, safer commuter experiences for London.

Watch Roland’s presentation for more details on TfL’s plans for London.

Explore the WSO2 middleware platform with its offerings in API management, integration, identity and access management, analytics, and IoT.

Did you know that WSO2 won TfL’s data analytics Hackathon contest? Learn all about it.

Building a Cloud Native Platform for CitySprint’s On the Dot Delivery Service

Picture a scenario where you are analyzing the results of a marketing survey which shows that a high percentage of consumers prefer same day shipping, online tracking of their orders, choice of shipping options, and deliveries within a specific time slot. Then you find out that retailers already fulfill around 65% of these needs, but there is a gap in the market, a gap that you can fill by offering a novel service. This is precisely what UK-based logistics and delivery service provider, CitySprint did when they developed the On the dot delivery service, which allows shoppers to receive their orders during a one hour time slot of their choice without extra costs.

“We wanted to positively disrupt the time slot delivery space. In doing so, we wanted to build an API ecosystem that sparks interaction, open new channels and reach new streams of revenue,” says Eduard Lazar, Senior Solutions Consultant at LastMileLink Technologies (a CitySprint Innovation Lab). At the heart of of this project was generating value for users and driving innovation, “On the dot is all about convenience for consumers, be it as a fulfillment method or in terms of collection and delivery time slots. We also wanted to simplify integration and create a developer community through our API ecosystem,” he adds.

Defining the key challenges was one of the first steps before introducing On the dot to consumers. To begin with, CitySprint had to move their data centers to the cloud in order to become a cloud native platform. They also had to create open RESTful APIs, enable identity federation, foster innovation so that it can result in a community of developers who will think up new marketable ideas and simplify integration. Selecting open source software is one of main tenets at CitySprint, and as such, they set about developing an open source platform made of WSO2’s API management, integration and identity and access management capabilities, using a DevOps approach. Meanwhile, the architecture was developed using Apache’s Tomcat and Cassandra, and WSO2Carbon used for continuous deployment.

By placing API management at its core, CitySprint has been able to achieve the required functionality and formed their innovation community (an interesting anecdote on the latter, a TechSprint event was organized where high profile companies sent teams of developers to CitySprint to build innovative products within 24 hours. Results have been quite amazing with an added bonus of introducing CitySprint to new leads).

From a business perspective, implementing this project was primarily underpinned by issues of costs, in addition to those of speed, integration, lifecycle, and skillset. When CitySprint introduced more complexity into the system, this also meant they potentially introduced a time lag. Yet, can this platform control costs through simplification and reuse? Is there a way to save time by simplifying integration? Is the skillset future proof? Can they model the whole lifecycle?

The result – On the dot – answers all the above with a yes. On the dot cloud native platform has empowered CitySprint to enter the market with an adaptable platform, which allows developers to self-sign and begin using the APIs, it is integrated as there are multiple systems working together, they have also connected data and devices, integrated platforms with those of their partners, and connected the user experiences of both customers and partners. Following their successes in the UK, plans are underway to make On the dot a global phenomenon and CitySprint is certain they can achieve this with the right technology.

If you need more details on how CitySprint made On the dot, watch their presentation.

Learn more about WSO2’s API management, integration and identity and access management capabilities.

UNRWA and Capgemini: Creating a Refugee Centric Data Model for Better Insights

The United Nations Relief and Works Agency for Palestine Refugees (UNRWA) has over 5 million registered refugees requiring education, healthcare and social safety assistance, among others. UNRWA aids refugees across five countries – namely Lebanon, Jordan, the West Bank, Syria, and the Gaza Strip which has over 500,000 students, 692 schools as of now, and hundreds of primary health facilities.

In order to automate several processes across the region, the team based in Gaza had already developed the Education Management Information System (EMIS) consisting of three modules (students, staff and premises) and reporting tools. EMIS captures information and manages the educational progress of half a million students, by integrating data from registration, health, facility management and human resources systems that are already in existence.

Yet, given the numbers and scale of its operations, a central data model that has the capacity to integrate data from several entities was the need of the hour to support its regional operations and EMIS. To transform their information management system, UNRWA and Capgemini used WSO2 technology to create a model which mirrors UNRWA’s organizational ethos – placing the refugees at the heart of all their operations.

“The technology is there, but it’s really about the people,” says Francesco Lacoboni, Managing Consultant at Capgemini. Accordingly, the main drivers of the new UNRWA Enterprise Architecture are built upon the strategic principles of people, information, collaboration, and security. People influence how the information is created, managed, and consumed. The platform is an information-centric one – rather than managing documents, it manages open data and content. Its shared approach design aims to improve collaboration, reduce costs, maintain standards, and ensure consistency across the board. Security and privacy features for data protection round off the principles of this platform.

Before the new model was introduced, there was a time where the information that streamed through the system was physically replicated via the transaction log. For reasons of ease and efficiency, UNRWA and Capgemini decided to provide a common set of APIs to all the developers, not only to fulfill the needs of the specific application, but to also create the framework for future use of this semantic concept. Every entity has a credible API that can be used to navigate the knowledge, eliminating the need to design a new API. The resultant Common Data Model (CDM) was created using OWL (Web Ontology Language), and its architecture and governance completed using WSO2’s integration and API management platforms.

For Luca Baldini, Chief of Information Management Services at UNRWA, it was the first time such an approach was used and now that it has been rolled out, he praises its benefits: “The new model has been very productive, as it created a common language between IT specialists and our business representatives. We can use different kinds of technology for data retrieval and distribution.” Francesco believes one of the main benefits of the new model is that it helps increase the transparency of UNRWA’s operations. Now that the new model is successfully in practice, analytics is the next frontier and they hope to leverage WSO2’s analytics capabilities to meet their requirements. Spurred by the possibilities of analytics, plans are in the pipeline to use this data model along with unstructured data provided from the field to improve operations and add further value.

You can watch Luca’s and Francesco’s presentation at WSO2Con USA 2017 to hear more about their project.

Learn more about WSO2’s integration, API management and analytics capabilities if you would like to use them in your enterprise.

State of Arizona: Introducing a Statewide Private PaaS to Improve Efficiencies and Trim Costs

Government institutions across the globe are using cloud-based technologies to add value to citizens and improve their functionality. The State of Arizona is no different, having built the Arizona Enterprise Services Platform (AESP) to reduce costs, improve efficiencies and foster sustainability in the long term. With over 32,000 state employees, 170 business units, over 1,400 IT professionals, and over 100 data centers/server rooms, a transformation of this scale was challenging. Yet, Prasad Putta, the director of enterprise technology services at the Arizona Strategic Enterprise Technology (ASET) office in the State of Arizona who oversees this project, saw an opportunity for improvement and seized it.

ASET is responsible for IT strategy, enterprise capabilities, policies/procedures, and managing high-risk, high-funded projects. AESP was rolled out as an answer to several questions: “How do we not start projects from scratch, stop re-inventing the wheel all the time, and have better data sharing practices? What can we do about redundant solutions throughout the enterprise, ease up license cost payments and solve security issues?” asks Prasad. With these in mind, Prasad and his team had a clear set of objectives they wanted to achieve. At the top of the priority list were cost reduction and sustainability as being a public institution, accountability was a key consideration. Other objectives included the enforcement of standards, revenue generation from data and services, a profitable mechanism for data sharing, allowing better data discoverability, risk reduction, and ease of development/maintenance from a developer’s perspective.

To address these requirements, ASET turned to the public cloud and decided to implement AESP as a private PaaS. The team at ASET was not looking to replace all the applications, rather prefered custom applications across the state agencies. They were also looking to expose data through APIs for private consumption, make the collaboration environment API-centric across the state, shorten their development cycle and ensure all the data is private to the state to mitigate any security and compliance risks. ASET was also looking at economies of scale as not all of the hundreds of applications were fully utilized at one given time. Their existing architecture was entirely hosted on AWS, but for the revamped architecture, AWS was limited to the infrastructure while the rest was built by using WSO2’s integration and identity and access management capabilities.

Introducing AESP brought with it another set of challenges. With agencies working independently, they had to be convinced to opt-in for this platform. Additionally, round-the-clock support was needed along with the right pricing model. Fortunately, AESP found the successful strategies and has several applications in the pipeline now. “Size the menu right” is one of Prasad’s analogies for success, i.e. to reduce the scope of applications to the most sought after ones. Initially, his team spent 30% to 40% of their time maintaining the sheer volume of applications, which is now handled by WSO2’s Managed Cloud. Several issues, such as the pricing model, are still work in progress, but buoyed by the successes, Prasad foresees a busy future.

For more information, watch Prasad’s full presentation at WSO2Con USA 2017.

Find out more about how you can use WSO2’s integration and identity and access management capabilities to improve your organization’s operational efficiency.

The WSO2 Approach to Creating and Managing Content for Open Source Products

“Just open, honest communication is the best thing in the world” (Brett Davern). I was delighted when I stumbled upon this quote, because it sums up our approach to technical content at WSO2. There are plenty of advantages to open content: driving adoption and expansion, improving content quality via better feedback from users, and increasing successful usage of our products.

You may wonder why we make our documentation and even our training content publicly available for free. After all, support is an integral part of our business model, and it contributes to a sizable percentage of our revenue at WSO2. What we have discovered is that high-quality, freely available content does not deter users from buying support. For customers who are building mission-critical solutions, support is essential to receiving timely responses to problems they may be experiencing, whether it’s a bug in the code or a question about the best way to solve a particular problem.

One of the primary advantages of open content is that it drives adoption and expansion. Our goal is to have as many users as possible, and when our documentation and training content is freely available, users have a better opportunity to get up and running with our products quickly and effectively. As they learn ways to solve their business problems with our solutions, people discover more of our products and features that can be used to solve other problems that they envision.

Another major advantage is that open content helps you to improve content quality. More readers mean more feedback. At WSO2, we take it one step further by making the documentation available during the development process itself to ensure that we receive feedback during the entire content release cycle. Getting user feedback early helps us immensely in the planning stage to make sure that issues of concern are addressed in our next release.

When developing training content, we point to the documentation for much of the conceptual information, so that as you learn to use the products during training, you become thoroughly familiar with the documentation as well. This approach allows users to easily go back and find information after they’ve completed the training. We’ve also discovered the following best practices for creating content for open source products:

  • Categorize the content types – at the beginning of a release, plan not only the documentation and training content for each new feature but also what would work best as technical articles, blog posts, or marketing content.
  • Write for a wide audience – open source products have wider audiences, many of whom are non-native English speakers. Use clear, concise language and include a glossary of terms.
  • Test and review on multiple platforms.
  • Engage the community – introduce simple processes for contributing, develop reward systems, build relationships with users, and recognize people’s strengths to maximize contributions from a wider community.
  • Release documentation at each milestone to encourage timely and ongoing feedback.

When your content is ready for distribution, there is a range of platforms you can use. We primarily use Confluence and GitHub at WSO2, but some other platforms we’ve been researching are ReadtheDocs.org, Mkdocs, and Asciidoc.

To learn more about these platforms, best practices, open source content licensing, and detailed advantages of open content, check out my webinar on creating and managing content for open source products.

Honoring WSO2’s Long-Standing Customers by Helping Those in Need

Earlier this year at WSO2Con USA we celebrated our customers who’ve stuck with us through thick and thin for 10 long years — eBay, Kaiser Permanente, Trimble and Concur. In recognition of their long-standing relationship with us, we launched the WSO2 10-Year Customer Anniversary Undergraduate Scholarship Program — a program that offers a full undergraduate university scholarship to passionate students in Sri Lanka.

Standing by our commitment to education (we have over 100 alumni that have or are currently pursuing master’s degrees or PhDs), we figured there’s no better way to honor our customers than by helping those who need financial assistance in following their dreams of a quality education.

The fully-paid program enables the selected students to obtain a degree in Computer Science, awarded by the prestigious University of Westminster, London, UK, through Informatics Institute of Technology (IIT), Sri Lanka. The program also provides a monthly allowance paid by WSO2 to meet daily expenses and mentoring by WSO2 employees throughout their school tenure.

We partnered with IIT and began the search for the perfect candidates in early August. We received many applications from students from all walks of life but had to narrow it down to four (for the four customers). We selected the students based on their financial need, educational qualifications, and extra-curricular activities.

After a lot of deliberation, we announced the selected candidates last week! Our Congratulations go out to

  • Negeesha Divyanjalee Katulanda selected for the BSc (Hons) Computer Science course
  • Piyumi Hansika Madhubani Gamage selected for the BSc (Hons) Computer Science course
  • Chanuka Abeysinghe selected for the BEng (Hons) Software Engineering course
  • Jayasanka Buddhika Weerasinghe selected for the BSc (Hons) Computer Science course

We wish you all the best!

Brigham Young University: Enabling API Discoverability and Data-driven Business Insights with WSO2

Brigham Young University (BYU) began their API Management story 2 years ago when they decided to adopt an API-first architecture that follows a governed process. With over 451 APIs for both external and internal customers, and several development teams working independently of one another, Brayden Winterton (Software Engineer at BYU) likens its management akin to running a small city.

Modernizing their API management was a result of a problematic system that existed at that time. For one, the API manager in existence was closed-sourced and used an old, unsupported third party code. Adding some confusion to the mix, BYU had two versions of their API infrastructure in production – having started with one version, developing a second version along the way and the migration process forever a work in progress. Due to a memory leak, boxes had to be rebooted nightly (if not all API traffic ceased by noon the next day). Furthermore, there was no monitoring of API usage and the documentation support was out of date. In short, BYU was in a “serious situation” to use Brayden’s exact phrase.

Faced with all these scenarios, BYU was looking to implement a new API management solution. A key need was to create a centralized repository for all the APIs at BYU, which enables developers to search for and find all the available APIs, in addition to the respective authorization processes. A seamless transition without drastic changes to their existing developer work was another one of their important requirements. Low latency, up-to-date documentation, integrating with legacy systems and the ability to keep track of all the APIs being utilized completed their wish list.

To implement their requirements, they turned to WSO2 API Manager and WSO2 Identity Server. BYU now has subscriptions that allow consumers to get through to the API and subsequent monitoring; they were able to integrate all legacy systems with message mediation, minimized latency even while mediating quite heavily and of course, it is all open source. The BYU model works on open subscription first, however there are instances where they have needed to block a subscription until further approval was granted. They have been able to do this with an open source platform. Another huge plus has been the ability to utilize industry standards and BYU even got something that was not available to them previously – monitoring and analytics to support their business decision making. Improving discoverability and keeping the documentation up to date were the last pending issues for BYU, ultimately solved by the BYU developer portal in the second stage of their implementation.

“Our developers who have migrated are having a fantastic experience. They’re able to use things in a standard way, able to find the documentation they are looking for, utilize libraries, things aren’t drastically different, all of their old systems are continuing to work and they are getting a lot better reliability out of what they’re trying,” says Brayden. Adding to this success, BYU has seen higher API consumption as of late and with the improvements in place, Brayden is excited about the future.

If you would like to listen to Brayden’s full presentation at WSO2Con USA, click here.

Learn more about the WSO2 API Manager and WSO2 Identity Server if you haven’t tried it out yet.

Nutanix: How WSO2’s Identity Server Enhanced Customer Experience

Nutanix is a leader in hyper converged systems with a mission to make infrastructure invisible by delivering an enterprise cloud platform that enables you to focus on the applications and services that power your business. At WSO2Con USA 2017, Director of SaaS and Tools Engineering at Nutanix Manoj Thirutheri explored how WSO2 Identity Server helped them enhance their customer experience to stay competitive against large vendors like HP, Microsoft and Cisco.

Nutanix provides over 4450 customers across the globe with a hyperconvergence appliance that has storage, virtualization and network components overlaid by an intelligent software layer in order to minimize the need for infrastructure. “Customer experience is the last mile of digital transformation,” Manoj said while stressing on the importance of creating an integrated ecosystem of customers and partners to be successful. They currently maintain multiple web portals for customer support, partner support, and the community. One of their top priorities is to make customer experiences as simple and seamless as possible. They needed to create a more seamless sign-on experience for their portals and mobile apps to maintain growth.

Because of the speed at which Nutanix was growing, many identity silos existed, which meant the same customer was identified in multiple ways. They had non-standard and insecure authentication and authorization mechanisms in place which made them vulnerable and hindered their user experience. Furthermore, their ability to be agile and innovate fast was deterred by the proprietary technology they used, which was not open or extendable. “The bottom line is, we didn’t know what our customers or partners were doing. We were lost,” notes Manoj. Having a 360 view of their customers’ activities and keeping track of them across the different portals were key requirements of their solution to these challenges.

As shown in the diagram below, Nutanix used WSO2 Identity Server to overcome their major identity and access management challenges. Manoj then explained the architecture from the bottom up. The highly available WSO2 Identity Server cluster is load balanced across multiple regions for high redundancy. Next, they built an intelligent API layer, which exposed all the APIs including user management, tenant management, service provider and identity provider APIs. By doing so they avoided vendor lock-in and didn’t couple their functionality to any technology, be it open source or proprietary. The third layer consisted of their own entitlement system called My Nutanix where customers and partners register and access the service providers. The green boxes at the top depict the service providers including the following:

  • The customer portal enables customers to access the services offered in My Nutanix.
  • The partner portal allows partners to perform deal registrations among other things.
  • The community portal is open source and can be used by anyone. Here, they use WSO2 Identity Server to authenticate the users through basic OAuth over Transport Layer Security (TLS), which allows them to track the users and gain new customer prospects.
  • They also have the educational and training portal in addition to many other service providers that are still in development.

Nutanix currently uses many industry standards for authentication including OAuth 2.0, OpenID Connect, and SAML 2.0, which are all supported out-of-the-box by WSO2 Identity Server. They also use WSO2 Identity Server for Just-in-Time (JIT) provisioning of users. Nutanix performs SMS-based multi-factor authentication (MFA) by using WSO2 Identity Server connectors to integrate with Twilio, which allows you to programmatically send and receive text messages using its web service APIs. In addition, they integrate with their partners through the Active Directory Federation Services (ADFS) provided by WSO2 Identity Server.

Apart from these implemented features, Nutanix is working on leveraging more capabilities of WSO2 Identity Server. They will soon bring in multi-tenancy because every customer has their own tenant with their own isolated roles. They will also experiment with a service-based authentication, a fairly new concept to them, which uses certificates to authenticate the user and creates the service accounts within WSO2 Identity Server. As Manoj states, “Two services, no human interaction”.

Having a product that is open source, supported multiple security protocols, and can scale was key. WSO2 Identity Server met all these requirements. WSO2 Identity Server helped create a seamless single sign-on experience for their customers, partners and prospects, while keeping track of all their actions. A key advantage that helped sustain Nutanix’s rapid growth was WSO2 Identity Server’s high scalability and availability and its ability to support a rapid increase in the number of users from 1000 to 100,000 in just two years. It met all of Nutanix’s requirements including out-of-the-box support for many standard protocols, multi-factor authentication (both SMS-based and Google authenticator), identity federation, multi-tenancy and tenant management. Furthermore, Nutanix also used WSO2 Managed Cloud, which provides excellent support.

“We now have a bunch of happy customers and partners. We ourselves are also very happy with WSO2 Identity Server,” Manoj added.To learn more about how Nutanix leveraged WSO2 watch Manoj’s talk at WSO2Con USA 2017.

Verifone: Using WSO2 Technology to Provide a Unique Payment Terminal that Increases Customer Engagement

In Honolulu, Hawaii, one man’s vision for the future of commerce has now become one of the world’s largest point-of-sale (POS) terminal vendors and a leading provider of payment and commerce solutions. Verifone still upholds this vision and keeps innovating for the future. At WSO2Con USA 2017 Ulrich Herberg, a senior Java architect at Verifone, joined us via Skype to speak about how they leveraged WSO2 technology when creating Verifone Carbon – a powerful device that combines elegant design into an integrated POS solution.

Verifone Carbon is a payment terminal that sets a new standard for a valuable and engaging consumer experience. It consists of two parts: a larger Android tablet facing the merchant and a smaller terminal with different kinds of payment functionality, such as Apple pay and payment through credit cards. These two devices are placed on a mobile base, which is used for charging the devices, printing receipts, and connecting to the ethernet.

What makes Verifone Carbon unique is that it’s embedded in an ecosystem called the Verifone Commerce Platform, which consists of a number of additional systems that provide more than what a typical payment terminal offers, explained Ulrich.

  • The developer portal allows third-party developers to create their own customer and merchant facing application by using Verifone’s APIs to download software development kits (SDKs) that can trigger payments, get information of successful or failed payments and more.
  • The app marketplace provides an interface similar to the Google Play Store or the Apple App Store where these apps can be placed and purchased.
  • The estate owner portal is used by large corporations that directly deal with the merchants to
    • Manage the estate (all the devices)
    • Get an overview of the devices
    • Manage, create, remove and update merchants
    • Purchase apps for the merchants
  • The merchant portal provides a smaller scope for the merchants only, which allows them to see their devices and purchase apps for their devices

With Verifone Carbon, merchants can now reward their best customers with loyalty points, display promotional media and coupons, leverage beacons for store analytics and invite customers to redeem personalized offers in real-time among other things.

Ulrich explained that for all of this to happen, they needed a solution that allowed them to manage and monitor all the Carbon devices. They started by evaluating commercial products. The commercial products worked on a pay-per-device model which would have been costly as they scaled up. At often times they didn’t have all the features they required and didn’t provide the flexibility to create any customized features.

The fully open source WSO2 Enterprise Mobility Manager (WSO2 EMM which is now significantly enhanced to provide enterprise IoT solutions as well as mobile device and app management in a single download via WSO2 IoT Server) overcame all of these challenges. “We were able to create a solution that fit our exact needs by either modifying the product on our own or getting WSO2 support services to help modify it,” said Ulrich. They avoided vendor lock-in and are independent of anyone else because they have control over the source code. They were also able to easily integrate WSO2 EMM with their existing terminal management infrastructure.

Ulrich then went on to discuss three major use cases of WSO2 EMM in Verifone Carbon.

Use case 1: Blank Android devices are shipped to the merchants so that they all have the same operating system image. WSO2 EMM uses individual device certificates to identify, authorize and authenticate these devices using mutual Transport Layer Security (TLS).

Use case 2: Verifone already has a legacy terminal management system which runs on a different operating system that can’t directly connect with and use Android features. So they used WSO2 EMM to communicate with the tablet.

Use case 3: Verifone doesn’t use the interface provided by WSO2 EMM so they had figure out how to use WSO2 EMM as a black box. They call it from their terminal management system, sends commands and monitors all the devices through it without having to know how it works internally. They did this by working closely with WSO2 to create a thorough list of RESTful APIs that were documented in Swagger.

Ulrich went on to list a few more WSO2 EMM features they currently use including

  • Getting device information including location data
  • Over-the-air (OTA) update that allows you to update the OS remotely
  • APK installation/update/removal in the background
  • Remotely locking, rebooting or factory resetting the devices
  • Debugging and sending Android logs to the server
  • Sending pop up notification to the tablet

He concluded by explaining in detail how they plan on scaling WSO2 EMM as the number of devices becomes larger.

To learn more about how Verifone used WSO2 technology to increase customer engagement through a unique payment terminal watch his talk at WSO2Con USA 2017.