Using API v3 issue

[Joao Ramos]

I'm trying to create a simple REST service using the Create API.

It's a simple scenario, containing a request/response pair, POST, a Body, and a configuration file.

https://<registry host>:1505/lisa-virtualize-invoke/api/v3/vses/VSE/services
Body: Multipart with the zip of the pair and the configuration file.

When the service is successfully created, it is deployed to VSE, but when opening MAR in Workstation, it cannot identify the arguments of the request Body to work with different scenarios.

------------------------------
Regrads,
João Paulo Ramos
------------------------------

Attachment(s)

CommunityCase.zip   2 KB 1 version

[Sankar Natarajan]

HI Ramos
Hope you are doing well and thanks for reaching out to the
community. I tried the artifacts that you have shared and identified the
change that is needed to facilitate identification of arguments.

Please change dataProtocols section of config JSON file as shown below:

"dataProtocols": [
{
"forRequest": true,
"typeId": "JSONDPH"
}

The typeId has been changed from 'RESTDPH' to 'JSONDPH'. With this change,
the arguments are identified accurately from the request JSON. (as shown
below).

Please try and let me know.

[image: image.png]

--
regards
Sankar Natarajan

[Joao Ramos]

Hi Sankar,
Tks for the reply, changing to JSON DPH worked fine. How can I define a META response that's different from the scenario?
Is it possible to make headers more automatic? Calculated at runtime? Such as, for example, date, content length, content type?

-------------------------------------------