| |
Results |
|
Error coccured during web service invocation:Response failed...
|
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:
|
|
|
|
SBM Web Service response is using two namespaces
|
In some cases the SOAP message returned from an SBM Web Service can use two different namespaces for its elements, where only a single namespace would be expected. The code does not correctly handle the case where the call is in one namespace and the elements type is defined in another namespace.
|
|
|
|
Error occurred during web service invocation:Response failed
|
When running an orchestration, the user sees an error such as: Error occured during web service invocation: Response failed...
|
|
|
|
Handling Large Web Service Responses in Service Steps
|
To handle the fault, you should place the Service step within a Scope step and catch the fault in the Catch All branch of the FaultHandler. In addition, you should consider reducing the size of the response SOAP message's payload by redesigning the way you invoke the Service step. For example, you could add filtering if the Web service supports it.
|
|
|
|
charset specification missing from HTTP header in WS responses
|
charset specification missing from HTTP header in WS responses
|
|
|
|
If a non-privileged user tries to use WS getitemsbyquery, XML response message should not include item id reference
|
If a non-privileged user tries to use WS getitemsbyquery, XML response message should not include item id reference
|
|
|
|
Changing the default size limit for files returned by the GetFileField and UpdateFileField Web service and JSON calls
|
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.
|
|
|
|
Fault handling from web service calls in orchestrations
|
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
|
|
|
|
GetUsers web service call does not return a value for the "timezone" parameter
|
GetUsers web service call does not return a value for <ae:timezone/> parameter in the XML response . It does, however, return the correct GMT offset expressed in milliseconds.
|
|
|
|
Using the RESTCaller SOAP wrapper utility service but get "No compatible tokens found on the request" in soap response.
|
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/'>
|
|
|
