Hello,
I'm trying to implement Orion context broker with Proton CEP and an external API, Mandrill, to send emails on event detection. Orion would take values from our own API and send them to CEP. On event detection, CEP would send a payload to Orion, who would parse it and direct it to Mandrill and have an email template merged with the variables and sent to the correct client.
While studying Orion http communication, I found that I wasn't able to make it send an http POSTs, using the subscription feature, with the JSON object formated the way each API needs to communicate.
For instance, CEP only takes flat JSONs of the form
{"name":"Report" , "value":"100"}
on a POST request, but Orion's output is a complex JSON. So, CEP isn't able to take inputs directly from Orion because variables in the JSON aren't accessible to it and vice-versa.
Same thing happens with Mandrill API, which does recieve JSON POSTs but with a particular configuration.
So I'd like to confirm that Fiware GEs don't generally have a way of communicating direclty through http and that we need to write some complementary backend code to parse these JSON requests.
Is this the case for other GEs as well? Am I missing something about Orion's http requests?
If you need more information, please let me know.
Thank you
Arthur Vieira
Geratriz, Portugal
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-tech-help
[Created via e-mail received from: Arthur Vieira <arthurmvieira@hotmail.com>]
extRequest
Major