Wednesday, July 7, 2010

Siebel Web Service with SoapUI

I was working with Siebel webservices for Query Customer and found that it was working fine from BPEL but when I try from soapUI, it returns junk characters. Upon intercepting both traffic using tcpmon, we found the issue was in one of the HTTP header. Basically "Accept-Encoding: gzip,deflate" which was sent from SoapUI was causing the problem.

In soapUI, you can disable this particular header via following option. Once the option is enabled, you can invoke Siebel web service doesn't return junk data and returns valid XML data.

3 comments:

Unknown said...

Chintan,

I cannot thank you enough. Thanks much. This has been a lifesaver! I was losing my mind over this problem.

Have you been able to import WSDLS with SOAP_DOC_LITERAL or SOAP_RPC_LITERAL bindings into SoapUI?

I cannot. I get an invlid message. Only SOAP_RPC_ENCODED work.

How about you?

Chintan Shah said...

That's great to hear. I probably have tried doc_literal and rpc_literal, but I don't remember or at least I don't have correct project.

Another thing you can try is to use existing project, and change endpoint URL and payload, at the end it is just http post request. I know importing would still be an issue, can be worked out separately.

May be you can send me your WSDL (chintanjshah at gmail) and I can see if I can replicate.

Innovapath said...

Excellent Post. Also visit http://whiteboxqa.com/selenium.