As for the technical architecture xMTT 2.0 consists of three parts:
- a client component that runs on top of the SAP NetWeaver Mobile Infrastructure Client
- NetWeaver Mobile on the Middleware
- the backend that the application runs against.
The offline client of SAP xMTT runs on laptops, tablet PCs, and desktops that use Microsoft Windows operating systems. These include Windows 2000, Windows XP and Windows XP Tablet PC Edition. Additionally, xMTT also requires Microsoft IE 5.5 or higher and JRE 1.4 or higher. As for the client’s hardware requirements any laptop currently on the market should meet xMTT’s hardware requirements. I would recommend at least a 1 GHz CPU and 1 GB of Ram though for performance reasons. Please note that there is currently no xMTT version for PDAs available.
Regarding the Middleware xMTT requires either SAP NetWeaver 2004 or SAP NetWeaver 2004s, which include NetWeaver Mobile (a.k.a. Mobile Infrastructure). I would recommend 2004s since it has a later end of maintenance. NetWeaver Mobile on the middleware helps you with administrating the devices and applications that are out in the field and with operating your mobile landscape.
The required hardware heavily depends on the numbers of mobile devices that you would like to have. For smaller numbers of users you probably do not need a separate box and could share a box with the backend installation. For larger numbers (hundreds or thousands) of users I would recommend a separate box for the middleware. In any case you need to think about this in the context of your project since the sizing is not only influenced by the user numbers but by the amount of data, the number of users synchronizing in parallel and your users’ synchronization frequence as well. So I highly recommend a project specific sizing.
As for the backend SAP xMTT 2.0 runs against R/3 4.7, mySAP ERP 2004 and mySAP ERP 2005 with configurations for CATS, HR & FI, ECC & ECC Extension. Please keep in mind that xMTT is a generic sync application. In contrast to Smart Sync applications the applications have to take care of the delta determination themselves which usually results in a higher load on the backend. Please make sure that your backend does not become the performance bottleneck and is able to handle the possible additional load.
If you’ve never made any experiences with mobile software you might be wondering why I am constantly hinting at load and performance. The reasoning behind this is that some customers nowadays operate mobile landscapes with up to 30000 clients / end users. It’s pretty easy to see that this number of clients can certainly result in a high load that your middleware and backend have to be able to handle.
I would assume that you will start out smaller. It’s still good to know that xMTT is able to handle this amount of users, isn’t it ?