Mobile Application Manager

The Mobile Application Manager (MAM) in connection with the mobile middleware MinCor.NET addresses the core issues of today's IT departments, secure operation of mobile devices and dynamic deployment of customized user interfaces for mobile enterprise applications.

Click here to download architecture as PDF-file.

MAM with the associated mobile middleware addresses both topics - security and deployment - at the same time. Mobile Customized User Interfaces follow the design principle of smart but thin clients with a tight coupling to the server. All data is safely stored on the server and no remains are left on the client device. This design pattern reduces the risk of loosing or compromising data when a device is lost. Moreover, the application itself is deployed to the device ’on demand’ and discarded after use. The ‘application on demand’-concept enables enterprises to design and deploy applications without the need of administering mobile devices.

From a technology point of view the core features are

• Integrated security layer – support of the widely used SSL/TLS protocol
• Tight coupling  – call backs (i.e. push and pull) and connection orientation allow a tight integration of mobile client devices
• Interoperability – seamless integration of the major software platforms .Net, J2EE and CORBA
• Performance – binary protocols reduce network traffic and computing time

Core design principles for MAM are:

• The use of standards for direct integration into large business IT infrastructures
• An open architecture allowing for various authentication and authorization models (e.g. LDAP or RADIUS)
• Self-contained easy to maintain application modules ensuring scalability
• 'Applications on demand’-concept leading to a significant reduction of maintenance costs for mobile devices

The complete MAM-package for the mobile device is bundled in one installation file (CAB-file) that can be downloaded over the wireless network. The system-installer on the mobile device handles the installation file automatically.

The purpose of the Middsol Bootstrap Launcher (MBL) is to load and start the Middsol Application Launcher (MAL). The MAL resides on the server and can easily be maintained. With the separation of MBL and MAL Middsol follows the same concept as anticipated for enterprise applications. The MBL has a minimal amount of functionality and does not need to be updated whenever new versions for the launcher are available.

Click here to download MAM details as PDF-file.

The MAL has the following core features

• User Login – user authentication is checked against a directory which can be a MAM-internal module or an external provider

• SSL/TLS encrypted communication

• Application Access Control – Application access is controlled via roles (user groups)

• Application Directory – applications are organized in a directory. A customized user interface  displays the directory content in a tree node structure

• Device dependent application selection – All applications managed by MAM have a flag indicating the device they are able to run on. Selection is done accordingly

• Search Tool – each application is associated with a node in the directory containing descriptions that can be searched by key words

The general deployment procedure for any application is divided into two steps

1. Deployment of the application on the server

2. Publishing the application in a node in the application director of the MAM

In a scaling scenario MAMs themselves can be organized in directories allowing, on one hand, to spread application over various locations and, on the other hand, to organize a network of multiple applications.

The MAM offers the unique opportunity to create and maintain mobile applications without touching the client device. The design and development of mobile applications can be done in a stand alone fashion with a subsequent deployment to the MAM. Core pattern and requirement for mobile applications are summarized as follows:

• The application is compiled into an assembly or executable with a single entry point (Main)
• The application is self contained. All necessary components are packed in a single zip-file
• The enterprise application runtime is embedded in the Middsol Application Sandbox. Context information is passed from the Sandbox to the enterprise application
• On top of the .Net compact framework the mobile application can make full use of the infrastructure provided by the Middsol Mobile Middleware layer

Click here to download Mobile Application Manager datasheet as PDF-file

ã Copyright 2006 Middsol GmbH. All rights reserved.