AnsweredAssumed Answered

CEM - Regex on ResponseBody Possible

Question asked by RazMan on Mar 25, 2014
Latest reply on Dec 29, 2015 by Hiko_Davis

Hello Community,

We are currently running CEM with Introscope 9.5 on a Linux 64bit:

Machine Settings 9.5.0.0 build 465369
Multi-Port Monitor 9.2.0.0038
Multi-Port Monitor Prerequisites 9.2.130913
System Health 9.5.0.0 build 465369
Third-party 9.5.0.0 build 465369
Tim 9.5.0.0 build 465369

We are trying to get create business transactions where the SOAP envelope contains a certain "user".  Is this possible to do?  I have created various templates under Transaction Discovery but none have seemed to parse the SOAP envelope.

 Under the template, I have even tried setting URL Path Filter and Content type to *

Under parameters, I have tried Any * Matches * 

 

Any ideas as to what I may be doing incorrectly.  A slightly scrubbed TIM log output is below:

 

Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Meta: RequestBody body = <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><soapenv:Header><{USERNAME}:Security xmlns:example="example.xsd" soapenv:mustUnderstand="1"><example:UsernameToken><example:Username>{USERNAME}</example:Username><example:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">{PASSWORD}</example:Password></example:UsernameToken></example:Security></soapenv:Header><soapenv:Body><port:getAllAdminCodeTypes xmlns="http://www.ibm.com/mdm/schema" xmlns:port="http://www.ibm.com/mdm/admin/port">.  <RequestControl>.    <requestID>{SOME ID }</requestID>.    <DWLControl>.      <requesterName>{REQUESTERNAME}</requesterName>.      <requesterLanguage>100</requesterLanguage>.    </DWL
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Full host: xxxx.domain.com
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Param: Resp   Resp Status = 200.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Param: RespHeader Resp X-Powered-By = Servlet/3.0.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Param: RespHeader Resp Content-Type = text/xml; charset=UTF-8.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Param: RespHeader Resp Content-Language = en-US.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Param: RespHeader Resp Content-Length = 8539.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Param: RespHeader Resp Date = Tue, 25 Mar 2014 19:40:32 GMT.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Param: RespHeader Resp Server = WebSphere Application Server/8.0.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Meta: Response Status = 200.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Meta: ResponseHeader X-Powered-By = Servlet/3.0.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Meta: ResponseHeader Content-Type = text/xml; charset=UTF-8.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Meta: ResponseHeader Content-Language = en-US.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Meta: ResponseHeader Content-Length = 8539.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Meta: ResponseHeader Date = Tue, 25 Mar 2014 19:40:32 GMT.
Tue Mar 25 15:40:36 2014  7339   Trace: w0:   Meta: ResponseHeader Server = WebSphere Application Server/8.0.

 Thank you in advance!

Outcomes