New to CloverETL Having issues with WebServiceClient

CloverDX Platform
1

I’m new to CloverETL and for that matter to integration using SOAP. I have a cloud based system which after logon the system responds with a sessionId. All subsequent requests must contain the sessionId. I used the WebServiceClient to log on and the return of the sessionId was successful and passed as $return to the next web service client.

The following is the next web service client call to request data from the cloud based system. As can be seen the $return is placed in the correct sessinID field in the soap call.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://objects.services/xsd" xmlns:ser="http://services">
   <soapenv:Header/>
   <soapenv:Body>
      <ser:findEntity>
         <ser:sessionId>95e2c2cf-0705-4b53-ac78-674bc46e8cca</ser:sessionId>
         <!--entity type id is 96 for request lookup -->
         <ser:entityTypeId>96</ser:entityTypeId>
         <!--The list attributes to be fetched: requestid(9601)-->        
         <ser:fieldsRequest>9601</ser:fieldsRequest>
      </ser:findEntity>
   </soapenv:Body>
</soapenv:Envelope>

When submitted to the cloud web service, the response in CloverETL is a null.

09:36:24,731 INFO  [WEB_SERVICE_CLIENT_39] Web Service Client response:
 null
09:36:24,731 ERROR [WatchDog_39] Component [WebServiceClient:WEB_SERVICE_CLIENT] finished with status ERROR. (In0: 1 recs, Out0: 0 recs)
 4
09:36:24,731 ERROR [WatchDog_39] Error details:
org.jetel.exception.JetelRuntimeException: Component [WebServiceClient:WEB_SERVICE_CLIENT] finished with status ERROR. (In0: 1 recs, Out0: 0 recs)
	at org.jetel.graph.Node.createNodeException(Node.java:631)
	at org.jetel.graph.Node.run(Node.java:599)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.axis2.AxisFault: 4
	at com.opensys.cloveretl.component.ws.proxy.b.onFault(Unknown Source)
	at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:462)
	... 3 more

When I run the same through SoapUI - I get a correct response.

soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns:findEntityResponse xmlns:ns="http://services" xmlns:ax21="http://objects.services/xsd">
         <ns:return xsi:type="ax21:EntityObj" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ax21:entityId>1205768674</ax21:entityId>
            <ax21:entityTypeId>96</ax21:entityTypeId>
            <ax21:methodValues xsi:type="ax21:ValuePair">
               <ax21:elementValue>1205768674</ax21:elementValue>
               <ax21:id>9601</ax21:id>
            </ax21:methodValues>
         </ns:return>
         <ns:return xsi:type="ax21:EntityObj" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ax21:entityId>1205841814</ax21:entityId>
            <ax21:entityTypeId>96</ax21:entityTypeId>
            <ax21:methodValues xsi:type="ax21:ValuePair">
               <ax21:elementValue>1205841814</ax21:elementValue>
               <ax21:id>9601</ax21:id>
            </ax21:methodValues>
         </ns:return>
               </ns:findEntityResponse>
   </soapenv:Body>
</soapenv:Envelope>

I’ve tried mapping, dumping to a file, a dump straight to Trash, nothing I try seems to get the response from the web service other than null. I’ve tried just mapping the elementValue which is really what I’m after. I’m stuck on this because it works fine in SoapUI but not in CloverETL. Any help would be greatly appreciated in telling me what I’m doing wrong in CloverETL.

Thanks,
Todd

2

Hi Todd,

Could you please post the full error stack trace, that way I can see what might be causing the error. Also, if possible can you please attach the graph, I would like to see how you are mapping data to the request in the WebServiceClient (please remove any sensitive data).

Thanks in advance,
Pedro