Skip to Content

As most of us already have been working on SUP architecture which says Sybase Unwired Platform is a mobile enterprise application platform used to create applications that could connect to heterogeneous back-end business data and can be deployed to various mobile devices with many other features.Similarly we have Agentry Mobile Platform offered by Syclo, it is an extensible framework for developing, deploying and managing  a wireless business application architecture and with many other features.

 

Here, I am summarizing all possible difference between these two mobile application development approaches:

 

 

1. From the Architecture point of view:

 

 

1.PNG

 

 

Key Areas SUP Syclo Agentry
Server Product Editions
  • Personal Development
  • Enterprise Development
  • Enterprise Server
  • Development Server
  • Production Server
Back Ends Support
  • SAP
  • Database (With JDBC)
  • REST/SOAP web service
  • SAP
  • Database
  • REST/SOAP web service
  • Files (with OS command scripts)
Various Application Types
  • Native App (Object API)
  • NativeApp (OData)
  • Hybrid App (HTML5)
  • Agentry Player App (Meta data driven)
Device Type Support SUP based apps are supported on
specific versions of mobile OS
Agentry based apps are supported on
specific devices of mobile OS

 

 

2. Mobile App Development:

 

There are few differences in mobile application development approaches using Sybase Unwired Platform and Syclo Agentry.

 

SUP Sylco Agentry
Mobile SDK Agentry Editor
Mobile Business Objects Agentry Objects
Attributes Properties (String properties, Object Properties,Collection properties)
Operations(CRUD)
  • Read operation is performed by a Fetch.
  • Create, Update, Delete are performed by Transactions.
Relationships Properties
No Integrated rule modeling tool Rule editor allows to model, test,
publish and reuse rules.
Analytics Functionality (MAKit) No Analytics Functionality

 

 

 

 

 

3. Mobile Solutions at Runtime:

 

 

SUP Syclo Agentry
Synchronization using Cache Database
On Mobilink Server
Synchronization using BackEnd
Exchange tables
  • Mobilink Protocol (RBS)
  • iMO Protocol (MBS)
  • HTTP/HTTPs (OData)
  • ANGEL messaging protocol
Authorization based on LDAP Nothing like this
SUP based Push Agentry based Push

 

2.PNG

 

 

 

4. SAP Mobile Solution Portfolio

 

 

3.PNG

 

SAP Syclo SMART Mobile Suite:

 

  • SAP Work Manager
  • SAP CRM Service Manager
  • SAP Inventory Manager
  • SAP SMART Rounds

 

check here for more details.

 

5. Mobile Application Lifecycle Managment:

 

 

6.PNG

 

7.PNG

 

From SMP 2.3 onwards,Sybase Unwired Platform and Syclo Agentry both are running on same server.

 

8.PNG

 

References: Wikipedia, SAP TechEd Mobility session

To report this post you need to login first.

7 Comments

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

  1. Michael Appleby

    Hi Jitendra,

    Quite a bit of information here.  Some of which you may want to modify a little for the specifics of Agentry applications.  Overall a decent outline, but if these images are copies of other content, please explicitly define the source for each as it is used.

    CRUD (Create, Read, Update, Delete) equivalents in Agentry are (Transaction, Fetch, Transaction, Transaction).  Or in simpler terms, a Read operation in Agentry is performed by a Fetch, while all processes which involved changing the backend are performed by Transactions (Create, Update, Delete).

    The SMART Suite picture of the various applications is no longer used and I sure hope that was not presented at TechEd.  Some of the apps listed were decremented before the apps were approved for release under the SAP management.

    Agentry does have analytics on the backend as part of the Addon in ERP or Maximo.  But I could be misunderstanding what you mean by Analytics.  Perhaps you could provide some examples of what you meant?

    Regards, Mike

    SAP Rapid Innovation Group – RIG

    (0) 
    1. Jitendra Kansal Post author

      Hi Michael,

      First of all thank you so much for detailed feedback.

      CRUD (Create, Read, Update, Delete) equivalents in Agentry are (Transaction, Fetch, Transaction, Transaction).  Or in simpler terms, a Read operation in Agentry is performed by a Fetch, while all processes which involved changing the backend are performed by Transactions (Create, Update, Delete).

      I have updated this part in above blog.

      The SMART Suite picture of the various applications is no longer used and I sure hope that was not presented at TechEd.  Some of the apps listed were decremented before the apps were approved for release under the SAP management.

      I have removed that SMART Suite picture. I didn’t know about some of the mentioned apps were decremented. I am very new to Agentry and i am doing some R&D to learn it.

      Agentry does have analytics on the backend as part of the Addon in ERP or Maximo.  But I could be misunderstanding what you mean by Analytics.  Perhaps you could provide some examples of what you meant?

      see, In SUP, Mobile Analytics Kit (MAkit) allows users to graphically view data in different types of chart. This MAKit can be used with SUP HWC.

      Do we have similar thing in Syclo Agentry?

      I referred MOB 101 Syclo Agentry for SAP Mobile Professionals for above summary.

      Rgrds,

      Jitendra

      (0) 
      1. ashish satapathy

        Thanks jitendra for this useful information on syclo.

        its very easy to catch the concepts on sup and syclo by making comparison between them.

        so its very helpful..

        (0) 
          1. ashish satapathy

            Hii Jitendra..

            your blog on SYCLO is very effective.

            I just want the list of ADD-ons that need to be configured in our Landscape for Syclo implementation. so if u can kindly providing the add-ons list ,it will be a great help.

            Regards

            ashish satapathy

            (0) 
  2. Steve Streeter
    Authorization based on LDAP Nothing like this

    If you set the Agentry Server’s File System Connection Enable Users, and set the “userDomain” to the network domain the users belong too.  This tells the Agentry Server to send the user information to the OS to call out to the AD to validate the user on that domain.

    If the Agentry Server is running on Linux you, the server needs to have a PAM module reconfigured.

    (0) 

Leave a Reply