Hi Gayan, +1. I have implemented Reboot, Shell command execution, firmware upgrade and app silent push/removal on the android layer (with the system app). Also the calling points to the system app in the agent operation manager as well. So once you have added these new operation to the back-end plugin layer + jaggery UI, we can test the end-to-end scenario. Also we have to decide how these new features should be presented to the user in the EMM jaggery app. The reason is, not every device in the device listing view is capable of all these operations. So we should implement a logic to filter out COPE devices with the system app installed. One way to achieve it is, having a config entry in android platform configuration (to track the system app installation to COPE devices).
Thanks On Wed, Feb 10, 2016 at 12:57 PM, Gayan Yalpathwala <[email protected]> wrote: > Hi, > > I have implemented the above in the emm jaggery app and also in the REST > Api layer. I will be further testing the end to end flow on a rooted device > with KasunD. Meanwhile, I will start adding operations for executing remote > shell commands and firmware upgrade. > > Thanks, > > On Tue, Feb 2, 2016 at 2:57 PM, Kasun Dananjaya Delgolla <[email protected]> > wrote: > >> Hi Gayan, >> >> EMM system service app has an Intent Service implemented, >> "EMMSystemService" you can invoke this service with the operation code as a >> parameter. I will document this and share with you guys ASAP. I have >> already implemented the agent side code to invoke this service as well. So >> you can just focus on the server side of it which is adding a new operation >> and the jaggery layer aspect of it. >> >> Thanks >> On Feb 2, 2016 12:23 PM, "Gayan Yalpathwala" <[email protected]> wrote: >> >>> Hi, >>> >>> I am in the process of implementing the device reboot support for EMM. >>> This feature will be available for allowed EMM user roles to restart the >>> device remotely. There will be an operation added to the device view of the >>> console. >>> >>> In case of Android, the agent application will need to communicate to >>> the system app to trigger the reboot. >>> @Kasun, Can you please let me how this communication layer is >>> implemented? >>> >>> 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/> >>> >> > > > -- > *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/> > -- 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>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
