1 of 1 people found this helpful
It supports remote calls that are abstracted by procedures. The meaning of the remote call is up to you. When performing a rest/http operation you can specifying an update verb PUT/DELETE.
I would try it out and get back. In the meantime, if there are any examples/tutorials out there - they would help - I know I am being too greedy here- but a little speed gainer would be good to have.
Can you be more specific as to your scenario, what type of service (rest, soap, general http) are you invoking? What operation are you trying to do? And do you have a payload?
From the example you already have above, the base level ws call for rest/http is invokeHttp:
EXEC MySourceModel.invokeHttp('GET', null, VARIABLES.qp, 'TRUE') - See more at: https://developer.jboss.org/wiki/HowToConsumeAJSONRESTWebServiceInTeiidDesigner#sthash.W2WDjuTq.dpuf
The first argument indicates a GET is being performed, which can be changed depending upon whatever you would need.
Thanks again for quick response,
I am trying to expose a rest service through the teiid-embedded. The another cause of concern is the custom authentication mechanism of the rest service - it provides urls to the actual service post authentication. So are there any extendible plug-points in the teiid ws-translator where I can just add some custom code to get this working?
> So are there any extendible plug-points in the teiid ws-translator where I can just add some custom code to get this working?
The current design of the ws translator / resource adapter is strictly for request / response scenarios. If you need a stateful connection with a custom authentication scheme, then you may need a custom translator and/or resource adapter. I don't think there will be sufficient hooks to do that as an extension. See the salesforce translator for something that behaves similarly - the login result includes the url of the actual endpoint. Then the SalesforceConnection will associate the session id with all subsequent usage of the connection and allows for multi-step processing such as batched results or bulk inserts.