Hi Tharindha, With current implementation of iOS enrollment to EMM server, the mentioned profile in step 9 is created on the fly by EMM server when a device enrollment happens with the system.
If I assume that "Assign devices in step 6" means an enrollment of the devices, shouldn't this "Request Profile in step 11" happen as a sub-action of step 6 since it's a pre-requirement for the enrollment? Also as a side note, for improved clarity of this activity diagram, it is better to introduce another swim lane for actor "EMM-admin" and initiate all relevant requests from there. Also, the arrow head of step 4 should be the other way around. Thanks, Dilan. *Dilan U. Ariyaratne* Software Engineer WSO2 Inc. <http://wso2.com/> Mobile: +94725197942 lean . enterprise . middleware On Mon, Feb 8, 2016 at 11:50 AM, Tharinda Ehelepola <[email protected]> wrote: > Hi All, > > *Supervision was introduced by Apple in iOS 5 to differentiate > institutionally-owned iPhones and iPads from personally-owned devices. > Supervision is enabled using Apple Configurator > <http://www.enterpriseios.com/wiki/Apple_Configurator>, Device Enrollment > Program <http://www.enterpriseios.com/wiki/Device_Enrollment_Program> if > purchased directly from Apple.* > > > > *Requirements - WSO2 should be registered in deploy.apple.com > <https://deploy.apple.com/> as a organization- A device is needed which is > directly purchased from apple * > I have design below architecture for the iOS supervision mode enrollment. > > > > Regrads, > Tharinda. > -- > > *Tharinda Ehelepola* > > *Software Engineering Intern* > LinkedIn <https://lk.linkedin.com/in/tharindadilshan> > TP : 94711834769 > Email: [email protected] > Web: tharinda.tk >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
