Backend Device Management (IDAS)
For more info about this Chapter, see here.
For more info about this GE, see here.
Why using an IoT Agent?
Transform IoT Device specific protocol to NGSI (a.k.a Active attributes)
Request data from the IoT Device at some intervals (a.k.a Lazy attributes)
Execute commands on the IoT Device communication based on context in the Broker.
Explore the subfolders of each of the available IoT Agent recipes. The Agents can be considered stateless services and hence be deployed in the replicated mode of swarm with any required amount of replicas, provided that you keep your configurations using the service name of the agent for routing purposes.
For good scalability, when deploying the mongo databases that your agents may use in case of persistence need, make sure you deploy with the provided recipe for mongo replica sets. More info here.
If you would like to try the IoT Agents in a local development environment, you can deploy the complementary services (Orion and Mongo) by using their corresponding recipes. See Orion's and Mongo's
If you are following the step-by-step of the official documentation guides,
you may find the scripts in the
test subfolders useful. Remember you no longer
have everything running in local host so you will have to adjust the urls
sometimes. You can use the service names if you are inside the docker network or
the IP of your docker swarm node (any of them) if you are outside the cluster.