Hi Maninda, We have output transport adopters which basically converts the streams to the respective transports such as JMS, etc according the current architecture. AFAIK there is already a JMS transport adopter. And therefore we need to write a Hive handler to write to the streams, rather JMS queue. In this model, we could leverage already existing output transport adopters to output the hive results, not only for JMS queue.
WDYT? Thanks, Sinthuja. On Tue, Sep 17, 2013 at 1:57 AM, Maninda Edirisooriya <[email protected]>wrote: > I am going to write a Hive handler that will send summarized data to JMS > queue. This will be used to collect summarized data from Hive and publish > them to a JMS queue / topic. This JMS topic will be the same topic where > the CEP events will also be published. > > This topic will be visible to dashboards so that they can subscribe to a > such a JMS topic according to the new BAM architecture. > * > Maninda Edirisooriya* > Software Engineer > *WSO2, Inc. > *lean.enterprise.middleware. > > *Blog* : http://maninda.blogspot.com/ > *Phone* : +94 777603226 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Sinthuja Rajendran* Software Engineer <http://wso2.com/> WSO2, Inc.:http://wso2.com Blog: http://sinthu-rajan.blogspot.com/ Mobile: +94774273955
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
