Dear Tali, Thanks a lot for all your help so far. Because of recent changes in the FI-WARE Lab environment (account changes; long-term accounts for accelerator projects only etc), we are having issues to keep the CEP deployed and running at their Lab environment. We need however the CEP running to make our Specific Enabler of FI-STAR project work. Would that be possible for us to have a blueprint or image of the CEP to run in our own infrastructure? Thank you! Best regards, Mikhail. Mikhail Popov Senior Project Manager, PhD Netlab - Networking and Transmission Laboratory [cid:31CA69A7-8746-414F-8ACC-2E5630DC4D3E] Acreo Swedish ICT AB Box 1070, 164 25 Kista, Sweden +46 70 778 77 69 mikhail.popov at acreo.se<mailto:mikhail.popov at acreo.se> www.acreo.se<http://www.acreo.se/> From: Tali Yatzkar-Haham [mailto:TALI at il.ibm.com] …. Yes, you are right. (In both cases you define one event type. At runtime, in your first option you will send 30 event instances, and in your second option you will send one event instance for representing the same information ) Best regards, Tali On Apr 15, 2015, at 6:37 PM, Altug Guner <altugguner90 at gmail.com<mailto:altugguner90 at gmail.com>> wrote: Dear Tali, For point number 3; correct me if I am wrong, if I have 30 readings for heart rate for a patient that I want to send to CEP, I have two options; 1- I will have an event type: e1.patientId and e1.heartRate and will send 30 POST messages 2- I will have an event type e1.patientId,, e1.heartRate1, ... e1.heartRate30 and will send it in POST. Did I understand correctly? Best Regards, Altug -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20150511/1052badf/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 6344 bytes Desc: image001.png URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20150511/1052badf/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy