Developing a ThingPoint Application with RAD Server

From RAD Studio
Jump to: navigation, search

Go Up to ThingPoint Overview


You can create a new ThingPoint application that uses a TEMSEdgeService component to listen for requests from the RAD Server Engine, and respond back with the needed data.

You need the following components in your ThingPoint application:

Connecting a ThingPoint Application with the RAD Server Engine

The ThingPoint uses the TEMSProvider component to set up the connection to the RAD Server Engine. Modify the following properties to set up the connection properly.

  • URLHost. The URL of the RAD Server Engine. Use:
    • localhost if the RAD Server Engine is running on the same machine as the ThingPoint.
    • IP Address of the remote RAD Server Engine if it is running on a different machine in which the ThingPoint runs.
  • URLPort. The connection port of the RAD Server Engine.
    • Default value: 8080
  • URLProtocol. The URL protocol identifier for the request to the RAD Server Engine. Possible values are http and https.
    • Default value: http

You may also need to configure the RAD Server Engine Authorization settings needed to connect to the RAD Server Engine (EMS Server).

Listening to Requests from the RAD Server Engine

The ThingPoint uses the TEMSEdgeService component to listen for requests from the RAD Server Engine. Modify the following properties to set up the listening service properly.

  • Provider: TEMSProvider component that identifies connection parameters to the RAD Server Engine.
  • ModuleName: Name identifier for the ThingPoint to uniquely identify it in the RAD Server Engine.
  • ListenerProtocol. The protocol identifier for the request from the RAD Server Engine. Possible values are http and https.
    • Default value: http
  • Connection parameters of the ThingPoint application:
    • ListenerService.Host. Host info where the ThingPoint is running.
      • localhost if the ThingPoint is running on the same machine as the RAD Server Engine.
      • IP Address of the remote ThingPoint if it is running on a different machine in which the RAD Server Engine runs.
    • ListenerService.Port. The connection port in which the ThingPoint application is listening for requests from the RAD Server Engine.

Adding an RAD Server Resource to a ThingPoint

You can also add new RAD Server resources to an existing ThingPoint by adding additional RAD Server modules.

To add a new Resource to a ThingPoint and declare its Endpoints, see Creating a RAD Server Package.

A ThingPoint has a built-in Resource which is called version. For instance, to retrieve version information for a ThingPoint from a browser use:

http://<URLHost>:<URLPort>/edgemodules/<ModuleName>/version

Accessing ThingPoint Resources from a Client Application

You can access any ThingPoint resources from an RAD Server Client Application.

To access a ThingPoint resource, you need to identify it as follows:

edgemodules/<ModuleName>/<ResourceName>

See Also

Retrieved from "http://docwiki.embarcadero.com/RADStudio/Alexandria/e/index.php?title=Developing_a_ThingPoint_Application_with_RAD_Server&oldid=269497"