August 24, 2013

Output of EAI Webservice with Soapui is Gibberish

This is most likely the first response from a Siebel Webservice when you use SOAP UI to test an Inbound web service.

Response you might get in SOAP UI response section would be like:

HTTP/1.1 200 OK
Date: Mon, 12 Aug 2013 11:44:11 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
_CharSet: UTF-8
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Content-Encoding: deflate
Transfer-Encoding: Chunked
Content-Type: text/xml;charset=UTF-8
Content-Length: 1061

ÃL__C: i=Š¯_á.t_¡ ä_:}¡Ø
h*K_INp?}×Æò_–¡—¹w ýýW«Õj%@_ö__¼_©&# 168;àWÃÉh<___ data-blogger-escaped-25="" data-blogger-escaped-_="" data-blogger-escaped-a="" data-blogger-escaped-l="" data-blogger-escaped-q="" data-blogger-escaped-u__="" data-blogger-escaped-x="">8¤_ :ÃBš ÂLç(_á”ʽ¢¥ê íímôös__ŽÇ_çË&#22 6;n ;º \iÌ_R©ÂÓªá \©™v-SFþO”µl]‹0õ Œ_wMÉ3aSÁ5_ôŸ ‘éu:__ˆŠ_W&›

As you would have realized web-service is working fine from Siebel end and returning correct HTTP  200 OK response, this is actually problem with default on response compression preference in SOAP UI which should be disabled to test any Siebel Inbound Web Service.

Uncheck the Response Compression to see actual SOAP response

Both the kind of output we get to see and the effort jecissalynn user have spent on youtube to made me post this.


1 comment :

  1. This is awesome! I can finally use it. Thanks a lot!