Skip to Content

SFTP to SFTP interface

Hi Folks,

I am working on SFTP(File) to SFTP(File) interface in sandbox system. File(Txt) is sending data in ~ format to target system .we are using a new approach ~ here.

i tested with following files in sandbox

1.xml to txt----successfull

2.txt to xml----successfull

3.txt to txt---unsucessfull

PI able to pick file and placing the file in target server but data is not populating .In target file the data is displaying only ~~~~~~ like this.

I checked in moni i can see the payload overthere.but in target system data is not coming.

Sender FCC

Receiver FCC

In output directory i am only getting this

22.png (18.5 kB)
23.png (7.4 kB)
24.png (583 B)
Add comment
10|10000 characters needed characters exceeded

2 Answers

  • Posted on Jul 31, 2012 at 11:50 AM

    Are you not seeing error in any of the pipeline steps? Also I want you to see in the receiver communication channel to find more details on this error. The error could be due to mapping area or invalid conversion parameters specified on the receiver channel. Provide more details on the target structure side.

    Add comment
    10|10000 characters needed characters exceeded

    • Just remove your mapping mm_file2file_ in Interface Determination.

      Your interface determination should have only outbound and inbound interfaces, interface mapping should be kept blank. Test end to end, it should work. Then remove all your ESR objects.

  • author's profile photo Former Member
    Former Member
    Posted on Aug 01, 2012 at 02:33 PM

    Hi Muni,

    Everyone here is correct in saying you could do this without any mapping steps.

    However, you should also be able to make this work with mapping. You are obviously very close to making this work because in your output file you are getting 4 delimiters but just the content is missing.

    If you look at your source payload in moni, right click, view source, copy this payload and paste it into your design mapping, test tab (source view).

    Then switch back to tree view which will parse your test input and verify your input message structure versus what your map expects.

    Now is your root node red or green? Sometimes you could run into a root level message name difference that keeps your payload from being recognized in the map.

    If you run this test and get output, you know the problem is something trivial in the output FCC parameters. However, if you run this test and get empty results, you may have a message type mismatch on your input FCC parameters and your sending message type.



    Add comment
    10|10000 characters needed characters exceeded