com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.

Setting Up the Work Profile

A work profile creates a containerized environment in a BYOD device to run corporate data and applications. This enables device admins to take control of the corporate data and applications running on the device without preventing the device owner from using the primary profile functionality.

Before you begin

  • Make sure to have an Android device that supports the Lollipop version or upwards.

    WSO2 IoT Server implements data containerization using the Android Managed Profile feature, which is only available on Android Lollipop OS version and above.

  • Do you have work profile that is already running on your device? If yes, on your device, go to Settings > Accounts and remove it. Else, you run into errors.

  • Start the WSO2 IoT Server core profile.

    cd <IoT_HOME>/bin sh iot-server.sh
  • Download the Android agent.

     Click here for more information.

    Follow the steps given below to get the Android Agent. 

Follow the instructions given below to set up the Android work profile:

  1. Tap INSTALL to start installing the Android agent.

  2. Tap OPEN, once the WSO2 Android Agent is successfully installed.

  3. Tap SETUP WORK-PROFILE to proceed with registering the Android device via the Work-Profile.

  4. Tap SET UP.

    If your device was not encrypted previously, you will be prompted to encrypt the device.

  5. Enter the server address based on your environment, in the text box provided and tap START REGISTRATION. A confirmation message appears.

    • Developer Environment - Enter the server IP as your server address.
      Example: 10.10.10.123:8280
    • Deployment Environment - Enter the domain as your server address.

      The Android Agent app's default port is 8280. If you are using any other port, the server address should state the new port in the following format: www.abc.com:<PORT>, e.g., if the port is 8289 the server IP is as follows: www.abc.com:8289.

  6. Enter your details and tap SIGN IN.
    • Organization - Enter the organization name only if the server is hosted with multi-tenant support or enter the default carbon.super, which is the default organization name on a non-multi-tenant environment.
    • Username - Enter the WSO2 IoTS username.
    • Password - Enter the WSO2 IoTS password.

    Read the policy agreement, and tap AGREE to accept the agreement.  
  7. Tap ALLOW to allow the WSO2 Android agent to access photos, media, and files, make and manage phone calls, and access the device location respectively.

  8. Set a PIN code of your choice with a minimum of 4 digits. A confirmation message appears.

    You will be prompted to provide a PIN code only if your device is a BYOD device. The PIN code will be used to secure your personal data. Thereby, WSO2 IoT server will not be able to carry out critical operations on your personal data without using this PIN. 

    Example: A device management admin cannot wipe your device or remove data from the device without the PIN code. You have to provide the PIN code to get your device wiped or you can log into the device management console and wipe your device by entering the PIN code.

  9. You have now successfully registered your Android device. Tap Device Information to get device specific information, and tap Unregister if you wish to unregister your device from WSO2 IoT Server.


Once the registration process is complete, navigate to the launcher of your device. Notice the duplication of application icons. The applications with red icons are the ones used by WSO2 IoT Server.

To deactivate Android Work Profile:

  1. Navigate to Settings > Accounts on your device.
  2. Click Remove work profile.
  3. Tap DELETE and proceed with the deactivation.

    Once the deactivation is complete, navigate to the launcher of the device. Notice the disappearance of the applications with red icons.



com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.