Hi All, Please find some detailed information regarding the Transport Adaptors in the below link [1]. We are now writing different Transport Adaptor implementations like WSO2Event-Sender, WSO2Event-Receiver, email, WSEventLocal & etc and completed some of them...
We are further working on EventBuilder, EventProcessor & EventFormatter at the moment.. [1] https://docs.google.com/a/wso2.com/presentation/d/1cto7wBG1y5KfeJqGFgp2FlqUeZz-VcdU30Tvmdwhlpo/edit?usp=sharing Thanks, Mohan On Fri, May 10, 2013 at 3:02 PM, Mohanadarshan Vivekanandalingam < [email protected]> wrote: > Hi All, > > We have completed the development of following components... > > - Transport Adaptor > - Transport Adaptor Manager > > Now, we are further working on other components and doing improvements for > them... > > Thanks, > Mohan > > > On Wed, May 8, 2013 at 7:59 PM, Sriskandarajah Suhothayan > <[email protected]>wrote: > >> I have attached the comportment diagram for the following >> >> - Transport Adaptor >> - Transport Adaptor Manager >> - Event Builder >> - Event Processor >> >> Regards, >> Suho >> >> >> On Thu, Mar 14, 2013 at 10:50 PM, Sriskandarajah Suhothayan < >> [email protected]> wrote: >> >>> After the discussion with Srinath we came up with the following CEP >>> architecture. >>> Here we have five components for CEP >>> >>> - Input Transport Adaptor - to receive incoming (XML, JSON, etc ) >>> messages via (JMS, Thrift, etc) >>> - Event Builder - to convert the (XML, JSON, etc ) messages into >>> Siddhi/Common Events >>> - Event Processor >>> - Event Formatter - to convert Siddhi/Common Events back to (XML, >>> JSON, etc ) messages >>> - Output Transport Adaptor - to publish output (XML, JSON, etc ) >>> messages via (JMS, Thrift, etc) >>> >>> With this model any WSO2 server (E.g BAM) can use the Input Transport >>> Adaptor & Event Builder to receive incoming events >>> and use Output Transport Adaptor & Event Formatter to notify outputs E.g >>> Email, >>> At the same time CEP can also be embedded in to other products (E.g ESB, >>> ELB, SS) & invoked using OSGi services buy installing Event Processor (and >>> if necessary Event Builder & Event Formatter) >>> >>> This model also enables events to be passed from one QueryPlan (Bucket) >>> to another within CEP, which was not possible in CEP 2.x. >>> >>> Thoughts? >>> >>> Thanks >>> Suho >>> >>> >>> >>> On Fri, Jan 11, 2013 at 3:58 PM, Amila Suriarachchi <[email protected]>wrote: >>> >>>> looks good. +1 for terminology. >>>> >>>> thanks, >>>> Amila. >>>> >>>> On Thu, Jan 10, 2013 at 12:13 PM, Sriskandarajah Suhothayan < >>>> [email protected]> wrote: >>>> >>>>> With CEP 2.0 we made Siddhi stable and working for most common >>>>> use-cases. >>>>> >>>>> With CEP 3.0 we need to make CEP work seamlessly with other systems >>>>> and also provide solutions to all eventing needs of the platform. >>>>> This is because we have various throttling and notification >>>>> implementations in the current platform, and with this solution we can >>>>> have >>>>> a unified throttling engine using Siddhi, and a unified notification model >>>>> provided by CEP so that whoever needs E-mail,SMS,etc notifications can >>>>> simply use that. >>>>> >>>>> I propose we should go for an architecture as described in the >>>>> attachment. >>>>> >>>>> With this, other products (Stratos,BAM,AM,AF) can easily use modules >>>>> like Notification, and Query&EventProcessor, for notification and Embedded >>>>> Event processing (throttling) needs. >>>>> >>>>> In addition as discussed at the mail "Bringing CEP input mapping >>>>> configuration into Siddhi" we will make input and output mappings as >>>>> Siddhi >>>>> based configuration instead of the current XML format, hence the Bucket >>>>> configuration file will not be an XML but be a Script file containing >>>>> Siddhi. >>>>> Though we move input,output mapping to Siddhi I still believe we need >>>>> to have UI for both input and output mappings as it will be more intuitive >>>>> for the users and as it also improves user friendliness. >>>>> >>>>> Thoughts? >>>>> >>>>> Suho >>>>> >>>>> >>>>> >>>>> -- >>>>> *S. Suhothayan >>>>> * >>>>> Software Engineer, >>>>> Data Technologies Team, >>>>> *WSO2, Inc. **http://wso2.com >>>>> <http://wso2.com/>* >>>>> *lean.enterprise.middleware.* >>>>> >>>>> *email: **[email protected]* <[email protected]>* cell: (+94) 779 756 757 >>>>> blog: **http://suhothayan.blogspot.com/*<http://suhothayan.blogspot.com/> >>>>> * >>>>> twitter: **http://twitter.com/suhothayan*<http://twitter.com/suhothayan> >>>>> * >>>>> linked-in: **http://lk.linkedin.com/in/suhothayan* >>>>> * >>>>> * >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Amila Suriarachchi* >>>> >>>> Software Architect >>>> WSO2 Inc. ; http://wso2.com >>>> lean . enterprise . middleware >>>> >>>> phone : +94 71 3082805 >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *S. Suhothayan >>> * >>> Software Engineer, >>> Data Technologies Team, >>> *WSO2, Inc. **http://wso2.com >>> <http://wso2.com/>* >>> *lean.enterprise.middleware.* >>> >>> *email: **[email protected]* <[email protected]>* cell: (+94) 779 756 757 >>> blog: **http://suhothayan.blogspot.com/*<http://suhothayan.blogspot.com/> >>> * >>> twitter: **http://twitter.com/suhothayan*<http://twitter.com/suhothayan> >>> * >>> linked-in: **http://lk.linkedin.com/in/suhothayan* >>> * >>> * >>> >> >> >> >> -- >> *S. Suhothayan >> * >> *Software Engineer, >> Member, Management Committee - Data Technologies Team, >> * >> * * >> *WSO2 Inc. **http://wso2.com >> <http://wso2.com/>* >> *lean . enterprise . middleware* >> >> *cell: (+94) 779 756 757 >> blog: **http://suhothayan.blogspot.com/*<http://suhothayan.blogspot.com/> >> * >> twitter: **http://twitter.com/suhothayan* <http://twitter.com/suhothayan> >> * >> linked-in: **http://lk.linkedin.com/in/suhothayan* >> * >> * >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *V. Mohanadarshan* > *Software Engineer,* > *Data Technologies Team,* > *WSO2, Inc. http://wso2.com * > *lean.enterprise.middleware.* > * > * > email: [email protected] > phone:(+94) 771117673 > -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com * *lean.enterprise.middleware.* * * email: [email protected] phone:(+94) 771117673
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
