Hi Chamin, BAM message tracer mainly monitors axis2 services that is deployed by the users; ie, axis2 services deplyed in wso2 as, proxy services, apis in APIM, ESB, etc. And currently the admin axis2 service calls are ignored. Therefore for IS, if you are planning to monitor the authentication admin services, then current message tracing feature may not work, and you may need to tweek that. But IMHO it will be better if you could have different agent for this purpose, and extract all related information that needs to analyzed in IS perspective rather trying to modify the message tracer as both are actually focusing in different usecases.
Thanks, Sinthuja On Mon, Dec 22, 2014 at 10:16 AM, Chamin Nalinda <[email protected]> wrote: > Hi all, > > Can someone explain me $subject and how to integrate it with WSO2 IS. I > followed article [1] and I guess it is very much the similar with IS as > well. I need to publish IS data (request data and corresponding respond > data) to BAM and hoping to use BAM Message Tracer. > > [1] > https://docs.wso2.com/display/BAM241/Setting+up+Message+Tracing+for+WSO2+ESB > > > -- > *Chamin Nalinda* > > Intern - Engineering > WSO2 Inc. http://www.wso2.com > lean.enterprise.middleware > > Mobile: (+94) 77 241 66 04 > Linkedin: https://www.linkedin.com/in/chaminnalinda > Web: http://www.ckreativity.com > Blog: http://techspiro.blogspot.com/ > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Sinthuja Rajendran* Senior Software Engineer <http://wso2.com/> WSO2, Inc.:http://wso2.com Blog: http://sinthu-rajan.blogspot.com/ Mobile: +94774273955
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
