POINT-TO-POINT vs. MEAP THE RIGHT APPROACH FOR AN INTEGRATED           MOBILITY SOLUTION      A RapidValue Solutions White...
Executive Summary                                               There are two commonly used approaches for building       ...
Enterprise Mobility SolutionsGone are the days when employees would sit in front of their desktop computers all day to do ...
As the name implies, cross-platform development frameworks provide the ability to develop once anddeploy across multiple p...
Approach                 Pros                                   Cons  P2P Solution             User experience is rich (ty...
INTEGRATED                                                        AUTHMOBILE DEVICE       DEVELOPMENT MANAGEMENT         E...
Comparing Point-to-Point and MEAPThe following table summarizes the key differences between Point-to-Point solutions and M...
Overall Cost         Customizations are expensive. IT cost            –      Lower administrative, maintenance            ...
Number of operating systems           7+                            7+ for native applications supported Access to HTML5 c...
Integrated Development                Eclipse plugin from Kony     Eclipse IDE Environment (IDE)                          ...
Choosing the Right ApproachWhat approach works best for your enterprise? While each organization will have a different mob...
ConclusionOf all the factors driving the need for mobility, the main parameters to consider are the number ofapplications,...
About RapidValueRapidValue is a leading provider of end-to-end mobility solutions to enterprises worldwide. We offer arang...
Upcoming SlideShare
Loading in …5
×

Point-to-Point vs. MEAP - The Right Approach for an Integrated Mobility Solutions - Whitepaper by RapidValue Solutions

2,561 views
2,259 views

Published on

There are two commonly used approaches for building integrated mobility solutions: Point-to-point integration and Mobile Enterprise Application Platform (MEAP).
This paper explains why an enterprise mobility integration solution is needed, describes and compares the two approaches, and provides a guide for how to choose the right mobility integration technique for your organization. The paper also examines various MEAP platforms available and the key differences between popular platforms - Kony and SAP Unwired Platform.

From a mobile application development standpoint, there is another widely used approach: cross-platform development frameworks. These frameworks allow
developers to build once and deploy across multiple device platforms. However, these frameworks lack integration and mobile device management capabilities,
and therefore we have excluded them from consideration for the purposes of this whitepaper. To learn more about cross-platform development, download our whitepaper: “How to Choose the Right Architecture for your Mobile Application” -
http://www.rapidvaluesolutions.com/whitepaper/

Published in: Technology

Point-to-Point vs. MEAP - The Right Approach for an Integrated Mobility Solutions - Whitepaper by RapidValue Solutions

  1. 1. POINT-TO-POINT vs. MEAP THE RIGHT APPROACH FOR AN INTEGRATED MOBILITY SOLUTION A RapidValue Solutions Whitepaper Feb - 2013
  2. 2. Executive Summary There are two commonly used approaches for building integrated mobility solutions: Point-to-point integrationEnterprise mobility has and Mobile Enterprise Application Platform (MEAP).transformed the way This paper explains why an enterprise mobilitybusinesses engage with integration solution is needed, describes and compares the two approaches, and provides a guide for how tocustomers, partners and staff choose the right mobility integration technique for yourwhile exchanging critical organization. The paper also examines various MEAPinformation. Innovative platforms available and the key differences betweenapplications are only part of popular platforms.an overall mobility solution –integrating them with existing From a mobile application development standpoint, there is another widely used approach: cross-platformsystems in a scalable manner development frameworks. These frameworks allowis equally important and can developers to build once and deploy across multiplebe even more challenging. device platforms. However, these frameworks lack integration and mobile device management capabilities, and therefore we have excluded them from consideration for the purposes of this whitepaper. To learn more about cross-platform development, download our whitepaper: “How to Choose the Right Architecture for your Mobile Application” - http://www.rapidvaluesolutions.com/whitepaper/A RapidValue Solutions Whitepaper Feb - 2013 02 02 RapidValue Enabling Mobility
  3. 3. Enterprise Mobility SolutionsGone are the days when employees would sit in front of their desktop computers all day to do theirwork and communicate with coworkers and clients. More and more companies are adapting enterprisemobility solutions to make it easier for their employees to work out of the office using mobile devicesand cloud services to perform business tasks.The two most popular enterprise mobility deployment techniques are:01 Point-to-Point: An application deployment technique which allows mobile users within the organization to perform a business operation and engage with co-workers and customers. It is mainly designed for smaller organizations.02 Mobile Enterprise Application Platform (MEAP): An application middleware designed specifically for mobile enterprise application users. It allows controlled access to all mobile applications hosted on a particular platform. Employees and enterprise customers can access and exchange data from any mobile device to perform a number of business operations.Definition of MEAPThere is a general tendency to combine MEAP/middleware tools with cross-platform mobiledevelopment tools. We would define MEAP as a platform that includes:– Comprehensive integration capabilities – Connectivity to corporate systems such as ERP, CRM, etc.– Mobile application development – Integrated Development Environment (IDE) for building mobile applications– Mobile Device Management (MDM) capabilities – Support for device provisioning, secure transmission of data, remote configuration, mobile asset tracking, policy identification and adaptation, etc.– Mobile Application Management (MAM) capabilities – Support for provisioning and access control to mobile applications used in business settings (configuration settings, user authentication, push notification services, application usage analytics, etc.)A RapidValue Solutions Whitepaper Feb - 2013 03 02 RapidValue Enabling Mobility
  4. 4. As the name implies, cross-platform development frameworks provide the ability to develop once anddeploy across multiple platforms, but mainly on the client/device side with minimal support forintegration. Since this paper is about integrated mobility solutions, we focus on the MEAP approach,with the view that cross-platform frameworks are outside the scope of the discussion.MEAPExamplesCross- Platform DevelopmentFrameworks ExamplesPoint-to-Point Solutions vs. MEAPPoint-to-Point ApproachTypically, a Point-to-Point (P2P)integration solution is used to developan independent native application foreach business requirement, usingindividual resources/middleware to MULTIPLE MIDDLEWAREhandle the data and control layer of the FOR EACH DATA WAREHOUSEapplication. This solution is useful when APPLICATIONdata segregation is possible andindependent security for the application NATIVE APPS ASis required. REQUIRED AND BASED ON LOCATION POINT-TO-POINT DEPLOYMENT ARCHITECTUREA RapidValue Solutions Whitepaper Feb - 2013 04 03 02 RapidValue Enabling Mobility
  5. 5. Approach Pros Cons P2P Solution User experience is rich (typically Need to build each application based on the based on native application specific business requirement, with limited development). reusability. Less expensive to build compared to Any changes required in the application need MEAP if the features required are developer involvement. straightforward. Performance is higher compared to Requires additional integration with identity MEAP since there are fewer management. applications to handle. Requires third-party connectors to integrate with external systems.MEAP ApproachGartner Group has developed a concept called the Rule of Three for determining when to use a MobileEnterprise Application Platform (MEAP). According to the rule, you should use the MEAP approach forenterprise mobility if the business requirements include (i) Three or more mobile applications, (ii)Three or more mobile OS (Operating Systems) and (iii) Integration with at least three back-end datasources. IPAD DESKTOP MOBILE ENTERPRISE APPLICATION PLATFORM (MEAP) IPHONE BLACKBERRY MEAP DEPLOYMENT ARCHITECTUREA RapidValue Solutions Whitepaper Feb - 2013 03 05 02 RapidValue Enabling Mobility
  6. 6. INTEGRATED AUTHMOBILE DEVICE DEVELOPMENT MANAGEMENT ENVIRONMENT EAI ADAPTERS | SERVICE BUS SERVER (CLOUD OR ON-PREMISE) WEB SERVICES WEB ENTERPRISE POLICY EAI TOOLS + DIRECTORY APPLICATION PACKAGES ENFORCEMENT LOGIC SERVICES SERVER DATA SOURCES DATABASE CONNECTIONS HTTP(S) HTTP(S) SERVER MULTICHANNEL VPN RELATIONAL VPN SOFTWARE APPLICATION ACCESS NoSQL DISTRIBUTION LOGIC GATEWAY DATABASE DEVICE CLIENT CLIENT OFFLINE APPLICATION APPLICATION OFFLINE NATIVE HTML5 BROWSER CLIENT AGENT UI+ LOGIC RUNTIME STORAGE BROWSER STORAGE Source: robtiffany.com MEAP ARCHITECTURE BLOCK DIAGRAM Approach Pros Cons MEAP Highly scalable architecture. Initial investment is high – requires upfront payment for the solution, maintenance fee and user based fee. Pre-integrated to identity Dedicated administrator is required to management system. maintain the MEAP server. Supports multiple platforms – native User interface and usability are (iOS, Android, Windows Mobile, sub-optimal. BlackBerry), web (XHTML browsers) and hybrid applications. Can leverage device features Initial implementation time is higher. seamlessly. Plug-in or connectors are available to communicate with systems such as SAP, Oracle, CRMs, etc. Web service layer runs on DMZ to secure the entire infrastructure. The solution can be deployed on premises or in a cloud.A RapidValue Solutions Whitepaper Feb - 2013 06 03 02 RapidValue Enabling Mobility
  7. 7. Comparing Point-to-Point and MEAPThe following table summarizes the key differences between Point-to-Point solutions and MEAP. Parameters Point-to-Point Solution Mobile Middleware/MEAP User Interface Typically a native application – rich user Not as great as point-to-point experience Cross-device Unique solution for every mobile device/ One solution across a wide range of mobile platform support mobile OS devices Device Each device update needs to be man- – Builds are specific to each type of Management aged individually device – Remote locking of mobile devices and remote wiping of data are supported Flexibility & – Each application update needs to be – New applications can be placed in a Change managed separately pre-defined shared location in the Management middleware – Multiple proprietary tool sets are required for managing & monitoring – Centralized management of data applications, security and devices – Single tool for managing all devices, applications and security Remote Not part of the solution but possible to Allows OTA provisioning to many devices Installation and distribute them over the air individually and mobile operating systems Updates simultaneously Connectivity Multiple integrations required to connect Pre-integrated with all kinds of backend all backend systems databases and other applications Security Each point-to-point solution has its own – Data resides in a centralized server security controls – Controlled at one location with single console Scalability & Requires additional hardware and software – Flexibility in expanding mobility Redundancy to support additional users and/or mobile applications – Seamless user experience with increase in number of users and/or mobile applications on the platform Implementation Initial investment is low Initial investment is high Cost Performance Decreases as number of hosted mobile High, with optimized services between applications increases client and server networksA RapidValue Solutions Whitepaper Feb - 2013 03 07 02 RapidValueEnabling Mobility
  8. 8. Overall Cost Customizations are expensive. IT cost – Lower administrative, maintenance increases with increase in team size and support costs (mobile enterprise app users) – Cost-effective if many mobile enterprise applications are to be supported supportedSummary Comparison Between Two Key MEAPsThe table below summarizes the differences between two popular MEAPs: Kony and SAP Unwired. Wehave selected only these two MEAPs for comparison to illustrate key parameters you should evaluatebefore deciding on the right MEAP for your enterprise. Parameters Kony SAP Unwired NATIVE APPLICATION CAPABILITIES Single code base for all native Yes Native UI components have to be UI components developed specific to each platform using native languages Access to all native capabilities Yes Supported with code written in native Native code generation Yes Not at present User experience Rich UX Browser-dependent. Code must be written specifically for each native platform PLATFORMS SUPPORTED Device platforms iPhone, Android, BlackBerry Windows Mobile 6.0, 6.1, 6.5 (Standard (4.2.1 and above), Win- and Professional), Windows XP, Vista and dows Phone (5.0 up to 7 (32 bit and 64 bit), BlackBerry 5.0 and Windows 8), Symbian, 6.0, iOS 4.2 and 4.3 Palm, J2ME Desktop clients/kiosks Windows 7 Windows XP, Vista and 7 Device-optimized mobile web Eight dedicated websites for Not at present 15+ browsers, five form factors, from WML to HTML5A RapidValue Solutions Whitepaper Feb - 2013 08 03 02 RapidValue Enabling Mobility
  9. 9. Number of operating systems 7+ 7+ for native applications supported Access to HTML5 capabilities Yes Yes PLATFORM FEATURES Language used Lua/Javascript Mainly Java, .Net and Objective C are also used Cross-platform debugger Yes Not at present Quick UI preview on all Yes None. Need to build and compile the platforms projects to view the UI Foreign function support from Yes Not at present single codebase Ability to seamlessly create Yes Requires usage of platform specific native deployable binaries for native SDK tools (to be configured and all platforms understood) Extensions – ability to augment Yes, all glue code is Yes, but glue code has to be manually existing APIs without auto-generated written for each of native SDK knowledge of underlying SDK Drag & drop widgets for UI Yes Needs to be done outside the developer development platform Coding required for consuming Not required Yes, all data mapping code has to be data from network services and handwritten mapping it to the UI widgets (80% of the application codebase) Wrapper-based solution (uses By default purely native, Yes, a hybrid web based container WebView for rendering) optionally WebUI can be approach used for rendering Synchronization capabilities Yes. Also supports offline Yes. Also supports offline sync sync Ability to download a new Yes Yes version of the application without accessing app stores Mobile Application Management Yes, supported via Kony App Requires additional license and compo- with App management Store and Kony App nent via Afaria capability Management ContainerA RapidValue Solutions Whitepaper Feb - 2013 09 03 02 RapidValue Enabling Mobility
  10. 10. Integrated Development Eclipse plugin from Kony Eclipse IDE Environment (IDE) INTEGRATION AND CONNECTORS Backend system integration Web Services support – Sybase ASE 12.x and 15.x, Sybase SQL REST/SOAP Anywhere 11.x, Oracle 10g and 11g, MS SQL Server 2005 and 2008, UDB 9.1, SAP R/3 4.6 and higher, SOAP and REST (XML) Services Extensible connectors to Yes Yes consume data from SAP, web services, XML, Java API Oracle backend support Yes Yes Connectors to Siebel, Yes Information not available PeopleSoft and SharePoint Connectors to SAP Five ways to connect to Supports JCO, Gateway and Web SAP JCO, Gateway (OData), Services Web Services, HTTP, iWay , and SAP Namespace (inside SAP) – i.e. no middleware SMS/MMS (2-Way & push) SMS/MMS – 2-Way and Not supported common push APIsA RapidValue Solutions Whitepaper Feb - 2013 03 10 02 RapidValue Enabling Mobility
  11. 11. Choosing the Right ApproachWhat approach works best for your enterprise? While each organization will have a different mobilitystrategy, when it comes to selecting mobile enterprise applications, you will reach a point where youhave to decide between a point-to-point solution and MEAP. As always, the right solution for yourorganization depends on your business requirements. The following figure illustrates key factors thatwill help you decide on a mobility solution that’s appropriate for your organization. – Focus is on building a small number of applications to run on a few mobile operating systems only (Blackberry, iOS, Android, Windows mobile) POINT-TO-POINT – Out-of-the-box solution is acceptable, and does not require much SOLUTION customization – Requires very few internal updates – Requires device-agnostic solution MEAP – Host multiple mobile applications across multiple mobile operating (MOBILE systems MIDDLE WARE) – Simplifies integration to back-end systems – Cost-effective over the long term POINT-TO-POINT SOLUTION VS. MEAPAccording to industry experts, a MEAP PERFORMANCEsolution works best for organizations looking TCO PER USERfor over three mobile applications or above Hi MEAP PERFORMANCE150 users. This decision-making chart willhelp you select between the two enterprisemobility approaches. However, before makinga decision, you need to understand the prosand cons of both types of enterprise mobility POINT SOLUTION PERFORMANCEsolutions and the cost involved in switching MEAP TCObetween the two solutions in the future POINT Lo SOLUTION TCOshould that become necessary. Users 50 100 150 200 Applications 1 2 3 4 DECISION MAKING CHARTSource: [Sybase White Paper]: What’s the point? Comparison of Middleware Vs. Point SolutionsA RapidValue Solutions Whitepaper Feb - 2013 03 11 02 RapidValue Enabling Mobility
  12. 12. ConclusionOf all the factors driving the need for mobility, the main parameters to consider are the number ofapplications, the device platforms to be supported, the amount of flexibility and control you need formanaging the servers and how quickly you plan to scale up. A point-to-point solution is the mostcost-effective and fastest approach for an immediate, single mobile application deployment. MEAP isbest suited for organizations with a well-defined mobility strategy and a vision for expanding their useof mobile applications.If you have any questions or need more information about building an integrated mobilitysolution, give us a call at 877-690-4744 or visit us at RapidValueSolutions.com. We lookforward to hearing from you!A RapidValue Solutions Whitepaper Feb - 2013 03 12 02 RapidValue Enabling Mobility
  13. 13. About RapidValueRapidValue is a leading provider of end-to-end mobility solutions to enterprises worldwide. We offer arange of mobility services across industry verticals, drawing upon a team of 175+ experts in mobilityconsulting and application development, along with experience delivering over 200 mobility projects.RapidValue delivers its services to the world’s top brands and Fortune 1000 companies, and has officesin the United States and India. www.rapidvaluesolutions.com www.rapidvaluesolutions.com/blog +1 877.690.4844 contactus@rapidvaluesolutions.comA RapidValue Solutions Whitepaper FebMobility Information Series – Jan 2013 - 2013 03 10 02 RapidValue Enabling Mobility

×