By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,710 Members | 1,626 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,710 IT Pros & Developers. It's quick & easy.

WSI test tool on analysing monitored logs (soap messages)

P: n/a
I have captured some SOAP messages (using org.wsi.test.monitor.Monitor
of the WSI test tool). When I try to analyze the messages with WSI
test tool analyzer, the "message" artifact of the report always return
"Missing Input". I have tried various "correlationType: endpoint,
operation, namespace". When I eyeball the captured SOAP messages,
they looks fine with correct namespace and valid operation name within
the soap body of the <meesageContent> of the monitored log. Is there
a way to force the analyze tool to run all messages regardless? Or
anyone encounters this problem before and can advise?

(The "description" artifact returns fine on the report.)
The monitored soap messages look like..
....
<messageEntry xsi:type="wsi-log:httpMessageEntry" ID="2"
conversationID="1" type="response"
timestamp="2004-07-21T10:42:36.981">
<messageContent>&lt;?xml version=&quot;1.0&quot;
encoding=&quot;utf-8&quot;?&gt;&lt;soap:Envelope
xmlns:soap=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;
xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quo...oductsResponse
xmlns=&quot;http://mystore.mycompany.com/ws&quot...tName&gt;Paper
....
....
&lt;/soap:Body&gt;&lt;/soap:Envelope&gt;</messageContent>
<senderHostAndPort>localhost:8080</senderHostAndPort>
<receiverHostAndPort>xxx.yyyy.www.zzz:portA</receiverHostAndPort>
<httpHeaders>HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Date: Wed, 21 Jul 2004 17:42:36 GMT
Server: Apache Tomcat/4.1 (HTTP/1.1 Connector)
Transfer-Encoding: chunked

</httpHeaders>
</messageEntry>
....

Thanks,
Clara Yeung
Nov 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
WS-I Test Tool... Seems like the work around is to separate the
analysis for WSDL and Message artifacts, by running either WSDL or
Message artifact once at a time.

For example, in the analyzerConfig.xml, when running "message"
artifact, comment out the "WSDL" artifact:
....
<wsi-analyzerConfig:logFile correlationType="operation">
../logs/logDA.xml
</wsi-analyzerConfig:logFile>
<!--
sometimes analyzing wsdl has negative effect to analysis of monitored
log, so run later
<wsi-analyzerConfig:wsdlReference>
<wsi-analyzerConfig:wsdlElement type="port"
parentElementName="DeadOrAlive"
namespace="http://www.abundanttech.com/webservices/deadoralive">
DeadOrAliveSoap
</wsi-analyzerConfig:wsdlElement>
<wsi-analyzerConfig:wsdlURI>
layer7/DeadOrAlive.wsdl
</wsi-analyzerConfig:wsdlURI>
</wsi-analyzerConfig:wsdlReference>
-->
....

Is it a bug in the WS-I test tool?

cl*********@yahoo.com (Clara Yeung) wrote in message news:<e5**************************@posting.google. com>...
I have captured some SOAP messages (using org.wsi.test.monitor.Monitor
of the WSI test tool). When I try to analyze the messages with WSI
test tool analyzer, the "message" artifact of the report always return
"Missing Input". I have tried various "correlationType: endpoint,
operation, namespace". When I eyeball the captured SOAP messages,
they looks fine with correct namespace and valid operation name within
the soap body of the <meesageContent> of the monitored log. Is there
a way to force the analyze tool to run all messages regardless? Or
anyone encounters this problem before and can advise?

(The "description" artifact returns fine on the report.)
The monitored soap messages look like..
...
<messageEntry xsi:type="wsi-log:httpMessageEntry" ID="2"
conversationID="1" type="response"
timestamp="2004-07-21T10:42:36.981">
<messageContent>&lt;?xml version=&quot;1.0&quot;
encoding=&quot;utf-8&quot;?&gt;&lt;soap:Envelope
xmlns:soap=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;
xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quo...oductsResponse
xmlns=&quot;http://mystore.mycompany.com/ws&quot...tName&gt;Paper
...
...
&lt;/soap:Body&gt;&lt;/soap:Envelope&gt;</messageContent>
<senderHostAndPort>localhost:8080</senderHostAndPort>
<receiverHostAndPort>xxx.yyyy.www.zzz:portA</receiverHostAndPort>
<httpHeaders>HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Date: Wed, 21 Jul 2004 17:42:36 GMT
Server: Apache Tomcat/4.1 (HTTP/1.1 Connector)
Transfer-Encoding: chunked

</httpHeaders>
</messageEntry>
...

Thanks,
Clara Yeung

Nov 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.