Active IQ Unified Manager Discussions

WS API problems in WFA 2.1RC

igorf

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>

         <!--Zero or more repetitions:-->

         <!--<parameters />-->

      </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>

         <!--Zero or more repetitions:-->

         <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>

2 REPLIES 2

Re: WS API problems in WFA 2.1RC

sinhaa

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>

         <jobId>196</jobId>

         <parameters/>

      </ws:getReturnParameters>

   </soapenv:Body>

</soapenv:Envelope>

-----

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: WS API problems in WFA 2.1RC

igorf

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.

Earn Rewards for Your Review!
GPI Review Banner
All Community Forums
Public