Dear Alex, Glad to hear you are using the CEP! What you can do: 1. Have one EPA, lets call it EPA1, that uses the temporal context you defined, lets call it TC1, (initiator Event_X, terminated after 24 hours). Make EPA1 of type Aggregate, that uses TC1. Set the evaluation policy of EPA1 to be deferred and don't set it conditions or input event. Make it generate a new type of event (that you need to define), lets call it E2. The purpose of EPA1 is to generate E2 24 hours after Event_X arrives. (If you don't want to have a warning on empty input events you can put Event_X as an input event of EPA1) 2. Now you can define another temporal context, lets call it TC2 that uses E2 as initiator. Hope this is what you wanted. I cc the FIWARE help, so this corresponding will be documented in the FIWARE issue tracking system. Please cc it as well in future correspondence. Thanks. Best regards, Tali Tali Yatzkar Haham Event-based Middleware & Solutions IBM Haifa Research Lab, Israel tali at il.ibm.com 972-4-8296320 From: Theologos Zacharopoulos <alex at konnektid.com> To: Tali Yatzkar-Haham/Haifa/IBM at IBMIL Date: 11/03/2015 04:20 PM Subject: Complex Event Processing, help Dear Tali, I am a Software Engineer who collaborates with the FiWARE GE, I am working on the IBM Proton about 2 weeks now, and I ma trying to configure a use case for the company I work for. I created a temporal context that starts the time that an Event_X is fired and it expires after 24hours, but I want a second temporal context start after 24hours of the event creation, can you please provide me some help on this? I tried to set the condition: Event_x.duration == 86400000, but that didn't work for me. Thanks in advance! Alex Zacharopoulos, Software Engineer @ Konnektid. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20150312/76f5d16d/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy