Receiver communication chanel error in File conversion scenario

[Former Member]

Hi ,

I am trying to implement a file-xi-file scenarion in which the input is a tab delimited file...The Sender channel works fine.

The problem i am facing now is that the receiver commmunication channel throws an error in adapter monitoring..the error says ...

"Receiver Adapter v2123 for Party '', Service 'FILE_TRANSFER2_SD':

Configured at 2006-05-18 14:26:02 GMT+05:30

History:

- 2006-05-18 14:26:02 GMT+05:30: Error: Conversion initialization failed: Exception: java.lang.Exception: Error(s) in XML conversion parameters found:

Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing "

If i remove the receiver content conversion then the channel works fine and gives me the output as one single string of charaters widout any formatting....

I have added both the fields in the content conversion of the receiver channel...

Plz help...

Thanx ,

Srestha

[Former Member]

Hi

The parameter "Recordset Structure" is incorrect

Please state the value for above parameter correctly or post it to forum , so that we can point out the fallacy

Regards

[Former Member]

Hi,

My record set structure is as follows :

RecordSet Structure - HEADER,*

HEADER.fieldNames NAME,LNAME,COMPANY,ID

HEADER.keyFieldValue 01

HEADER.fieldSeparator '0x09'

HEADER.endSeparator 'nl'

HEADER.fixedFieldLengths10

ignoreRecordSetName true

Thanx ,

Srestha

[Former Member]

Hello

Set RecordSet Structure - HEADER only . No need for *

Regards

Note : ignoreRecordsetName is not required

[Former Member]

Hi,

In recordstructure just give HEADER no need of *.

U need to either specify fieldSeparator or fieldFixedLength.because the xml structure when it is produced in the flat file will be either fixed length seperated or it will be a comma,space or delimeter separated.

So no need to specify both.

And in the reciever no need to mention keyfieldvalue,

if it is not a fixed length sperator then just specify the

fieldSeparator and the endSeparator.

regards

jithesh

[Former Member]

Hi ,

Thanx a lot...the receiver channel works fine now...but anothr problem s dere :(....the output file which gets created does not contain the entire file data..only the first field...

Plz help .

Thanx a lot,

Srestha

[Former Member]

Hi,

i think u have given fieldFixedLength in ur reciever communication channel,

as per ur reciever file communication channel scenario

Header.fieldNames name,Lname,company,id

and u have given

Header.fieldFixedLengths 10.

so u have mentioned fixed size only for the first field.so in ur output file u get only one field.

So give ur Header.fieldFixedLengths 10,10,10,10 fixed size for all the four fields

regards

jithesh

[Former Member]

Jithesh ,

Thanx for replying back so promptly..i have removed the fixedfieldlengths field from the receiver channel...

I tried populating it back again with the values u specified..it dint work....only the first field came....

Please help.

Thanx ,

Srestha

[Former Member]

Hi,

try this

just give the Record Structure Header

and

in the content conversion parameter give it as

Header.fieldSeparator ;

Header.endSeparator 'nl'.

and its actually fieldFixedLengths and not fixedfieldLengths

regards

jithesh

[Former Member]

Hi,

You have to give in you field content conversion either the paramter 'field seperator' or 'fieldFixedLengths'

<i>'If you make a specification here, the system expects that the structure contains the specified character string (one or more characters) as a separator between the individual columns.

If you have not made an entry for fieldFixedLengths, this is the only specification to identify the individual columns in a row.

If you made a specification for fieldFixedLengths, the extra length of the separator is taken into account, but no further consistency checks are performed.</i>

Regards

Vijaya

Message was edited by: vijaya kumari

[Former Member]

Hi vijaya ,

I have mentioned both the fields in the receiver content conversion.

Regards ,

Srestha