Provisioning

Following the procurement of the IoT Gateway device hardware and the setup of the Cloud connection, the next step is to provision the IoT Gateway hardware itself.

 

Typically, a new IoT Gateway device does not yet contain an Azure SQL Database (and therefore no configuration databases). In addition, the box itself does not yet know how to communicate with anything. It needs to be provisioned to tell it how to communicate with the Cloud and the Azure IoT Hub.

 

Provisioning Setup

 

Via an included Local User Interface, a user can enter:

The Gateway will then communicate with IoT.Iconics.com, which is a global service that will register the Gateway within the IoT Hub. The IoT Hub must have a registered Gateway in order to initiate communication.

 

IoT.Iconics.com sets up:

How to Provision IoTWorX

Connecting to the IoT Gateway (the hardware itself) and accessing the provisioning settings for IoTWorX is similar to how to connect to and configure a home WiFi router.

  1. On either the gateway or a remote PC on the same network as the gateway, open a Web Browser and go to http://<gateway>:1447/, replacing “<gateway>” with the computer name or IP address of the gateway device.

IoTWorX Login Page

  1. Log in with the credentials:

Username: admin

Password: iconics

 

You can alternatively enter "user" as the Username, as well.

 

You'll be able to change the login credentials later on.

Overview

ICONICS IoTWorX - Overview Page

  1. IoTWorX will open to the Home/ Overview tab, which includes the following Device Information:

Device Set Up

  1. Click on the Provisioning tab pulldown menu and select "Device Set Up".

NOTE: The Provisioning tab also allows you to go straight to the Cloud License and Device Location settings by themselves.

 

Provisioning Tab in IoTWorX

 

You are asked, "How would you like to provision your device?" and have the option of:

In this example, we will connect to an IoT Hub on Azure, so click on the top selection and then Next.

  1. You will then be asked to "Please, select an option that fits your needs.", as shown below.

Hub Options in IoTWorX

 

You can select from:

In this example, we have an existing IoT Hub but need to register a device, so click on the top selection, then Next.

  1. You will then be asked to "Please, enter the information required for the provisioning of the IoT Gateway." as shown below.

Licensing, IoT Hub and Database Settings for IoTWorX

 

IoT Hub

Database

Cloud License

 

If the cloud license pool is not set, then the IoT Gateway will run in demo mode only.

IoT Gateway Device Details and Location

 

Providing details in this section is optional, but it may help in troubleshooting potential problems.

Once you have completed your settings, click on the Provision device button.

 

Several processes take place at this point. The IoT Gateway with the Device name that you provided will be created and registered on your specified IoT Hub (in this case, on the Azure Portal). Once the device is registered there, you will get the Connection String for the IoT Gateway. This Connection String is unique so each device name also has to be unique in the IoT Hub (on the Azure Portal). The Connection String will be used in the Publisher to be able to publish data from the device to the IoT Hub. The Connection String to the SQL Azure database will be used to create default configuration databases for use with Modbus, BACnet, SNMP, and publish lists on the SQL Azure database.

  1. Once these processes are complete, you will see a message that your device has been provisioned.

Click on the Overview tab, and you will see that your set device name now appears in the IoT Hub Device ID section.

 

If you return to the Azure Portal, you can then see that your provisioned IoT Gateway has been added to your listed devices, as shown below.

 

IoT Gateway Device Listed in Azure Portal's Device Explorer

 

See Also:

IoT Gateway Setup

Procurement

Cloud Setup

Overview

Diagnostics

Communicator

Collector

Visualizer

IoT Gateway Configuration in Workbench