if I understood your question correctly, you are using "Internet of Things for Neo environment" [1] where you have your IoT Message Type configured and the Device is sending messages to the IoT MMS using that defined format. Now you want to extend your Message Type with an additional field and would like your existing T_IOT_ table also be extended, right?
Yes I'm using IOT to receive message and store it in my an HANA table this part work correctly. But now that I want is, when I receive a new message from my IOT device, publish throught a websocket the new message stored in my table.
Could you please rephrase this sentence "But now that I want is, when I receive a new message from my IOT device, publish throught a websocket the new message stored in my table." in other words please?
so, based on your additional comments above, the use case you describe is: react on incoming messages from the device (new entries in the table) and then do some action (forward new entry via WS).
First part of the use case reminds me some similar threads [1], [2], [3] from the Community archive. Summarizing those ones, you have basically two options:
Make use of HANA Triggers [4] and react on new entries in the DB table.
Configure IoT HTTP Message Processing (Message Forwarding) [5] in addition to the default SQL one, so that your device messages are also forwarded to some arbitrary HTTP endpoint (implemented by you).
As for the second part (forwarding an entry via WS):
In case of HANA Triggers I am not quite sure if XS is able to establish WS connectivity (never tried it myself).
In case of HTTP endpoint, you are free to implement WS connectivity yourself. It is completely on you what to do when you receive the forwarded message from IoT MMS.
I've seen your answer (to use HANA triggers) for this kind of requirement now a couple of time and always wonder how that would actually help to solve the issue.
Sure, when a new record gets inserted into a table, one can call some HANA procedure or change the data, but there is no option to signal the XS/XSA app connected to the HANA instance in this setup.
If I'm following correctly, the only way for the application to notice and react to new records in the table would be to poll the table and look for new entries. Is that correct? Or how else would that work?
when suggesting Triggers those days, I have been pretty much confident that calling XSJS procedures by Triggers was a part of the hands-on session done by Thomas in one of those firsts openSAP "SAP HANA" courses [1] (late 2013). Now, after watching some of the videos, I couldn't find it. Also, this direct answer [2] from Thomas confirms that I was wrong. My fault.
So, the only way would be to poll the table, as you say. Thanks for correction!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.