Note that, in the response, the field "contextId" indicate the identifier to be used to [terminate the instance](#terminate-an-existing-instance-of-onboarded-mec-application).
Note that, in the response:
- The field "contextId" indicates the identifier to be used to [terminate the instance](#terminate-an-existing-instance-of-onboarded-mec-application),
- The field "referenceURI" indicates the URL to the new instance of the onboarded MEC application, see clause [Ping request](#ping-request]).
#### Ping request
The requets `GET /dai/doping` is the ping/pong request.
The requets `GET /onboarded-demo4/ping/{appcontextid}` is the ping/pong request to send to the instance of the onboarded MEC application [onboarded-demo4](#onboarded-demo4).
The requets `POST /dai/availability/{appcontextid}` provides the location availability for the specified instance of the onboarded MEC application.
```sh
$ curl -X POST "http://mec-platform.etsi.org:31111/dai/availability/20"-H"accept: application/json"
```
### onboarded-demo4
The MEC application onboarded-demo4 is a basic HTTP REST API "Ping/Pong" application. When it recieves an HTTP GET /ping request, it replies with 200 OK "pong".
@@ -122,9 +132,9 @@ The goal of thos application is just to validate the support of MEC-016 Service
## Using Demo4
### Preamble
### Preamble (reserved to MEC Sandbox administrator)
Before to use Demo4, you have to copy the file ~/AdvantDEGE/examples/demo4-ue/src/onboarded-demo4.yaml into the folder /var/lib/docker/volumes/meep-dai/_data/ (required to use sudo command)
Before to use Demo4, the file ~/AdvantDEGE/examples/demo4-ue/src/onboarded-demo4.yaml shall be cpopied into the folder /var/lib/docker/volumes/meep-dai/_data/ (required to use sudo command). This is the descriptor of the onboarded MEC application [onboarded-demo4](#onboarded-demo4).