IzoT CT and IzoT Net Server - Using the SmartServer IoT iNex Export Tool (KB1430)

The following only applies when you are using SmartServer IoT with a IzoT Net Server Integration tool (like IzoT CT).  If you using DMM for the LON devices you can ignore this Knowledge Base article.

When using a IzoT Net Server database for LON devices, you must first configure the SmartServer for IMM using the CMS Device Widget Action Menu.  After you created your IzoT Net Server database then you need to export the IzoT Server database (all or specific subsystems). 

The SmartServer IoT device has to be at the top of the Subsystem that you want to export.  That is, if the SmartServer IoT is in subsytem "Subsystem 1.Subsytem 2" then you can export only devices in Subsystem 2 and its child subsystems. This allows you to create a single IzoT Net Server database in which you use more than one SmartServer to view device datapoints and each SmartServer only has access to a subset of all devices in the database.  

When you use the iNex tool you need to specify the subsystem that you want to export. All devices in this subsystem and child subsystem are exported to the SmartServer.  This allows you to target just the devices you want see in the SmartServer CMS.  The iNex export tool, available in the "SmartServer IoT Release Notes and Downloads" is a DOS command that needs to be run from a DOS command prompt.

The SmartServer documentation and downloads are available at the following link.  The SmartServer IoT Training Videos also has a "IzoT CT Workflow for SmartServer IoT" that takes you through the process of exporting a IzoT Net Server database to the SmartServer.

http://iecdocs.diasemi.com/

Export Instructions:

1. Create IzoT Net Server database
   • You need to add the SmartServer IoT device for the SmartServer  IP-70 channel
     • Each SmartServer that you want to see devices in its CMS has to its own IP-70 channel and SmartServer IoT device
     • A SmartServer IoT device and IP-70 channel are not needed for SmartServers only used for IP-852 routing.   
2. Import Device Resource File XML files to the CMS Device Type Widget
   • Use the IzoT Resource Editor to create the Resource XML files for the Resource File Set 
   • See "Creating Resource Definitions" in the SmartServer IoT User's Guide
     "Site Planning > Collecting or Creating Device Interface (XIF) Definitions > (Optional) Collecting Device Interface Definitions"
3. Run iNex
   • See "Importing Devices from an IzoT Net Server" in the SmartServer User's Guide "Site Provisioning > Discovering Defining, or Importing Devices" section
4. Access device datapoints in CMS Web pages
   ---------------
5. Make changes to IzoT Net Server
6. Optionally import any new Device Resource File XML files
7. Run iNex again

iNex Format - Run from a DOS prompt ("Window Key + R" then type cmd)

inex /n:"<Network Database Name>" /e:"Target Subsystem"/mqtt://<SmartServer hostname>/<segment ID> /direct:ine

Example 1: Network "network 1" with SmartServer IoT on Subsystem "Subsystem 1"

inex /n:"network 1" /e:"Subsystem 1"/mqtt://10.1.128.83:1883/17q2d7k /direct:ine /verbose

Example 2: Network "school 125" with SmartServer IoT on "Subsystem 1.Subsystem 2"

 inex /n:"school 125" /e:"Subsystem 1.Subsystem 2"/mqtt://10.1.128.83:1883/17q2d7k /direct:ine /verbose