The problem statement says like this, "We use correlation to keep track of related messages in a sequence of message exchanges. For example, the purchase order and the sales will have the same order number. To ensure that the purchase order and the corresponding sales operations are correlated, we can assign a correlation using the purchase order number. In finding correlation we have to define the elements that are relevant to the messages to be correlated with."
For me this can be implemented like this, 1. First let users to engage activity monitoring service based. 2. Then in each service let users to define an xpath to extract the correlation id. That depends on the message format. 3. Since now BAM publisher can send the same activity id for related messages relate them and show in the BAM admin console. thanks, Amila. On Sun, Oct 9, 2011 at 8:43 AM, Amila Suriarachchi <am...@wso2.com> wrote: > hi, > > I read this link[1] about the feature. But I could not get what type of use > case it try to address and how the client going to see the results. Are > there any other document on this? > > As I understood in order to make this works, client suppose to add a soap > header as given and BAM publisher copy that activity id to published > message. Otherwise BAM publisher generates an id for each and every request > without making any correlation between them. > > How practical asking clients to set a special soap header which is most > probably not given in wsdl? > > > [1] http://wso2.org/project/bam/1.3.0/docs/activity.html >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
