Mark,
I ran two tests in order to determine the source of the error. The first time I invoked the service, I left the SOAPAction value just as it was when I created the web service connector (document/urn:crmondemand/ws/account/10/2004:AccountInsert). Siebel on demand reported the following error:
<?xml><soap-env:envelope><soap-env:body><soap-env:fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>SOAPAction '<?>' is of invalid format: SOAPAction should be of the form "rpc/operationName" or "document/operationName".(SBL-EAI-08006)</faultstring><detail><siebelf:errorstack><siebelf:error><siebelf:errorsymbol></siebelf:errorsymbol><siebelf:errormsg>SOAPAction '<?>' is of invalid format: SOAPAction should be of the form "rpc/operationName" or "document/operationName".(SBL-EAI-08006)</siebelf:errormsg></siebelf:error></siebelf:errorstack></detail></soap-env:fault></soap-env:body></soap-env:envelope>
Next, I delimited the SOAPAction value with double quotes (“document/urn:crmondemand/ws/account/10/2004:AccountInsert”). Everything worked fine.
Thanks for the good feedback, Mark. This has been a valuable learning experience.
BTW - I opened an OLD book of mine, “Programming Web Services with SOAP”, and found the following under “Contentious Issues”:
“The W3C working group that is standardizing SOAP is leaning towards deprecating the SOAPAction header in the next version of the protocol.” Since this book was printed in 2002, this might already be the case.
#API-Management#webMethods#soa