Excellent stuff! Thanks Pasindu! On Fri, Apr 22, 2016 at 12:22 PM, Pasindu Jayaweera <[email protected]> wrote:
> Hi all, > Implementation of Data containerization for Android BYOD scenario has been > done, except the part of App Managing from AppManager. To implement that > part, it is necessary to get EMM API access by being a partner in Google > EMM Community. Getting Partnership is still on the process and find the > progress from the mail with subject [1]. > I've created a document to explain the current implementation of the > $subject. > > Thanks. > > [1] - Shall we go for EMM Developer community partnership with Google? > > > On Fri, Mar 18, 2016 at 3:28 PM, Pasindu Jayaweera <[email protected]> > wrote: > >> Please find the sketch attached below. >> >> On Fri, Mar 18, 2016 at 3:19 PM, Pasindu Jayaweera <[email protected]> >> wrote: >> >>> Hi all, >>> Let me describe the current progress of the implementation of $subject. >>> Once the agent is downloaded to the device, it is able to detect whether >>> device has the ability to create a work profile (android managed-profile). >>> If so, then it will prompt the user asking for creating the managed profile >>> first. After creating the managed profile and adding the agent to it, the >>> user is again prompted to uninstall the agent in the personal profile since >>> it is no longer used. After those steps, EMM agent in the work-profile >>> starts the enrollment process just as the old agent enrollment. >>> >>> As Kasun mentioned earlier, we will be able to push apps from AppManager >>> to the work profile using Google Play EMM API. We have submitted a request >>> to be registered to 'Android For Work'. Once they review the request we >>> will be given access to the EMM API and we will have to implement Android >>> For Work features in our EMM. Then we will be able to register as an >>> Accepted EMM Partner of Google as well. >>> >>> In the work-profile, the agent is able to do additional operations and >>> the implementations of some previous operations like 'Enterprise Wipe' is >>> also going to be changed. So I'm going change the previous implementation >>> of operations in the agent by creating a separation based on the 'agent >>> version' using Factory Method Pattern. Given below is a sketch of it. >>> Please note that the possible versions to seperate so far as I identified >>> are, >>> >>> 1. Agent for Marshmallow Work-profile Environment >>> 2. Agent for Marshmallow Environment (without a work-profile) >>> 3. Agent for the older versions of Android OS (From Jellybean to >>> Lollipop) >>> >>> >>> >>> >>> Appreciate your feedback on this. >>> >>> Thanks.... >>> >>> On Thu, Mar 3, 2016 at 10:12 AM, Kasun Dananjaya Delgolla < >>> [email protected]> wrote: >>> >>>> HI Milan, >>>> >>>> It's not that App manager will be useless. The suggestion I made is >>>> ONLY applicable for managed profile scenario. App manager integration will >>>> be there as it is for BYOD and COPE. And also google enterprise integration >>>> should also be there as a switchable configuration. The point is, with appM >>>> we can't address app installs on a managed profiles under containerization. >>>> My suggestion was to address that. Also we have another option to have apps >>>> published under play for enterprise and have the same app listed under our >>>> app manager (maybe as a new artifact type or as a play store app (public >>>> app type in the publisher)). Once the installation triggers, we can do it >>>> via their REST API as I described above. We can go for one of these >>>> options. >>>> >>>> Thanks >>>> >>>> On Thu, Mar 3, 2016 at 9:45 AM, Milan Perera <[email protected]> wrote: >>>> >>>>> Hi Kasun/ Pasindu, >>>>> >>>>> >>>>>> IMO we should at least implement support for this so that we can >>>>>> present at least this approach to achieve containerization using managed >>>>>> profiles. >>>>>> >>>>>> But in this case will our app manager integration be become useless ? >>>>> IMO we should write a connector or something to support the REST API >>>>> which is provided by Google Enterprise Play Store so that we would be able >>>>> to publish/install/uninstall >>>>> applications via our AppManager to the Google Enterprise Play Store. >>>>> WDYT? >>>>> >>>>> Regards, >>>>> >>>>> -- >>>>> *Milan Perera *| Software Engineer >>>>> WSO2, Inc | lean. enterprise. middleware. >>>>> #20, Palm Grove, Colombo 03, Sri Lanka >>>>> Mobile: +94 77 309 7088 | Work: +94 11 214 5345 >>>>> Email: [email protected] <[email protected]> | Web: www.wso2.com >>>>> <http://lk.linkedin.com/in/milanharinduperera> >>>>> >>>> >>>> >>>> >>>> -- >>>> Kasun Dananjaya Delgolla >>>> >>>> Software Engineer >>>> WSO2 Inc.; http://wso2.com >>>> lean.enterprise.middleware >>>> Tel: +94 11 214 5345 >>>> Fax: +94 11 2145300 >>>> Mob: + 94 771 771 015 >>>> Blog: http://kddcodingparadise.blogspot.com >>>> Linkedin: *http://lk.linkedin.com/in/kasundananjaya >>>> <http://lk.linkedin.com/in/kasundananjaya>* >>>> >>> >>> >>> >>> -- >>> *Pasindu Upulwan Jayaweera* >>> Software Engineering Intern >>> Mobile: +94 718187375 >>> >>> Blog : pasindudesk.blogspot.com >>> WSO2 Inc: http://wso2.com/ >>> >>> >> >> >> -- >> *Pasindu Upulwan Jayaweera* >> Software Engineering Intern >> Mobile: +94 718187375 >> >> Blog : pasindudesk.blogspot.com >> WSO2 Inc: http://wso2.com/ >> >> > > > -- > *Pasindu Upulwan Jayaweera* > Software Engineering Intern > Mobile: +94 718187375 > > Blog : pasindudesk.blogspot.com > WSO2 Inc: http://wso2.com/ > > -- Prabath Abeysekara Technical Lead WSO2 Inc. Email: [email protected] Mobile: +94774171471
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
