...
| Excerpt |
|---|
Download the WSO2 IoT Server. | Note |
|---|
If you are running WSO2 IoT Server, stop the server before proceeding to the next step. |
Navigate to the <IOTS_HOME>/wso2/analytics/scripts directory via the terminal and run the following command. This installs the geo extension feature to WSO2 IoT Server. | Code Block |
|---|
mvn clean install -f siddhi-geo-extention-deployer.xml |
Open the <IOTS_HOME>/conf/cdm-config.xml file and enable the GeoLocationConfiguration and PublishLocationResponse configurations. This enables the geo extension feature in WSO2 IoT Server. | Code Block |
|---|
| <GeoLocationConfiguration>
<Enabled>true</Enabled>
</GeoLocationConfiguration>
<OperationAnalyticsConfiguration>
<PublishLocationResponse>true</PublishLocationResponse>
<PublishDeviceInfoResponse>false</PublishDeviceInfoResponse>
<PublishOperationResponse>
<Enabled>false</Enabled>
<Operations>
<!-- Publish specific operation responses -->
<!--
<Operation>BATTERY_LEVEL</Operation>
<Operation>CHECK_LOCK_STATUS</Operation>
-->
<!-- use wildcard '*' to publish all responses -->
<Operation>*</Operation>
</Operations>
</PublishOperationResponse>
</OperationAnalyticsConfiguration> |
Start the WSO2 IoT Server broker, 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 broker.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. 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.
|
|
Enroll devices with WSO2 IoT Server
Follow the steps given below to enroll a device:
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. |
- Access the geofencing map for the device you just enrolled:
- Click theImage Modified icon, and then click Device Management.
- Click view on the device you just enrolled and select the Location tab.
Setting alerts
Geofencing alerts allow users to set pop-up alerts when a device enters or exits the defined geometry boundaries. You can set up the following alerts using the WSO2 IoT Server geo extensions.
...