Response size Limitation for TSoap in Talend Open Studio

Highlighted
Five Stars

Response size Limitation for TSoap in Talend Open Studio

Hi,

Im using Talend Open Studio for Data Migration for get response from Soap service and insert into SQL database. Im facing size limitation issue when extracting data from Soap Service response. Large part of response is missing when output tSoap output. The response coming as encoded with base 64 from soap service and it will decode through from java code using tJavaRow.
The encoded response actual size length which get from Postman Client is 155467158. But when getting response size from tsoap from Talend Open studio is 16325,most of the data is missing. The below is the screen shot of the Talend job design. 

The below code is used inside of tJavaRow.

String encodeList = sss.encodeByte;
System.out.print(encodeList);

byte[] buf = new sun.misc.BASE64Decoder().decodeBuffer(encodeList);
String decodeList = new String(buf, java.nio.charset.StandardCharsets.UTF_8);
context.OutputXMLEM = decodeList;
System.out.print(decodeList);

 

Could you tell me is there any way to get whole response from tSoap?

Moderator

Re: Response size Limitation for TSoap in Talend Open Studio

Hello,

The return result of web service is a string with XML format, you can use tExtractXMLField component to extract the value after tSOAP.
tSOAP--main--tExtactXMLField--main--output.

Let us know if it is OK with you.

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables

Blog

Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema

Blog

Best Practices for Using Context Variables with Talend – Part 4

Pick up some tips and tricks with Context Variables

Blog