Currently there are lots of usability issues with BAM mediator, hence as an
alternative we came up with the Data Publisher Mediator[1] as part of a
client engagement.
Data Publisher Mediator uses LoadBalancingDataPublisher to send events to
BAM/CEP endpoints and it also supports XML configuration.
The only drawback is that the Data Publisher Mediator doesn’t have a UI. I
believe writing a UI to this mediator will enhance data publishing and
solve the current usability issues that we are facing now.
A sample XML configuration is as follows
<dataPublisher>
<receiverUrl>tcp://localhost:7612</receiverUrl>
<authenticatorUrl>ssl://localhost:7712</authenticatorUrl>
<userName>admin</userName>
<password>admin</password>
<streamName>AllLocationEvents</streamName>
<streamVersion>1.6.4</streamVersion>
<attributes>
<!-- <meta>
<attribute name="price" type="string"
value="//m:price"/>
</meta>-->
<payload>
<attribute name="latitude" type="double"
default="2.2" value="//m:latitude"/>
<attribute name="longitude" type="double"
default="67.78" value="//m:longitude"/>
<attribute name="accuracy" type="double"
value="//m:accuracy"/>
<attribute name="updatedTime" type="long"
value="//m:timestamp"/>
<attribute name="device_uuid" type="string"
value="//m:device-uuid"/>
</payload>
</attributes>
<namespaces>
<namespace prefix="m" uri="
http://schemas.google.com/latitude/2010"/>
</namespaces>
</dataPublisher>
Regards
Suho
[1]https://svn.wso2.org/repos/wso2/people/suho/data-publisher-mediator
--
*S. Suhothayan
*
Associate Technical Lead,
Management Committee Member, Data Technologies Team,
*WSO2 Inc. *http://wso2.com *
<http://wso2.com/>*
lean . enterprise . middleware
*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: 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
