Page Comparison

Let's take a look at the tasks that Chris (the IoT team administrator) and Alex (the device owner) have to do, from downloading WSO2 IoT Server to registering the Android device.

...

1. Download the WSO2 IoT Server sample pack.

2. Create a directory named samples in the <IoT_HOME>/core directory and copy the downloaded file to it.

3.  Navigate to the samples directory and run the command given below to copy the required content to the quick start guide setup.

   Code Block
   cd <IoT_HOME>/core/samples/mobile-qsg sh copy-files.sh

4. Start WSO2 IoT Server.
   If you started WSO2 IoT Server previously, stop the core and analytics profiles using CRTL+C, and restart the two profiles in the given order.
   Restart the servers using the following command:

   Code Block
   ./wso2server.sh

5. Run the mobile-qsg.sh script.

   Code Block
   sh mobile-qsg.sh

   Note
   If you haven't configured WSO2 IoTS for iOS, the iOS sample policy will not be created. Therefore, you will get the message given below. This will not restrict you from trying out the Android quick start guide. Code Block Unable to create the ios passcode policy. Terminating the IoTS QSG now.

...

1. Access the WSO2 IoT Server console by navigating to https://<IoT_HOST>:9443/devicemgt .

   Tip
   title Tip by Chris
   By default, <IoT_PORT> has been set to 9443 for HTTPS and 9763 for HTTP. Since we access the IoT console over HTTPS, use 9443 in the URL. When the pages appear, the web browser will typically display an "insecure connection" message, which requires your confirmation before you can continue. Expand title 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, you must "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 the 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.

   

   1. Enter chris as the username and chrisadmin as the password.

   2. Click LOG IN. 

   The device management dashboard appears, giving you easy access to the devices, users, and policies in your organization. 

2. Click View under POLICIES.
3. Click the edit logo that is on the passcode policy for Android devices.

4. Update the passcode profile that is already in place by defining the maximum fail attempts as 4, and click CONTINUE.

   Info
   A profile in the context of EMM IoTs refers to a collection of policies. If you want to know more about each policy setting, hover your mouse pointer over the help tip. Example:

   

5. The passcode policy that was created for this scenario has the following groups assigned. You can optionally update the groups.
   1. Chris has selected the set user role/s option and then selected the iotMobileUser role from the item list.

   2. Chris has selected Enforce as the action that needs to be carried out when a device has not complied with a policy.  

      Info
      The following actions are referred to as non-compliance rules and determine how policies are monitored.

      Non-compliance rules	Description
      Enforce	Forcefully enforce the policies on the assigned groups.
      Warning	If the assigned groups do not adhere to the given policies, a warning message will be sent.
      Monitor	If the assigned groups do not adhere to the given policies, the server is notified of the violation without notifying the user, and the administrator can take the necessary actions.

   3. Click CONTINUE.

6. Optionally, you can update the name and the description of the policy.

7. Click SAVE to save the configured profile or click SAVE & PUBLISH to save and publish the configured profile as an active policy to the database. It is mandatory that the policy is assigned to Alex's mobile device, so Chris clicks SAVE & PUBLISH to make the policy active immediately when the device enrolls with WSO2 IoTS.

   Info

   If you SAVE the configured profile, it will be in the inactive state and will not be applied to any devices. If you SAVE & PUBLISH the configured profile of policies, it will be in the active state. The active policies will be enforced on new devices that enroll with EMM IoTs based on the policy enforcement criteria. If you want to push this policy to the existing devices and want this policy to be applied to the devices, click APPLY CHANGES TO DEVICES.

...

1. Sign in to the WSO2 IoT Server device management console using alex as the username and alexuser as the password.

2. Click Enroll New Device.
3. Click Android to enroll your device with WSO2 IoTS.
4. Enroll the device.
   1. Click Enroll Device.

   2. Scan the QR code to download the Android agent onto your Android device.

      Info
      Make sure that your Android device and the IoT 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.

      Info

      Expand title 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.

5. Alex taps Download IoT Server Agent on this screen.
   

6. Open the downloaded file, and tap INSTALL.
   
7. Tap OPEN, once the WSO2 Agent is successfully installed.
   

8. Tap Skip and go to Enrollment, which will direct you to install the device with WSO2 IoT Server in the default manner.

   Tip
   title Tip by Chris
   In WSO2 IoT Server, data containerization is implemented using the Managed Profile feature. For more information on how to set up the Work-Profile, see Setting Up the Work Profile.

9. Enter the server IP and the port as your server address in the text box provided.

   Example: Register the device via HTTP: 10.10.10.253:8280

   

10. Tap Yes to continue.
    
11. Enter your details and tap Register. A confirmation message will appear..
    
    • Username - Enter alex as the username.
    • Password - Enter alexuser as the password.
    • Domain Domain - In this example Alex leaves the the Domain empty empty, as it is only required if the server is hosted with multi-tenant support. 
      
    • Username - Enter alex as the username.
    • Password - Enter alexuser as the password.
    • Ownership type - Selects the BYOD ownership option. 
    
12. Tap Yes to continue.
    
13. Read the policy agreement, and tap Agree to accept the agreement. 

14. Tap ALLOW to allow the WSO2 Android agent to make and manage phone calls, and to access photos, media, files, and the device location.

    Note
    You will get this message only if your device is on Android OS Marshmallow (6.0) or above.

    Example:

    

15. Alex sets a PIN code with a minimum of four digits and clicks Set PIN Code. The PIN code is used to secure your personal data. Therefore, the IoT server will not be able to carry out critical operations on your personal data without using this PIN. 
    Example: If Chris needs to enterprise-wipe Alex's device or remove data from the device, Chris cannot directly wipe it without the PIN code. 

    Info
    You will be prompted to provide a PIN code only if your device is a BYOD device.

    

16. Confirm the PIN and click OK to continue.
    

17. Anchor
    Step8 Step8

    Tap ACTIVATE to enable the EMM IoTs device administrator on your device. A confirmation message will appear after enabling the device admin.
    
    Alex's device is now successfully registered with WSO2 IoT Server. Alex can click Unregister to unregister this device.
    

...

1. Access the IoTs device management console using alex as the username and alexuser as the password that was sent via email.
2. Click View under DEVICES.
   

3. Click on the registered device.
   
   Alex tries out the various device operations via the WSO2 IoT Server console.
   Image Removed Image Added

   1. Alex misplaces the mobile device, so Alex clicks Ring to ring the device and find out if the device is lying around the workspace.

   2. Alex then remembers that the phone was unlocked, so Alex uses the Device Lock operation to lock the device so that the content in the device will be safe.

   3. Using the Location operations Alex finds out that device is in Chris's office. Alex calls Chris and asks Chris to call back from the device.

   4. To make sure Chris can call using the device, Alex removes the device lock (password) using the Clear Password operation.

   Info
   For more information on the available features, try out the Android operations.

...

1. Navigate to the App Store using the following URL:  https://<IoT_HOST>:9443/store


2. Sign in using alex and alexuser as the username and password.

3. Click the Catalog mobile application, and click Install.
   

4. Select Instant install, and click Yes.
   
5. Click on your device in the pop-up menu to install and subscribe to the application.
   A success message will be shown when you have successfully subscribed to the application.
6. Tap Install on your device to finish installing the application.
   
   Now you can use start using the application. For more information, see Downloading Applications via the App Catalog Application.

What's next?

• Take a look at the screencast showcasing the WSO2 IoT Server functionality.
• Want to know more about what you can do by enrolling an Android device with WSO2 IoT Server? For more information, see Working with Android.