Skip to Content

NetWeaver Mobile 7.1 from an Architectural Perspective

Mobile Environments are different from traditional IT environments. They add a new dimension in complexity as a result of the distributed environment and the diverse technologies involved. Operating mobile landscapes can therefore be a challenge for Administrators.

SAP’s new platform for Enterprise Mobility, NetWeaver Mobile 7.1, implements a large number of lessons learned from numerous customer projects and enables companies to operate bigger than ever mobile landscapes in an easier fashion.

SAP NetWeaver Mobile 7.1 is the next version of SAP NetWeaver Mobile and the successor to the SAP Mobile Infrastructure. It offers significant improvements in terms of data synchronization performance and also comes with new tools that simplify development. It also has improved Mobile Device Management capabilities to minimize the effort of managing mobile devices.

Some of the highlights of the new product are:

  • Higher Scalability to allow for the handling of more mobile devices and larger volumes of data
  • Event-driven architecture for a significant increase in system performance and shorter device synchronization times
  • New highly optimized data realignment algorithms
  • Flexible model-driven data distribution capability that makes it easier to create and change data distribution rules
  • Development of Mobile Components using the Web Dynpro framework, resulting in shorter development cycles and reduced TCD
  • Improved Mobile Device Management, Monitoring and Security
  • Ability to track security incidents, such as failed application logon attempts, and allowing taking preventative action by blocking the synchronization of a device

To protect customer’s investments NetWeaver Mobile 7.1 comes with a compatibility layer for existing mobile applications. This layer allows you to continue using mobile applications built on earlier versions of SAP NetWeaver Mobile (e.g. Mobile Infrastructure 2.5) and run those in NetWeaver Mobile’s compatibility mode.

NetWeaver Mobile 7.1 implements the three tier architecture of a typical mobile environment. It basically is the same architecture that you might know from the Mobile Infrastructure. The mobile environment consists of a number of mobile devices, a SAP NetWeaver AS Middleware system and one or more backend systems. The client connects to the Middleware by using an https connection. The middleware connects to the backend using an RFC connection.


The components needed on the mobile device are a database for data storage, a Java Virtual Machine and the Mobile Client. Depending on what client device we are talking about different versions of JVM and database need to be used. Both JVM and database provide the infrastructure the mobile client needs to fulfill its tasks. Its main tasks are to provide the runtime environment for mobile components and to exchange data with the mobile middleware. Changes of data on the mobile client are being tracked. In addition to that the mobile client manages the mobile component registry and data access to the local database.

The Mobile Middleware is the central part of a mobile landscape. Its core component is the Data Orchestration Engine (DOE). It stages object instances from back-end systems and distributes these object instances, including updates of these object instances, to occasionally connected mobile devices. Updates to these object instances, either in back-end systems or mobile devices, are tracked and distributed to all affected data stores.

The Consolidated Data Store (CDS) is a component of the Data Orchestration Engine. It is basically a data cache containing the latest version of all mobilized object instances. This helps reducing the load on backend systems in case of data realignments and when new devices are created. Queues can be configured to have the latest data (Queues are precalculated).

In addition to that the Data Orchestration Engine has a device queue for each physical device. This queue acts like a mailbox containing latest updates to object instances. During synchronization cycles, this information is picked up by the device and updates made on the mobile client are dropped off.

The Device Inventory is a component of the Mobile Administrator that is a part of the Mobile Middleware as well and serves as a central store with information on mobile devices that are currently used in the field. The information stored for these devices contains, among other data, OS type, installed applications and users.

You must be Logged on to comment or reply to a post.
  • Hi Karsten,

    Its really a cool blog to start with.

    I just wanted to know how DOE supports multi user for the same mobile device.

    It was said that we have to register/create a device ID for a particular user in the middleware and when the user sync he gets the mobileID which was created in Middleware.

    So how come the other user share the same deviceID.


    • Hey Kathick,

      From what I know you have to create the user in the middleware first. After that you have to create a user/password on the client.

      It is important to notice that the sync concept for NW Mobile 7.1 is different - with NW Mobile 7.1 synchronization is device specific. This means that there is no user specific sync.

      Authorizations are an option for allowing multiple users to work on a device without seeing somebody else's data.

      Hope this helps.