Hi,
Please refer following points discussed today with regard to App management
in EMM.
Participants: Inosh, Kasun, Milan, Hasunie, Madhawa, Lakshman and Gayan.
App update operation
=================
Currently, App Manager provides an option to create a new version of an
existing app by replicating its metadata. Here, the user has the option to
upload a new binary file. This process doesn't keep a relation to the old
app and there is no API to notify that an update exists for the previous
version of the app. An API needs to be written in order to read registry
data of the newly created app and notify the version status of a particular
app.
Three options to update an app:
1. Automatic updates pushed to devices when an app update is available.
- When a new version of the app is added in AppM publisher, the devices
which have already installed the particular app will get a notification.
This will be done along with a policy installed on the device. This
particular policy will define whether to notify updates or not.
2. Update button on AppM store view to trigger an update manually.
- The manual update option will allow the user to select a particular
device to push the app update to. When doing this, we need to address the
following issue.
An older version of the newly added app may or may not be previously
installed on all devices that are added to EMM, or some devices may not
have the app installed at all. Therefore, there needs to be a mechanism to
minimize the number of unnecessary app installation requests sent to
devices. One suggestion is to maintain the Device ID, App Name and the
Version mapping in EMM and expose them through a REST API. In the AppM
store, this API will be called and a filtering will be done prior to
listing down devices, that are eligible for an Install, Update and
Uninstall. Respective operations will be enabled/ disabled accordingly.
3. Enterprise Update button on AppM store view.
- In addition to the role based and user based approaches, we need to
integrate device grouping into this. A new tab "Device Groups" will be
added to Enterprise Install/ Update screens.
When adding a new version of the app in publisher, the admin user has the
option to either deprecate the previous version of the app or to maintain
different versions simultaneously.
Scheduled App Install, Uninstall and Update
==================================
There will be an option added on AppM UI to schedule above three tasks.
These scheduling params will be added to the operation request. The actual
scheduling will happen on EMM end through an ntask TaskService. However, in
order to schedule operations with a geographic compatibility, device's time
zone will be added to device info.
Monitoring
========
A policy will be installed on the device, in which the blacklisted and
whitelisted app IDs are listed. A monitoring operation will be initiated by
the server periodically, which will enforce the aforementioned policy on
the device. The policy's compliance will be checked on the device and be
notified to the server.
Thanks,
--
*Gayan Kaushalya Yalpathwala*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
LK: +94 71 868 2704
UK: +44 747 844 3609
<http://asia14.wso2con.com/>
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
