Page Comparison

Location-based services (LBS) uses real-time location or geo-data from devices to monitor and track devices. The geo extension in WSO2 IoT Server provides real-time information about geospatial objects. It processes spatial data from an external source of events and analyzes/manipulates this data to produce meaningful information to end users. You can interact with it to generate a variety of alerts and warnings. 

The following sections guide you through installing the geo extension, using geofencing, and setting up alerts. 

...

1. Download the WSO2 IoT Server.

   Note
   If you are running WSO2 IoT Server, stop the server before proceeding to the next step.

2. Navigate to the <IOTS_HOME>/wso2/analytics/scripts directory and run the following command. This installs thegeo the geo extension feature to WSO2 IoT Server.

   Code Block
   mvn clean install -f siddhi-geo-extention-deployer.xml

3. Open the cdm-config.xml file found in the <IOTS_HOME>/conf folder and set the following properties under the <GeoLocationConfiguration> tag to true. 
   This enables thegeo the geo extension feature in WSO2 IoT Server.

   Code Block
   <GeoLocationConfiguration> <isEnabled>true</isEnabled> <PublishLocationOperationResponse>true</PublishLocationOperationResponse> </GeoLocationConfiguration>

4. Start the WSO2 IoT Server core and analytics profiles and sign in to the WSO2 IoT Server Device Management Console.

   Expand
   title Click here for more information.
   Panel borderColor #11375B bgColor #ffffff borderWidth 2 Start the WSO2 IoT Server broker profile. Code Block cd <IOTS_HOME>/bin sh iot-serverbroker.sh Start the WSO2 IoT Server core profile. Code Block cd <IOTS_HOME>/bin sh iot-server.sh Next, start the WSO2 IoT Server analytics profile. Code Block cd <IOTS_HOME>/bin sh analytics.sh Access the device management console. For access via HTTP: http://<IOTS_HTTP_HOST>:9763/devicemgt/  For example: http://localhost:9763/devicemgt/ For access via secured HTTP: https://<IOTS_HTTPS_HOST>:9443/devicemgt/  For example: https://localhost:9443/devicemgt/  Enter the username and password, and sign in. Info 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 WSO2 IoT Server before being able to log into the IoT Server device management console. For more information on creating a new account, see Registering with WSO2 IoT Server. 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:

   Tip
   title Deploying in a multi-tenant environment
   The geo analytics artifacts are deployed by default in the WSO2 IoT Server super tenant. However, if you are setting up geofencing in a multi-tenant environment, you have to deploy the geo analytics artifacts in each tenant.  Log in to the device management console using the tenant credentials. Click the button and select Configuration Management > Platform Configurations. Click the Deploy Geo Analytics Artifacts button. If required, you can use this button to re-deploy the geo analytics artifacts in the super tenant mode.

5. Enroll a device. Let's enroll an Android device for this tutorial.

   Info
   For more information on how to enroll an Android device, see Android. For more information on how to enroll other sample device types, see Enrolling Devices.

6. Access the geofencing map for the device you just enrolled:
   1. Click the  icon, and then click Device Management.
   2. Click view on the device you just enrolled and select the Location tab. 

...