Registering a ThingPoint in the RAD Server Engine
Go Up to ThingPoint Overview
A ThingPoint is a stand-alone application that can run apart from the RAD Server Engine (it may be running on a different computer).
A ThingPoint implemented with a RAD Server EdgeModule needs to be registered in the RAD Server Engine (EMS Server) to be accessed from an RAD Server Client Application.
A ThingPoint registers the following data in the RAD Server Engine:
- ModuleName. Unique name of the ThingPoint in the RAD Server Engine.
- Protocol. TCP protocol used to connect to the RAD Server Engine.
- Connection properties. Host and port where the ThingPoint service listens for requests from the RAD Server Engine.
- Host. Host where the ThingPoint is running.
- Port. Port where the ThingPoint service listens for requests from the RAD Server Engine.
- Resource Names. Names of the resources that extend the ThingPoint functionality.
The RAD Server Engine uses the following saved data of each ThingPoint:
- ModuleName and Resource Name to identify a REST request from the RAD Server Client application that is targeted to the ThingPoint.
- Connection properties to make REST requests to the ThingPoint.
Registering a ThingPoint in the RAD Server Engine
You can use the following components to register a ThingPoint with RAD Server EdgeModules and its resources in the RAD Server Engine.
Component | Use |
---|---|
TEMSEdgeService |
Use the AutoRegister property set to |
Use the RegisterModule method. |
- Note: The custom resources of the ThingPoint are also registered in the RAD Server Engine.