Dear all,

I´m looking for some documentation about how to publish a Uniface Service operation (call-in) thru REST API instead regular WebServices.  

Any ideal will be welcome.

Best regards,

Marcelo Martins

Dear all,

I´m looking for some documentation about how to publish a Uniface Service operation (call-in) thru REST API instead regular WebServices.  

Any ideal will be welcome.

Best regards,

Marcelo Martins

Hi Marcelo,

Just a little addendum to Ian answer.

If you want to be compliant with REST, you'll have to know the HTTP method used by client (GET, POST, PUT, DELETE..). There might be another way to get it, but the solution I found is to parse the $webinfo('WebServerContext') and look for the REQUEST_METHOD.

For the router, a simple selectcase will mostly cover it.

Hope it helps

REST services are 'just' webpages. 

So you need to write a USP which can process the input/url called to parse them and perform the required actions/return the required data. 

Here are the top and bottom of our basic API usp 

operation exec
PUBLIC WEB
variables 
	string  v_url ,v_params, v_id, v_data
	struct v_output
endvariables

v_params = $webinfo("input")
v_url = $webinfo("pathinput")

structtojson v_data, v_output
putitem/id $webinfo("HTTPRESPONSEHEADERS"),"Content-Type","application/json; charset=utf-8"

$webinfo("output") = v_data

return(0)

The code in the middle parses v_url for the entity/function required and v_params for the data. 
The response is then built in a struct (v_struct) and transposed to JSON for output by the end of the proc. 

Hope this helps, 

Iain

Iain,

One question: is it possible to receive the parameters  in the same way  I put response (using JSON, in form-data/body) to avoid the params in URL?

Marcelo