This documentation is for WSO2 Enterprise Mobility Manager version 1.0.0. View documentation for the latest release.

Unknown macro: {next_previous_link3}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

WSO2 Enterprise Mobility Management (EMM) comprises of two components, namely Mobile Device Management (MDM) and Mobile Application Management (MAM). WSO2 EMM is 100% open source, and is developed on top of WSO2 Carbon for greater scalability and interoperability. The WSO2 EMM architecture diagram is as follows:

MDM enables organizations to secure, manage and monitor Android and iOS powered devices (namely, smart phones, ipod touch devices and  tablet PCs), on both corporate and personal (employee-owned) devices, irrespective of the mobile operator, service provider or the organization. The Device Management sub-module, within the MDM, enables the MDM to communicate with the MDM console. The Notification module handles the Google Cloud Messaging (GCM) service for Android, and the Apple Push Notification Service (APNS) for iOS. These notification services send data from the MDM server to the respective users' devices. The MDM uses the Adapter as a mediator to communicate with iOS and Android powered devices. The Application Management module is a sub-module within the MDM, which enables communication between the MDM server and the MAM server. The Admin can connect their own user store to the EMM. However, we do not allow a secondary user store to be connected.

MAM enables organizations to control the corporate applications on mobile devices, which are enrolled to the MDM. MAM has three key consoles to manage the the corporate applications, namely the PublisherStore and MAM Console. Users with publisher rights can use the Publisher to publish, unpublish, deprecate or retire their mobile apps; while users with reviewer rights, can approve or reject mobile apps that are submitted for approval. Users can use the Store to discover mobile apps easily, and install apps to their own mobile devices. The Admin uses the MAM console to manage users, policies, and to install and uninstall mobile apps in bulk.

  • No labels