Hi all, "Third" module responsibility of conversion - this could be done by implementing specific input and output adapters of our CEP engine These adapters support JMS meaning we can subscribe to a topic or listen to a queue for incoming events and we can publish to a topic or send to a queue outgoing events \ complex events. These adapters also support REST as clients. Meaning we can REST GET events from a RESTfull service as incoming events to CEP and we can REST POST events to a RESTfull service as outgoing \ complex events Regards, Guy Sharon Manager, Event-based Middleware & Solutions Group IBM Research - Haifa Phone: 972-4-8296587 | Mobile: 972-54-6976417 E-mail: GUYSH at il.ibm.com Website: www.research.ibm.com/haifa/dept/services/soms_ebs.html Find me on: and within IBM on: Haifa University, Mount Carmel Haifa, HA 31905 Israel From: Moltchanov Boris <boris.moltchanov at telecomitalia.it> To: Juanjo Hierro <jhierro at tid.es> Cc: "fiware-data at lists.fi-ware.eu" <fiware-data at lists.fi-ware.eu> Date: 29/02/2012 20:04 Subject: Re: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE Sent by: fiware-data-bounces at lists.fi-ware.eu Hi Juanjo, Ok. Got your point and never used it differently. Sorry if sometimes seemed differently. I would confirm that the PubSub based on the context broker is unable to handle any request without an valuated entityID notation. Thus, as stated from very beginning and discussed with Guy and as you suggested (after conversation with Carlo during the last f2f) we have to comply with the context data structure (Within the vision document). Otherwise the query, subscription and entity resolution all based on the context broker will not work (confirmation from Telecom Italia developers). Therefore regarding the third point (Event Objects) of your email below the PubSub shall receive EventsObjects, and then eventually republishing them to the consumers, with an entityID and will provide to anyone CEP included the context data elements with entityIDs. You have suggested, if I?m not wrong, to put this enityID either fixed or fixed but configurable. I suggest, as discussed with Guy and tried to explain in the call, that we derive the entityID from the EO?s attributes if there is at least one. If there is no one a fixed entityID such as entityID=CEP shall be introduces. And viceversa an entityID coming from the PubSub into the CEP might be ?encoded? into the EO?s entity attribute element. However both such conversions are out of scope of the current components and shall be performed by a ?third? module that will accomplish an EO into the context element (EO(event,opt.entityID) -> context(entityID, scope=event) and viceversa will rebuild an EO from a context element (context(entityID,scope)->EO(scope+attr.entityID)). Moreover, the same ?third? module could perform subscription to the PubSub for the events/scopes that the CEP needs to derive the EO, as far as, if I remember well, the CEP is unable to perform the subscription and shall be feeded (pushed) by the events or contexts_as_events, Guy confirm? And the PubSub does not perform subscription on itself, but on behalf of a consumer. There may be no explicit specific consumer for feeding the CEP, thus this subscription task to the PubSub on behalf of the CEP will be taken by this ?third? component. Let?s have a closer look to this proposed architectural/functional vision in tomorrow AC. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [ mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Tuesday, February 28, 2012 1:19 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE Hi Boris, PLEASE, while making your proposal for the solution on how to map concepts between the Pub/Sub Broker GE and CEP pleas DO FOLLOW the terms and definitions proposed in the FI-WARE Product Vision: "Context Elements" (which certainly map to the concepts defined in OMA) "Data Elements" (= Context Elements but without EntityId) "Event Objects": the programming structure that will be used by the CEP into which Context Elements and Data Elements should be mapped. Let's try to avoid the term "Event" which may introduce confusion and doesn't add to much the technical discussion which is indeed about how to map between the data structures listed above (the term Event can be used but should then be under the definition provided in the FI-WARE Product Vision). Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non è necessario. _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20120229/0f6c2bf0/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 518 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20120229/0f6c2bf0/attachment.jpe> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 467 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20120229/0f6c2bf0/attachment-0001.jpe> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 494 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20120229/0f6c2bf0/attachment-0002.jpe> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 360 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20120229/0f6c2bf0/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20120229/0f6c2bf0/attachment-0001.gif>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy