WSO2 Enterprise Mobility Manager (EMM) is a unique solution designed to specifically address the mobile enterprise needs. EMM includes of two key aspects: Mobile Device Management (MDM) and Mobile Application Management (MAM). WSO2 EMM also supports single sign-on (SSO) and multi-tenancy.
EMM enables organizations to secure, manage and monitor Android and iOS powered devices (i.e., smart phones, ipod touch devices and tablet PCs), irrespective of the mobile operator, service provider, or the organization. Users need to accept the Policy agreement, which states all the actions that can be carried out on the device when enrolling with EMM. EMM only controls the corporate data that is present on the devices, while the personal data is left untouched.
First user experience
In the previous WSO2 EMM releases it was mandatory for the users to fully configure WSO2 EMM before being able to run the product. Now, WSO2 EMM 2.0.0 binary pack comprises of a default Android Agent. Thereby, enabling users to seamlessly download and run EMM without any prior configurations. This will allow users to use Android devices to get a better understanding of WSO2 EMM.
Local notification method for Android devices
The GCM server has a limitation on the number of messages that can be sent to the GCM server. However, this new Local notification method for Android devices does not make use of the GCM server. Thereby, the number of messages sent via the GCM will be minimized. Furthermore, the Local notification method does not send the messages via the payload, as it did in previous EMM versions. Thereby, this will minimize the MDM command loss.
Tenant based configuration
The tenant admin will be able to use the Configuration Manager wizard to setup the tenant's general, Android and iOS configuration details. Thereby, this allows each tenant to customize their settings based on their requirements. For more information, see Tenant Based Settings.
Ability to change password
Previously, users were not allowed to change the default password that was assigned by WSO2 EMM. However, now users are allowed to change their password. Thereby, users will be able to change their default password to a password of their choice.
Removal of devices from WSO2 EMM
Previously, administrators were not allowed to remove devices from WSO2 EMM after they were enrolled. However, now the administrators can use the Enterprise Wipe feature to remove enrolled devices from WSO2 EMM. Thereby, this will enable the administrators to maintain WSO2 EMM efficiently.
Improved API security
The APIs that are exposed to the devices have been secured in WSO2 EMM using OAuth.
Improved compliance monitoring
When the system is clustered, then using the nTask Component, only one node will be allowed to perform the compliance monitoring that will dispatch messages to the GCM or APNS.
Bug Fixes / Improvements
For the list of fixed issues, go to WSO2 EMM 2.0.0 - Fixed Issues.
For the list of known issues, go to WSO2 EMM 2.0.0 - Known Issues.
Issues can be reported using the public JIRA.
Engaging with Community
Join our mailing list and correspond with the developers directly.
Developer List : email@example.com | Subscribe | Mail Archive
WSO2 encourages you to report issues, enhancements and feature requests for WSO2 EMM. Use the issue tracker for reporting issues.
We encourage to use stackoverflow to engage with developers as well as other users.
We are committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology.
For additional support information please refer to http://wso2.com/support/
We welcome your feedback and would love to hear your thoughts on this release of WSO2 EMM.
--WSO2 EMM Development Team--