Skip to Content
0
Former Member
Nov 23, 2006 at 03:55 PM

MI with non-SAP backend: ANY BEST PRACTICES ?!!

51 Views

Dear All,

I was looking through some docs and articles to check what is the best practice for integration of MI customised application with non-SAP backend systems, and found them confusing and mutually-excluding.

In SAP MI 2.5 setup documentation, standard System Architecture consists of 3 main components: Mobile Device, SAP Middleware and Backend system (SAP or non-SAP without any XI in between). Further to that, it confirms that using Smart Synchronisation, it'll be possible to retrieve the data from SOAP-enabled external non-SAP system.

That statement is backed by another doc published on Service Marketplace, which describes integration of Web Dynpro applications with different backend platforms. We can find here not only SOAP link, but also additional option of using Java RMI calls for backend systems with J2EE engine.

At the same time in the same Marketplace there is one SAP Note (717510) on MI 2.5 release restrictions. According to that Note, Mobile Infrastructure does not support integration with non-SAP backend systems !

FAQ answers on SDN Web site (see the link below) clarify that Exchange Infrastructure can not be used for integration of MI with non-SAP backend either !

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cc489997-0901-0010-b3a3-c27a7208e20a#q-5-9

Because of such polar statements, it's not clear whether it's possible to link Mobile application with non-SAP system or not. And if yes, are there any best practices at all ?

Thanks,

Laziz