In Business Mashups, when performing a Transition with a web service associated, you may receive the above error message. The full error message would be similar to:
If you would like to communicate to TeamTrack using Web Services but are using NT Challenge Response (NTLM) for authentication. And have also setup the gsoap virtual directory to use NTLM (otherwise there would be a security hole, since non-authenticated users would be able to execute web services programs on the TT database with only a valid loginid and no password).
The total size of the response that is returned by the GetFileField and UpdateFileField calls is determined by the FileFieldTotalSizeMax_MB global system setting in the code. The default value is 50MB.
When a web service is called from an orchestration the way it will be handled depends on how the webservice responds. If it is regular response , the it will not be caught as a fault. If it is SOAP fault, then it can use a named catch branch
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 )
