Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Modify geo fencing configuration instructions

...

Excerpt

  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 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

  3. 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
    languagexml
    <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>

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

    Expand
    titleClick here for more information.

    Start the WSO2 IoT Server broker profile.

    cd <IOTS_HOME>/bin sh broker.sh
    Panel
    borderColor#11375B
    bgColor#ffffff
    borderWidth2
    Code Block

    1. Start the WSO2 IoT Server core profile.

      Code Block
      cd <IOTS_HOME>/bin
sh iot-server.sh

    2. Next, start the WSO2 IoT Server analytics profile.

      Code Block
      cd <IOTS_HOME>/bin
sh analytics.sh

    3. Access the device management console.

      • For access via HTTPsecured HTTPS: httphttps://<IOTS_HTTPHTTPS_HOST>:9763/devicemgt/ 

        For example: http://localhost:9763/devicemgt/For access via secured HTTP: https

        :

        //

        <IOTS_HTTPS_

        HOST>:9443

        PORT>/devicemgt/ 

      • For example: https://localhost:9443/devicemgt/ 

    4. 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.

    5. 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
    titleDeploying in a multi-tenant environmentAnalytics Artifacts

    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 tenantneeds to be deploy per tenant manually. 

    1. Log in to the device management console using the tenant admin credentials.

    2. Click the button and select Configuration Management > Platform Configurations.

    3. 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.

...