S.No. | MI 7.0 | MI 7.1 |
| 1. | - Have ABAP+JAVA stack.
- Doesn't have Data Orchestration Engine.
| - There is only an ABAP Stack. No JAVA stack is required.
- Netweaver Mobile Administrator has been completely re-written in ABAP WebDynpro. WebDynpro runtime is part of the Mobile Client for handhelds.
- Completely re-designed middleware (now has Data Orchestration Engine).
|
| 2. | All replicated data resides in one table MEREP_207. | In MI7.1 replica DB is a real DB with multiple tables which removes MI7.0 limitations on replica DB size as well as increases sync performance in MI7.1. |
| 3. | Each user on a mobile device will have a separate DB, even when users are assigned the same application. | In MI7.1 one data object instance is shared, for example, data will be downloaded to the device only once, even if it is required by different users which mean that with 7.1 mobile app has to handle multiple languages. |
| 4. | Has SyncBos for transaction. | In MI7.1 there is no transactional SyncBos anymore - everything is replicated on the middleware. |
| 5. | Most Apps in MI7.0 run on JSP - not very performing and a complete server running on a PDA. The only other solution is to use AWT because the runtime on the PDA is based on Creme 3.27, compatible with JDK1.1.8 only. | Even on PDA MI is based on a Creme version compatible to JDK1.4 and so you can even use eSWT and SWING UI - making it much easier to build fast user interfaces. On top, SAP supports now a selection of WebDynpro controls on the client. |
| 6. | No such feature available. | The new architecture allows for prefetching and precalculation of data to be sent to the client before the client actually connects. So lot of traffic on the backend if many clients connect at the same time should be gone with 7.1. |
| 7. | No such feature available. | To minimize impact of lost or stolen devices following features are available: - Lock device.
- Remote wipe device data.
- Ability to track security incidents, such as failed application logon attempts.
- Allows blocking the synchronization of the device.
|
| 8. | No such support was available. | The mobile client now supports J2ME CDC on PDAs and JSE 5.0 on laptops. |
| 9. | No such built-in capability for third party integration is there in NW 7.0. | Integration with non-sap system using ESR/XI Integration by calling enterprise service inside BAPI wrapper. |
| 10. | This feature not available here. | Partial and full reset/erase of client data store remotely. The administrator can remotely reset or erase the data of certain data objects or all data objects. |
| 11. | Background synchronization is not automatic | Automatic background synchronization on client. The mobile client can be configured to automatically trigger the synchronization cycle (when network connection is available) without user interaction. |
| 12. | No such information provided by NW7.0. | Statistics and alerts: Administrators get a central view of the current statistics, for example, the number of processed messages, newly created devices, initial/delta loads, and so on. Alerts are used to pro-actively notify administrators once the value reaches a certain threshold (for example, average synchronization duration > x seconds, queue size > x kb). |
| 13. | Feature not available. | - Configurable device inventory: The device inventory holds information on all mobile devices in a landscape, such as mobile components, agent configuration, and users on device.
- The device inventory can be configured: New attributes can be added which could be useful for administration purposes (for example, the device model) or for data distribution (for example, the work center ID). You can decide whether the device inventory is maintained manually and/or automatically using information from an external source (back-end system or file). Organizational changes that affect devices can, therefore, be reflected automatically.
|
| 14. | No such feature. | - Comprehensive message and device monitoring: A comprehensive set of new monitoring tools provides different views for monitoring activities. The data flow of messages coming from devices and back-end systems can be tracked in detail. The consolidated data store and individual device queues can be displayed easily to speed up troubleshooting tasks. Messages with problems (error or conflict) can be reprocessed.
|
