| title | keywords | status | creationdate | lastupdated | description | createdby | updatedby |
|---|---|---|---|---|---|---|---|
How do I? |
help, topics, guides |
inprocess |
20170920 |
20171105 |
Gives a set of questions and answers how to do specific tasks |
bytemaster-0xff |
bytemaster-0xff |
A great place to get started is our getting started guide.
We have a number of support options including documentation, an online forum as well as a ticketing system. If none of those options work for you please contact us.
Please contact us to be put in touch with an implementation partner.
Applications built with NuvIoT are managed and hosted on a number of trusted cloud providers, deploying and hosting your application is automated as part of the system. If you need to host your application, please contact us to discuss options to install our NuvIoT runtime on your servers.
The entry point for data into the system is a Listener. You define how your listener works and the listener monitors a port, protocol or external source for incoming messages.
You will create a listener that will listen on a port, protocol or connect to an external messaging queing source that will accept incoming messages.
You will need to pass an unique identifer as part of your message. As part of building your application, you will create a device id parser that will identify what part and how the device id should be extracted from your incoming messaage.
In some case you will only have one type of message that you are listening for, if you have multiple message types you will need to establish a message id and send that within your messagae. Once you have your message id you will need to add a messag id parser that will identify what part and how the message id should be extracted from your incoming messaage.
Once you create your message definition you will have added a number of fields that you expect in your message. Those fields are automatically stored from each message. In addition you can create attributes of your device that store the most current value that was received in a message.
After the planner identifies the message id it will use the device configuration to select a route which will specify the pipeline modules that will be used to process your message.
You build up a message definition. The message definition contains all the fields that make up your message. Once a message has been identified by the message id the values of your message will be extracted and can be used in your workflow.
Check out our overview to get an idea of what's involved with building your application.
After you deploy your application, we povide a simulator to create messages you can send to your application.
Devices are stored in device repositories, after you create your repository you can add them through our IoT App Studio in the Device Repositories section or you can add them with our mobile app. If you have a large number of devices you need to add, please contact us to help you import your devices.
Security is very critical part of any IoT platform. We have a sentinel module that every message must pass through before we use any data that is passed in to our system.
We provide a sophisticated workflow engine where you can visualy configure how your messaages are processed, we also provide a state machine engine to build state dependent behavior. In addition we provide a javascript editor to build scripts.
There are three primary strategies with integrating with other systems, the first is to listen for incoming messages on a port, protocol or external messaging system with a listener. The second is to send messages to an end point or service from an output command in your workflow with a transmitter. The final way is to expose an input command as a REST service from within your workflow.