WS API problems in WFA 2.1RC

igorf — Thu, 05 Jun 2025 05:56:03 GMT

getReturnParameters WS API call with variable number of parameters was working fine in previous WFA version.

Now if I specify zero number of parameters, like below, it returns fault.

<?xml version="1.0" encoding="UTF-8"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.wfa.netapp.com/">

<soapenv:Header />

<soapenv:Body>

<ws:getReturnParameters>

<jobId>284</jobId>

</ws:getReturnParameters>

</soapenv:Body>

</soapenv:Envelope>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>Fault occurred while processing.</faultstring></soap:Fault></soap:Body></soap:Envelope>

If I specify at least one parameter, everything works as expected:

<?xml version="1.0" encoding="UTF-8"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.wfa.netapp.com/">

<soapenv:Header />

<soapenv:Body>

<ws:getReturnParameters>

<jobId>284</jobId>

<parameters>LIFname</parameters>

</ws:getReturnParameters>

</soapenv:Body>

</soapenv:Envelope>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns2:getReturnParametersResponse xmlns:ns2="http://ws.wfa.netapp.com/"><return><name>LIFname</name><value>nasvmwesx01lab01</value></return></ns2:getReturnParametersResponse></soap:Body></soap:Envelope>

Re: WS API problems in WFA 2.1RC

sinhaa — Wed, 14 Aug 2013 11:34:26 GMT

If you don't want to provide any parameters the following request will return all the return parameters in the given job execution.

End Point: WorkflowService_rpc

----

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.wfa.netapp.com/">

<soapenv:Header/>

<soapenv:Body>

<ws:getReturnParameters>

</ws:getReturnParameters>

</soapenv:Body>

</soapenv:Envelope>

-----

Re: WS API problems in WFA 2.1RC

igorf — Wed, 14 Aug 2013 16:24:24 GMT

This is good to know. However, in HPOO I have little control on how InvokeMethod2 constructs dynamic parameters portion in SOAP request. This breaks integration with HPOO which was working fine with previous WFA release.

topic WS API problems in WFA 2.1RC in Active IQ Unified Manager Discussions

WS API problems in WFA 2.1RC

Re: WS API problems in WFA 2.1RC

Re: WS API problems in WFA 2.1RC