I'm not sure if the billing service needs the data from the business analysis. If it doesn't need those data, it could be more easy by using wire-tap[1]
[1]http://camel.apache.org/wire-tap.html -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Thursday, April 25, 2013 at 9:29 PM, James Green wrote: > This isn't to do with Camel per se but I'm hopeful I'm asking this question > of the the right audience! > > Basically we're going to be routing event messages into some storage > component where some of those messages may be billable to customers. > > We have an existing service that charges customers based on a high level > aggregate summary of activity. We are missing a component that takes these > new event messages, performs business analysis on them, then sends them > onwards into our existing billing service. > > BPM sounds almost like the thing we want, but it's rather broad given our > somewhat narrow scope. > > Can any Camel users advise on what they use to aggregate events for billing > purposes? > > Thanks, > > James
