CODEWITHSUNDEEP
fiwarefiware-orioncomplex-event-processing
A. Vieira
A. Vieira

Reputation: 1281

Interfacing Orion and other GEs from fiware and other APIs

I'm trying to integrate Proton CEP and Mandrill, an email service, mediated by Orion context broker. When I was starting to study Orion, I thought that it would be able to communicate directly with CEP, exchanging JSON objects through http. And also that Orion would be able to parse each object to deliver to the correct format understandable by each API.

From the examples and documentation available I was able to understand that another API developed by us should be doing the parsing and mediating the communications between each API.

So I'd like to confirm that this is so and that I'm not missing something. Is Orion indeed unable to customize its outputs?

If confirmed, then I will proceed with development of this mediating API.

Arthur

Edit: I believe I wasn't clear above about the issue. I hope adding this helps.

Proton CEP recieves through http POST JSON objects, but it only understands the variables if they are in simple format, like {"Name1":"Value1","Name2":"Value2"}, with no arrays or complex struture.

Orion, can comunicate in JSON as well through http, but I can't control the structure of the JSON output. So the result is that CEP wouldn't be able to understand inputs from Orion and process them. The same issue arises with other APIs too. And I'd like to confirm that Orion is indeed unable to custom its output and that this integration needs to be done on our side.

Upvotes: 2

Views: 231

Answers (3)

duxan
duxan

Reputation: 124

You can find best explanation about connection between CEP and Orion in latest guides.

User guide's Appendix A specifies steps to establish such a communication (subscription(s) and/or simple publish).

Upvotes: 1

fgalan
fgalan

Reputation: 12294

The JSON format that Orion Context Broker sends in notification conforms to the NGSI10 context management specification. Using a predefined JSON (instead of a custom one) is the best way to ensure that interoperability with other NGSI-compliant software works.

Before doing the NGSI-to-Proton adaptation piece yourself, I'd recomend you to check with Proton development team if there is any existing NGSI connector to their system that you can reuse. You can find contact details in Proton page at FIWARE catalogue.

Upvotes: 0

kzangeli
kzangeli

Reputation: 448

Orion only understands/returns XML and JSON, and with this it is able to communicate with most of the GEs in FIWARE. I can't tell you anything about the Proton CEP, sorry. To make sure you have interoperability between GEs (and especially other components) a "mediating gateway" will solve the problem, of course.

Upvotes: 1

Related Questions