Using the RESTCaller SOAP wrapper utility service provided by SBM that enables SBM orchestration workflows to call REST-based Web services you may see the following error in the Common Log instead of the service running as expected. A Web service was invoked at Service step RESTCaller_post, and now the Orchestration Engine is receiving the following message: <soapenv:Envelope xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/'>
You can use the attached registry keys to enable some very basic logging about the soap request and response that gets sent and received from notifications or other web services. This can be particularly helpful when a soap request or response is too large and gets chopped of in the Common log. This logging will show the entire request and response envelope.
com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: java.security.PrivilegedActionException: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Bad response : (404Not Found )
Error occurred during web service invocation: A Schema Parser exception occurred while parsing the response at line 1:3167 Schema Parser Exception : Could not find element actionDisplay in task
Meaning, you can run the ZMF connect web service from SOAPUI, and then you’re done. You cannot use SOAPUI to connect to ZMF, and then run another web service. The sample application provided in this document demonstrates how to perform several such functions in ZMF (e.g. connect to ZMF, perform a function, receive the response , disconnect).
<urn:extraOption><urn:name>HasRuntimeParams</urn:name><urn:value>1</urn:value></urn:extraOption> </urn:options> When you run the web service the response should be the same results you get in the UI but in XML format.
