Hi Dilshan, We are taking into consideration maintaining MDM and normal push certificates for each tenant. Had a offline discussion with Chathura Dilan and asked him to come up with a UI for it. This will be done by tenant admin and also the Super admin can configure this for the tenants. With regard to implementing it, i.e., use the specific certificate when notifying the device, the iOS jar needs to be changed. Can we have a meeting today after lunch regarding this??
Regards, Nira On Wed, Apr 30, 2014 at 11:46 AM, Dilshan Edirisuriya <[email protected]>wrote: > Hi Chan, > > I think we have to focus more on multitenancy. Right now you have the > point "Fixes to the Policy Component (multiple policy, policy levels, > tenancy)". But other than this there are major areas which needs to be > refactored. Eg: separate app deployment for tenant, maintaining mdm and > normal push certificates for each tenant etc. > > Regards, > > Dilshan > > > On Wed, Apr 30, 2014 at 9:47 AM, Chan <[email protected]> wrote: > >> Hi folks, >> We have been discussing about the EMM 1.1.0 discussion earlier on and I >> sent a mail about it to @architecture before. But I thought of summarizing >> the long email thread :) >> >> The plan is to release EMM 1.1.0 with below improvements and features >> >> - Refactoring the EMM backend >> - Standardizing UI to use Caramel >> - Use the components library (ES team is using) >> - Separate emm_service app that will serve devices (this is for our >> ambitious goal of supporting 50, 000 devices) >> - Fixes to the Policy Component (multiple policy, policy levels, >> tenancy) >> - Removing MySQL dependency (running with H2) >> - Fixing the dependency to the email address >> - Use the refactored ES store and publisher >> - Test cases for EMM server-side >> - Test cases for Android and iOS client apps >> - Converting Jars developed for iOS into OSGi services >> - Fixing product related problems >> - Supporting Multiple User stores >> >> Since what is mentioned above is overwhelmingly big we have made the >> below plan - >> >> Planned release June 1st >> Going to hand over to QA - May 3rd week >> Development - April last week >> >> Task break down - >> >> - *Server* >> - HTTP API (emm & emm_service apps) - All >> - Business Logic layer (Policy and Messaging - emm & emm_service >> apps) - Niranjan and Harshan >> - Carbon refractor - Gayan >> - OAuth - Gayan >> - User Management - Dulitha and Kasun Dissanayake (iOS Kasun) >> - UI - Dilan >> - Enterprise Store Integration - Dilan and Dulitha >> - Unit Test - (Niranjan, Harshan, Kasun Dissanayake, Gayan) [all >> those involved in the Server] >> - Refractor and convert iOS jars to osgi service - Dilshan >> - *Android Client* >> - Performance optimization (checking *memory leaks and etc using >> DDMS*) - Insoh >> - Local notification integration testing - Inosh >> - Testing the new payload structure (implemented by Kasun) once >> the server side is done - Inosh >> - OAuth - Gayan >> - Unit Test - Krishanthi >> - *iOS Client* >> - OAuth - Gayan and Dilshan >> - Unit Test - Harshan >> >> Cheers~ >> >> -- >> Chan (Dulitha Wijewantha) >> Software Engineer - Mobile Development >> WSO2Mobile >> Lean.Enterprise.Mobileware >> * ~Email [email protected] <[email protected]>* >> * ~Mobile +94712112165 <%2B94712112165>* >> * ~Website dulitha.me <http://dulitha.me>* >> * ~Twitter @dulitharw <https://twitter.com/dulitharw>* >> *~Github @dulichan <https://github.com/dulichan>* >> *~SO @chan <http://stackoverflow.com/users/813471/chan>* >> > > > > -- > Dilshan Edirisuriya > Senior Software Engineer - WSO2 > Mob: + 94 777878905 > http://wso2.com/ > -- *Niranjan Karunanandham* Senior Software Engineer - WSO2 Inc. WSO2 Inc.: http://www.wso2.com M: +94 777 749 661 <http:///>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
