MI7.0 VS MI7.1

[Former Member]

Hi,

What is the difference between MI7.0 ,MI7.1 ?

[Former Member]

Hi Santoshkumar

According to my knowledge

In MI 7.0 there is ABAP and JAVA stack.

But in Mi 7.1 there is only ABAP Stack. JAVA stack is not required

In MI 7.0 background synchronization is not automatic

But in MI 7.1 background synchronization is automatic

Regards

Ruturaj

[pvannest]

check this blog:

/people/priyanka.singh3/blog/2009/02/26/difference-between-netweaver-mobile-70-and-71

[Former Member]

Hi,

while Larissas reply focusses more on the data flow and the SyncBO details - there is as well a big difference if it comes to the UI. Most Apps in MI7.0 run on JSP - not very performant and a complete server running on a PDA.... well..... The only other solution was using AWT and cause the runtime on the PDA was based on Creme 3.27 it was compatible with JDK1.1.8 only.

With MI7.1 SAP changed this as well. 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 more easy to build fast user interfaces. On top, SAP supports now a selection of WebDynpro controls on the client.

So if you start a new project and have a server available it makes absolutely sence to start with MI7.1 in my understanding - this is really the "lessons learned" version!

Regards,

Oliver

[former_member304703]

Yes, there is a HUGE difference.

Naming convention in this case is really misleading: there is almost no architectural changes between MI2.5 and MI7.0 but Mi7.0 and MI7.1 are two very different products.

Just to give you a few examples:

1. MI7.0 - 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 perfomance in MI7.1.

2. MI7.0 - each user on a mobile device will have a separate DB, even when users are assigned the same app. In MI7.1 one data object instance is shared, for example, an equipment will be downloaded to the device only once, even if it is required by different users (and different mobile apps, not completely sure about this last statement). Which means that with 7.1 mobile app has to handle multiple languages. And if the statement in brackets is true different mobile apps can reach data of each other (which removes a problem with 7.0 of different mobile apps integration).

3. In MI7.1 there is no transactional SyncBos anymore - everything is replicated on the middleware.

There are more changes than this, that was just a few that popped in my mind.

All the above being said - mobile app that has been written before 7.1 arrival will NOT run on 7.1 without some changes!

And truth be told, to completely utilise performance advantages promissed by 7.1 new apps have to be written based on the new mobile infrastructure architechture.

Regards,

Larissa Limarova

[former_member211905]

Hi!

We consider to install MI7.1, today we are using MI2.5. We developed our own application, jsp-based using generic sync.

You say we probably have to rewrite our application when we are going from MI2.5 to MI7.1, what do you mean by that? Can you be more precise?

Best regards

Øyvind

[Former Member]

Hi,

you can run the JSP app still - you need to convert the SyncBOs, cause this has changed - but there isa note for the conversation available. Be aware there is no S01 SyncBO any longer for example.

The UI: With MI7.1 you have a possibility to use WD or eSWT as UI - this gives you much more performance compared to JSP apps on a PDA. So you can rewrite the UI code, but you can as well run the app as a JSP still and use compatibility mode that willallow old apps to work. But to have the full beneft of MI7.1 it makessence to rewrite some areas of the code and to adapt it to MI7.1.

That is one reason why MAM for example is not available for customers as MI7.1 verison at the moment.

Regards,

Oliver