on 08-23-2017 11:24 AM
Hi Experts,
How do you pass your XML file from PI to SFTP server host folder?
My partner provided the hostname,tcp port, username and password.
What should I do next? How to make sure my file gets into this SFTP?
Appreciate your comments.
JC
Hi,
Would you need this? https://blogs.sap.com/2015/09/28/copy-files-without-mapping-pi-74-java-only-copy-files-without-chang...
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jeff,
Can you elaborate a bit more on what exactly you are struggling with? Configuring the SFTP receiver adapter is fairly straight forward. You may refer to this link and see if it helps.
Regards,
Patrick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Patrick,
Thanks for the quick reply and manual (it really helped).
Checked my SFTP config based on your manual and so far I think everything is in order.
Problem is I would like to pass the file from PI to SFTP folder (host).
I was able to create a couple of XML files manually in the target folder of my SFTP.
Need help on why I can't do it via PI?
What is the issue? Authorization? Our network? My Com Channel?
Regards,
JC
Hi Experts,
Tried to monitor the Communication Channel via the PI monitoring tool:
It said all our com channels are up and running.
The other com channels were able to pick up the file from the SFTP server.
While my com channel has nothing? See the Cluster Node screenshot. It only has greenlight but no file transferred to the SFTP server.
Appreciate your expertise guys.
JC
Well, before your message can go to the communication channel, it needs to enter PI somehow, be routed and possibly translated and only then delivered to your receiver channel. My question was whether you can see the message at some stage of its lifecycle in the message monitor. Once you have identified your message, you should get an idea of its whereabouts from the logs.
Message monitoring is one of the functions in the runtime workbench. You can use it to trace your message through the PI pipeline. If you're on a dual stack system, you could also use T-Code IDX5 to check the status of your incoming IDocs from ECC or SXMB_MONI to trace the pipeline processing in the integration engine.
Unfortunately I'm not familiar with the particular error shown in your screenshot. Maybe try to refresh the cache and explicitly import the metadata of your IDoc (IDX2)?
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.