Page Comparison

Background

In the past, organizations used to strictly enforce the COPE (corporate-owned, personally enabled) model on mobile devices to ensure data security. However, multiple users can use a single COPE device, reducing the level of accountability and increasing the level of vulnerability. Today swipe-savvy smart phones have flooded the market due to the evolution in mobile devices. As a result, organizations are getting accustomed to adopting the BYOD (bring your own device) program, which allows employees to use their personal mobile devices to access valuable corporate data and applications. This helps to increase employee collaboration, efficiency, and productivity; however, the organization is vulnerable to security threats. Therefore, organizations have a growing need to monitor and manage corporate and personal (employee-owned) mobile devices that have access to corporate data. 

...

WSO2 EMM consists of three key consoles: EMM Console, Publisher and Store. Users use the Publisher to manage enterprise apps throughout their application life cycle, which includes application states such as, published, unpublished, approved, rejected, deprecated, and retired. The Store acts as a marketplace and contains all the corporate mobile apps, which users can search, view, rate and install on-demand. The administrator uses the EMM Console to manage users, administer EMM policies, install or uninstall mobile apps in bulk, and more. Furthermore, WSO2 EMM is released under Apache Software License Version 2.0, one of the most business-friendly licenses available today.

See the WSO2 screencast for a step by step tutorial on how to get started with WSO2 EMM and for an overall explanation of the entire EMM console.