Mobius services are the engines which drive MobiusFlow. Each service is essentially a microservice performing a specific task and possibly acting as an interface to a piece of hardware or a 3rd party service such as Microsoft's Azure platform or the IBM Cloud.
In addition to task specific logic, services can instantiate and manage Mobius objects. These Mobius objects typically mirror real world devices such as sensors and actuators.
Each service within a Mobius node is given a unique ID. This is a three digit hex number which forms the second part of the Mobius URI hierarchy. When referencing a service, for example during a discovery process, this unique ID must be used (see MobiusFlow Uniform Resource Identifiers). For more information read the MobiusFlow Architecture section of this documentation.
Services are created on the Mobius configuration page by dragging a service from the Service Palette onto the Configuration Tree. Once a service has been added to the Configuration Tree it can be configured by selecting it in the tree, which displays the service's configuration page.
To understand more about configuring services, select a service from the Services list on the left of this page.