Versions Compared

Old Version 3

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The device ownership application is a pre-configured application with special privileges to perform tasks, such as monitoring settings, managing settings, and other privileged tasks. In a COPE device use case, the organization will have complete ownership of the device by using this concept. See the subsections given below to fully understand the device ownership concept.

...

  1. Assign the device ownership settings to the service application using one of the following methods.

    Note

    The device ownership settings only work for SDK API levels 21 and above.

    • A command issued through the Android Debug Bridge (adb).

      Expand
      titleClick here for more information.
      Panel
      borderColor#11375B
      bgColor#ffffff
      borderWidth1

      Follow the steps given below to assign the device ownership settings on the WSO2 EMM service application via the adb.

      1. Download and install Android Studio.

        Info

        For more information, see installing Android Studio.

      2. Build the WSO2 EMM Agent application:

        Info

        To build the WSO2 EMM Agent application, Android Studio should have API levels 16 and 2223.

        1. Open Android Studio.
        2. Click SDK Manager.
        3. Click the SDK Platform tab and select the API levels 16 and 2223.
          Example:
        4. Click Apply.

      2. Run the command given below:

        Code Block
        adb shell dpm set-device-owner org.wso2.emm.system.service/.ServiceDeviceAdminReceiver
        Note

        dpm is not supported by SDK API levels below 21.

        Expand
        titleClick here for more information on what happens when you run the adb command

        The Android system creates an XML file in the device's <DEVICE>/data/system directory once you run the command to assign the device ownership settings in the service application as shown in step1.
        The name of the XML will be device_owner and it contains the package name of the service application having the device ownership.

        Example:

        Code Block
        titledevice_owner.xml
        <device-owner package="org.wso2.emm.system.service" name="Your app name" />
        Info

        A non-system application can not modify the XML file that is in the device's <DEVICE>/data/system directory unless it's rooted. Therefore Android guarantees that only the configured application gets the privileged device ownership status.

    • Integrating Android for work. 

      Info

      For more information on how this is done, see the content under Google account method in the Android Developer Guide.

    Panel

    The device ownership settings can also be assigned through a special Near Field Communication (NFC) message. Since this is a new feature, not all Android devices will have it. Therefore, this feature will not be supported by EMM 220.

  2. Reboot or restart your Android device.

    When your Android device restarts or boots up, it will check for the configured device-owner.xml file. If the file exits, the application mentioned in the XML file is assigned the device ownership settings. 

    Note
    titleImportant

    Before restarting your device, make sure that the system service application is installed on the device. Not having the system application on your device can lead to device restarting/rebooting issues, after you have configured it for device ownership.

Integrating the service application with WSO2 EMM

...