Connecting the Asset Gateway to the deviceWISE Cloud

At this point, you should have a connection from your Asset Gateway to the Internet. This could be over a cellular connection or an Ethernet connection, or both. The final task is to connect it to the deviceWISE Cloud. To connect to an deviceWISE Cloud, you must configure a TR50 connection. You will need to use the application token from your account in the Management Portal to complete your TR50 connection from a module.  To connect the asset gateway to the IoT Portal, do the following:

1. Click on the Developer and note the address of the API server that you should use (For example, api.devicewise.com in the screenshot below).

   The links shown in the figure below vary depending on the instance of the portal you are using.

   

2. Under the GENERAL group, click Applications
   

   An application in this context is an item that is used to assign roles, license information and access control rights. The application is assigned an application token that is then referenced by a gateway or by an external application when connecting to the IoT Portal.
   Your organization may have an application already defined to use for Asset Gateways.

   The Applications page appears.
   

3. Click the New Application button.
   
   
   
4. Enter the following details:
   
   
   1. Enter a name and description
   2. Select Default for the Auto Registration Thing Definition ID
   3. Check the Org Admin option
   4. Set the License field to Industrial Asset Gateway (Evaluation).
      
5. Click the Add button to add the new application.
   
6. The new application is displayed on the Applications page. Copy the new Asset Gateway Application's Token string value to your clipboard.
   
   
7. From the Workbench left pane, expand the appropriate Asset Gateway node.
   

8. Click on TR50, and then select the TR50 Management tab: 
   
   Select the Connection Management tab where you can view status information and configure your connection to the deviceWISE Cloud.
   The tab provides various information about the state of the connection, the amount of data used, and the latency of the connection.
   

   Reference	Parameter	Description
   a	State Status Connect Time Traffic Sent Traffic Received Latency	Information about the state and status of the TR50 connection and the network traffic between the Asset Gateway and the M2M Service.
   b	TR50 Server Address	This is the Endpoint URL for MQTT copied from the Management Portal -> Application page. Unless you are told differently, you can leave the TR50 Server Address set to api.devicewise.com.
   c	Connection Type	Select MQTT with SSL. Note: SSL connections require SSLv3 or TLS1+.
   d	Proxy Type	If you are connecting to a wired network and you need to go through an HTTP, SOCKS4, SOCKS4A, or SOCKS5 proxy, configure the proxy using the Proxy Type parameter.You will need to contact your IT department if you are not sure about the URL or access credentials for your proxy. If you are using a cellular connection, you can ignore this parameter.
   e	Thing Key	This is an deviceWISE Cloud-wide unique hardware ID for this gateway. The Thing Key selection list options include values that are valid for this gateway, and may include the: MAC address of the gateway's Ethernet port Serial number of the gateway International Mobile Station Equipment Identity (IMEI) number of the gateway's cellular modem. The hardware ID must be unique for all gateways connected to the same deviceWISE Cloud. It is used in the deviceWISE Cloud registration process and must match the gateway's definition specified in the Management Portal
   f	Application Token	Paste in the Default Application Token string copied from the Management Portal Applications page.
   g	Organization Key and Open Server	Information about the organization and deviceWISE Cloud for a started connection.

9. Select Save to save your settings.
   
10. Select Start to establish the TR50 connection to the deviceWISE Cloud.