Mobile Client Technology (mySAP CRM) is client technology designed for Microsoft Windows-based, occasionally server-connected CRM field applications. These applications offer a rich function set, such as SAP CRM Mobile Sales and SAP CRM Mobile Service.
Mobile Client Technology works in conjunction with SAP CRM Middleware, assuring full integration of mobile clients with the CRM server. The server-side and client-side CRM Middleware components provide sophisticated data synchronization including; replication and realignment services, integrated software logistics for design-time and runtime objects, backup and recovery mechanisms as well as extensive administration and system monitoring capabilities. The generic runtime framework serves as the implementation environment for mobile applications. The runtime framework consists of a Business Document Layer (BDL), a Business Object Layer (BOL) and a User Interface Layer (UIL) on the mobile clients. The three-layer architecture supports the paradigm of separating presentation, business logic and persistence of application data. An underlying relational database stores the application data.
With the SAP Mobile Application Studio (MAS), developers of mobile applications experience a state-of-the-art development environment. The environment facilitates visual modeling of mobile applications by providing design tools, wizards and implicit code generation. SAP MAS uses an integrated, object-oriented repository, the Mobile Application Repository (MAR), to store all development objects of the Business Object Layer (BOL) and the User Interface layer (UIL). SAP MAS manages multi-user development by supporting version management, change history and collision handling, and controls software logistics with transport and upgrade support.
Business Documents (BDocs) as well as the table structures reside in the CRM Middleware repository on the CRM server; they are defined and maintained there. Respective runtime data must be transferred to the Mobile Clients, and this occurs during the usual installation and upgrade procedures.
Components & Integration
The following illustrations detail the various components of Mobile Client Technology for mySAP CRM and show how they fit into the CRM system landscape for the mobile scenario.
Running Mobile Client Applications
Mobile Client Applications, for example, SAP CRM Mobile Sales, run on laptops or tablet computers with a Microsoft Windows 32-bit operating system. The applications run in offline mode and offer rich functionality for working with business data. The business data is stored in the local User Database on each mobile device. From time to time the user triggers data synchronization with the CRM server via the Communication Station to send and receive all updated data. The CRM Middleware takes care of proper handling, updating and distribution of the data from and to the various Mobile Clients. On the CRM server the full set of mobile data is stored in the Consolidated Database. Furthermore, administration and monitoring facilities of the mobile landscape are available on the CRM server.
Developing Mobile Client Applications
Mobile Client Applications are designed and developed with the SAP Mobile Application Studio (MAS). SAP MAS offers various visual modeling tools to build the applications in a three-tier manner. All development objects of the User Interface Layer (UIL) and the Business Object Layer (BOL) reside in the Mobile Application Repository (MAR) and are accessed from SAP MAS tools as needed. The UIL is the presentation layer for user input and output while the BOL contains the application business logic. Built-in code generators produce the runtime files of the UIL and BOL. The runtime files are deployed to the various mobile clients using the CRM Middleware. The persistence and synchronization layer, called the Business Document Layer (BDL), provides a view for filtering the user database data and acts as an object oriented wrapper for the relational data.
BDocs as well as table structures are modeled on the CRM server. The corresponding runtime files are deployed to the mobile clients along with the runtime files of the UIL and BOL.
The MAR connects to the CRM server, allowing for transport of design-time data. In the standard three-environment system landscape (Development, Quality, Production) every MAR is connected to its own CRM server. As a result, design-time data can be transported from one environment to another using the standard SAP transport system. Runtime data however, must be generated and deployed within the same system environment.
Release Dependent Information