ME vs message queue

[Former Member]

Jan,

thanks for the great articles on the mobile infrastructure- appreciated! I read the material and I have an impression that ME serves pretty much the same purpose as a message queue (e.g. JMS). Is that correct or are there fundamental differences between message queueing products and ME?

Thanks again!

[jan_fetzer]

Hi Dmitry,

it is correct that queuing of messages is one of the capabilities of MI; nonetheless, MI does a lot more than that: I'd like to think of MI as three things at once: a runtime for mobile apps (featuring a local web browser that allows for JSP/AWT UI programming, extensive APIs (including queuing of requests, but also data persistence on file system/DB, data replication via business objects, tracing, multi-language support etc.), a synchronization middleware (allowing for encrypted, compressed and guaranteed delivery of requests + data replication from any SAP or non-SAP system with the granularity of business objects and finally an administration toolset allowing for deployment of mobile apps to any number of devices from a central system, assigning of business data for replciation to end-users, process control etc.).

In that, even though MI is not (today) JMS-compliant, MI is a lot more than just a queuing service.

Cu, Jan