Information about MI 7.1

[Former Member]

Hi ,

I want some information about MI 7.1 architecture and how MI client 7.1 works with respect to the Mobile Device.

I found some information like MI 7.1 has only ABAP Stack so how can i develop applications in webdynpro java,

in 7.0 we have Abap Stack and Java Stack so how it differs from 7.0.

Regards,

Sunaina Reddy T

[Former Member · Accepted solution]

Hi,

DOE (the server part ) contains only abap stack. The default client framwork(mobile client) contains the java stack.

For more information on developing applications check out the [developer's guide|http://help.sap.com/saphelp_nwmobile71/helpdata/en/8F/0B674240449C60E10000000A1550B0/frameset.htm]

There is also option to migrate applications from 7.0 to 7.1 ; It will not be a smooth upgrade due to architectural changes., hence would be a two box upgrade(at the server). Applications could be migrated with minimal efforts to continue working with NW Mobile 7.1

Regards,

Liji

[former_member206242]

Hi,

SAP Netweaver Mobile 7.1 constitutes of DOE (middleware) and Mobile client

SAP Netweaver Mobile Client 7.1 are based on java stack whereas DOE which in turn talks to SAP backend are both based on ABAP stack. So client applications are still developed using WDP java.

This is similar to MI 7.0.

regards,

Nipun

[Former Member]

Hi ,

Netweaver mobile 7.10 is not just another new version of Netweaver Mobile 7.0

Mobile 7.10 comes with a complete architectural change and has more capabilities compared to 7.0 , high scalability(data volume, number of devices etc) , better modeling options, multi channel access , lesser synchronization time to name a few.

NW mobile 7.1 could be used to build mobile applications suiting offline and onlines scenarios.

In few words to mobilize enterprise solutions

SAP R/3 will act as backend

---talks to DOE through remote enabled BAPI Wrappers ---

NW mobile will be middleware that does the data orchestration

-

---

Upon Synchronization of mobile device with DOE using a messaging protocol over http(s)

Receivers could be devices with client application installed / another server.

Netweaver mobile constitutes of server (DOE) and a default client framework (Netweaver mobile client) .

Mobile application could be created using NetweaverDeveloper Studio(NWDS) that will present the data required by the mobile device user.

This mobile application once deployed on a device will work on the local persistency and during synchronization with DOE sends the modified/new data to Backend via DOE.

Customers can also develop a custom client framework and application that still talks to DOE (and inturn to backend)

check this [elearning stuff|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/204fc387-6646-2a10-99b7-bba030bc3f68] for architecture of NW mobile 7.1

Regards,

Liji