Skip to Content

I wrote a Qualities Required for a Successful Enterprise Mobile Solution last year describing some of the important aspects of enterprise mobility.  Typically enterprise standardizes their processes and enables these processes through their Enterprise Information systems like ERP, CRM etc., and users are getting enough choices when it comes to the selection of a mobile device.  There are various devices which enable productivity application for the users and technology that is used for enabling these productivity applications is invariably different in different device types.  There is a natural need for business process world and mobile world to take few steps closer to each other in order to enable the power of mobile in the context of business.  That’s precisely what is enabled by SAP – Sybase Co-innovation platform.   

Co-innovation Architecture

SAP and Sybase jointly designed an integration of their core platforms which always had been the backbone of the enterprise mobility architecture.  Essentially SAP NW Data Orchestration Engine (Middleware component of SAP NetWeaver Mobile) and Sybase Unwired Platform are integrated through well defined mobile centric interface pattern which are standard based.  With this approach Business Process world is brought closer to the mobile world by enabling DOE which takes care of efficient business information access (both offline and online) to talk to SUP and Enterprise mobile world is brought closer to the business process world by enabling SUP to translate business information produced by DOE in the context of native device usage.  Not to forget Sybase already enables mobile application on various device types including iPhone and BlackBerry.  Picture below provides a deployment view of the integrated platform.  Based on this architecture already couple of solutions available in the market (Sybase Mobile Sales for SAP CRM and Sybase Mobile Workflow for SAP Business Suite)

SAP Sybase Co-innovation

Co-innovation Architecture Responsibilities

It is also important to understand the responsibilities of various components; otherwise there might be some confusion around integration of two middleware solutions.  In this integration responsibilities are clearly separated and integrated platform provides one joint mobile infrastructure which solves end to end need of the enterprise mobility with all the required Qualities Required for a Successful Enterprise Mobile Solution.

DOE Responsibilities

  • Business data responsibility determination
  • Business data integrity
  • Business data synchronization with delta handling and multiple version handling
  • Business information direct access (like opportunity lookup)
  • Server side programming model and development/customizing environment

SUP Responsibilities

  • Native application & application development infrastructure for client
  • Messaging and connectivity to the device
  • Device management
  • PIM synchronization

Joint Responsibilities

  • End-2-end lifecycle management for deployment, version control and trouble shooting
  • End-2-end integrated application dev and customization programming model
To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member
    Dear Ramprasadh,

    As the architecture stated has SUP in the middle of client and DOE. So will it impact the performance on the response to the client. And also it may introduce more management burden and trouble shouting might be difficult as there is one more layer introduced between client and DOE.

    It is just my perception.


    1. Former Member Post author
      Hello Kiran
        This is the primary reason why there is clear separation of concern.  When it comes to mobility we need to connect device world (messaging & connectivity) with the business world (data & integrity).  Both are clearly separated (can even argue roles of people dealing with these systems are different, business and IT) and it provides one unified MEAP for any enterprise.  Probably if you look at the details of integration this might be more clear E.g. Device management/interrogation/provisioning would be done through SUP, Business transaction monitoring/data conflict/error resoultion/business rules etc., will happen in DOE.  This clearly distinguishes the roles and responsibilities and helps in providing proper SLAs by IT to the end users when it comes to error resoultion.  I will try to blog one more level of detail in coming weeks and will try to make it more clear.


      1. Former Member
        Hi Ramprasadh,

        Could you please clarify differences between SUP 1.5.2 and NW Mobile 7.1 SP9 in terms of SAP data distribution rules, data synchronization and conflicts resolution. According to documentation both platforms have frameworks to address these concerns.

  2. Former Member
    Dear Ramprasadh,

    SUP can connect to SAP R/3 via webservices (SAPJCO Connector) and has cache database also i assume to monitor the conflict.Error Handling i am not sure if its possible in SUP.Then why a enterprise should invest in DOE when they can directly access SAP R/3 via webservices using SUP?

    Best Regards,

    1. Former Member Post author
      Hello Devendra
        This requires understanding of little bit of details.  Part of the high level answer is in responsibilities of these boxes which are arrived at based on the core strength.  Will add more examples to explain this in detail very soon


      1. Former Member Post author

        Can you throw some light of the need of Sybase and netweaver mobile to enable SAP mobility. If SAP R/3 BAPI can be accessed via webservices (SAPJCO connector), from the blackberry jdk or objective c for iPhone development, what are advantages of introducing two additional layers, Netweaver mobile and SUP?


  3. Former Member Post author
    Hi Ram,

    SUP / NW 7.1 combinedly says for two best functionality use both , but you can also go with SUP for small level mobility project.SAP has accquired purely SUP for multi level OS support.

    But presently from a technical prespective getting partially convinced is kind of ok , but when it comes to managerial action to be taken , with these new dimensional multiple option products somewhere left unaswered ,where it is hard to convience.Multiple views are rasied why to have this , we can achieve the same with that , but later the tech team falls short of added advantage which may be realized later.

    My sincere advice to comment on these aspects how is the performance w.r.t SUP and MI combinedly ? for the sake of admin clarity we cannot make system complex where we need to log into multiple system to know status.

    Mobilty is a new topic  , well why SAP has not planned to put only use best part of Sybase in NW 7.1 and make it as single unit.

    Mobiltiy world is seems to be interesting , but each ppl’s views are clearly confusing.

    Same thing happening with PI 7.1 and then 7.3 with java only but can have abap , for BPM u can use BPMN.

    why all these ?



Leave a Reply