The CLAMP HTTP participant receives configuration information from the CLAMP runtime, maps the configuration information to a REST URL, and makes a REST call on the URL. Typically the HTTP Participant is used with another participant such as The CLAMP Kubernetes Participant, which brings up the microservice that runs a REST server. Once the microservice is up, the HTTP participant can be used to configure the microservice over its REST interface.Of course, the HTTP participant works towards any REST service, it is not restricted to REST services started by participants.

The HTTP participant runs a Control Loop Element to handle the REST dialogues for a particular application domain. The REST dialogues are whatever REST calls that are required to implement the functionality for the application domain.

Configuring a Control Loop Element on the HTTP participant for an Application Domain

The HTTP participant allows the REST dialogues for an Application Domain to be managed. A particular Application Domain may require many things to be configured and managed and this may require many REST dialogues to achieve.