Setting Up the Work Profile

Prerequisite

You need to have an Android device that supports the Lollipop OS version or upwards.

In WSO2 IoTS, data containerization is implemented using the Managed Profile feature. This is only available for the devices that support the Lollipop OS version or upwards.

Follow the instructions given below to enroll an Android device:

Sign in to the Device Management console.
Click here for more information.
Follow the instructions below to sign into the IoTS device management console:
Start the server.
Access the device management console.
For access via HTTP: http://<HTTP_HOST>:9763/devicemgt/
For example: http://localhost:9763/devicemgt/
For access via secured HTTP:
https://<HTTPS_HOST>:9443/devicemgt/ For example: https://localhost:9443/devicemgt/
Enter the username and password, and sign in.

The system administrator will be able to log in using admin for both the username and password. However, other users will have to first register with IoTS before being able to log into the IoTS device management console. For more information on creating a new account, see Registering with IoTS.
Click LOGIN. The respective device management console will change, based on the permissions assigned to the user.
For example, the device management console for an administrator is as follows:
Click Enroll New Device.
Click Android to enroll your device with WSO2 IoTS.
Enroll the device.
1. Click Enroll Device.
2. Scan the QR code to download the Android agent onto your Android device.
  
  You need to make sure that your Android device and the IoTS server are on the same network, else you will not be able to download the Android agent.
  After scanning the QR code you will be directed to a web page. When this page appears, the web browser will typically display an "insecure connection" message, which requires your confirmation before you can continue.
  
  Click here for more information.
  The WSO2 IoTS consoles are based on the HTTPS protocol, which is a combination of HTTP and SSL protocols. This protocol is generally used to encrypt the traffic from the client to server for security reasons. The certificate it works with is used for encryption only, and does not prove the server identity, so when you try to access these consoles, a warning of untrusted connection is usually displayed. To continue working with this certificate, some steps should be taken to "accept" the certificate before access to the site is permitted. If you are using the Mozilla Firefox browser, this usually occurs only on the first access to the server, after which the certificate is stored in the browser database and marked as trusted. However, with other browsers, the insecure connection warning might be displayed every time you access the server.
  This scenario is suitable for testing purposes, or for running the program on the company's internal networks. If you want to make these consoles available to external users, your organization should obtain a certificate signed by a well-known certificate authority, which verifies that the server actually has the name it is accessed by and that this server belongs to the given organization.
Click Download Android Agent.
Open the downloaded file, and tap INSTALL.
Tap OPEN, once the WSO2 Android Agent is successfully installed.
Tap Setup Work-Profile to proceed with registering the Android device via the Work-Profile.
Tap SET UP.
Tap OK to confirm.
Tap UNINSTALL to uninstall the WSO2 EMM agent you downloaded previously.
Enter the server address based on your environment, in the text box provided. A confirmation message will appear.
- Developer Environment - Enter the server IP as your server address.
  Example: 10.10.10.123:9443
- Deployment Environment - Enter the domain as your server address.
  
  The Android Agent app's default port is 80. If you are using any other port, the server address should state the new port in the following format: www.abc.com :<PORT>
  For example, if the port is 9779 the server IP is as follows: www.abc.com:9779
Tap Yes to continue.
Enter your details and tap Register. A confirmation message will appear.
- Username - Enter the WSO2 IoTS username.
- Password - Enter the WSO2 IoTS password.
- Domain - Enter the domain only if the server is hosted with multi-tenant support.
- Ownership type - Select the corresponding device ownership option. This will customize the device management behavior accordingly.
  - BYOD - Bring your own device.
  - COPE - Corporate owned personally enabled.
Tap Yes to continue.
- If you select BYOD, go to the preceding step - You will be shown a policy agreement, which you can either accept or reject.
  
  You will get access only if you accept the policy agreement.
- If you select COPE, proceed to activate the device administrator - As it's a corporate owned device, you will not be shown a policy agreement. You will have to adhere to the company policy.
Read the tenant policy agreement, and tap Agree to accept the agreement.
Set a PIN code of your choice with a minimum of 4 digits. The PIN code will be used to secure your personal data. Thereby, the IoT server will not be able to carry out critical operations on your personal data without using this PIN.
Example: If the device management admin needs to wipe your device or remove data from the device, he/she can not directly wipe it 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. A confirmation message will appear.

You will be prompted to provide a PIN code only if your device is a BYOD device.
Confirm the PIN and click OK to continue.
Tap ACTIVATE to enable the WSO2 Agent administrator on your device. A confirmation message will appear after enabling the device admin.
You have now successfully registered your Android device. If you wish to unregister the registered device, click Unregister.

Once the registration process is complete, navigate to the launcher of your device. You will see that some applications are duplicated, with one set of the applications having a red icon. These applications are the ones used by WSO2 IoTS.