cancel
Showing results for 
Search instead for 
Did you mean: 

FTP Receiver Adapter is completly ignoring the file content conversionurn..

rainer_hbenthal
Active Contributor
0 Kudos

Hi,

i'm picking up a flat file using the NFS adapter, the payload in the message monitoring looks like this:


<?xml version="1.0" encoding="utf-8" ?> 
<ns:MT_FILE xmlns:ns="urn:......">
<Record>
<Line>100221120100000000000000</Line> 
<Line>100221120100000000000000</Line> 
</Record>
</ns:MT_FILE>

I'm now writing this to an ftp server, message protovol is set to File Content Conversion and the conversion parameters are set to this:


Line.addHeaderLine	1
Line.fieldSeparator	#
Record.fieldContentFormatting	nothing
Line.fieldContentFormatting	nothing
Record.fieldSeparator	*

looks realy weired and is not really what is needed but i changed the parameters dramatically, but none of those conversion parameters are taken in effect.

The resulting files always looks the same, nor do i get a header line nor do i get the "weired" newline characters. i'm alway getten nl/0X0A as line separator.

What do i miss?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Rainer,

You need to do content conversion for the nodes, not for the recordset.Remove Record conversion parameters and try.

Thanks,

stefan_grube
Active Contributor
0 Kudos

> You need to do content conversion for the nodes, not for the recordset.Remove Record conversion parameters and try.

This is wrong. It is the other way:

Use parameter

Record.addHeaderLine 1

When you want to have a different end-of-line cjaracter, you have to use the correct parameter

Record.endSeparator

Sometimes it really helps to look in online help.

Answers (1)

Answers (1)

rainer_hbenthal
Active Contributor
0 Kudos

Hi,

its working now, thx.

Sometimes you miss the wood for the trees, even having the help files printed out....