| |
Results |
|
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/'>
|
|
|
|
Release Package gives error "RequestTimeout: The orchestration request was submitted but the server timed out waiting for the response"
|
When editing a Release Package and attaching a Dimensions Baseline or a ZMF Package, the system make give error: Error occurred during web service invocation: SOAP Fault Code: env:Server
|
|
|
|
How to get more logging when the SBM GSOAP web service is called
|
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.
|
|
|
|
Get Response failed...The handle is invalid in Event Viewer when running an orchestration workflow.
|
Error occurred during web service invocation: Response failed... The handle is invalid.
|
|
|
|
The Orchestration Engine cannot send the Web service request at Service step SAC_GetMapRecordForProductAndRelease with Agile Connector
|
com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: java.security.PrivilegedActionException: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Bad response : (404Not Found )
|
|
|
|
Upgrade from 6.0: When start manual task, get error "A Schema Parser Exception occurred while parsing the response at line 1:3167"
|
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
|
|
|
|
Example application to illustrate using the "RESTCaller" functionality that enables an SBM orchestration workflow to call REST-based Web services.
|
http://www.predic8.com/rest-demo.htm This example url returns an XML response that looks like this. <CUSTOMER xmlns:xlink
|
|
|
|
How to use the RunReportXml web service with a report that takes a query at runtime parameter.
|
<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.
|
|
|
|
ZMF: Call to 'base' approvePackage web services gives error "java.io.IOException: Non nillable element 'approverEntity' is null"
|
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 one such function in ZMF (e.g. connect to ZMF, perform a function, receive the response , disconnect).
|
|
|
|
ZMF: Call to 'base' web services gives error "java.io.IOException: java.io.IOException: Non nillable element 'user' is null"
|
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 one such function in ZMF (e.g. connect to ZMF, perform a function, receive the response , disconnect).
|
|
|
