Receiver file channel-FTP

Hello All,
Scenario is Outbound(ECC to FTP).
Below is the steps in audit log of Receiver file adapter:
12.07.2011 03:30:07 Information Write to ftp server "AAAA", directory "'DEV'", file "DEV.OUTPUT>XML".
12.07.2011 03:30:07 Information Transfer: "TXT" mode, size 55 bytes, encoding ISO8859-1.
12.07.2011 03:30:07 Information 200 SITE command was accepted
12.07.2011 03:30:07 Information File processing finished.
12.07.2011 03:30:07 Information MP: leaving
12.07.2011 03:30:07 Information The message was successfully transmitted to endpoint <local> using connection File_http://sap.com/xi/XI/System.
12.07.2011 03:30:07 Information The message status was set to DLVD.
In step3, It is saying 200 SITE command was accetped. But I didnt mention any UNIX command in my receiver file channel(FTP
transport protocol).
Can someone tell me from where is this coming or is it a default one?
Thanks,
Regards,
Moorthy

Hi
Please see the DOC for SITE Command:
SITE command is used by the server to provide services specific to the system. Most of the SITE commands can be used by the admin only. You can get all the available SITE commands by "SITE HELP".
http://incubator.terra-intl.com/projects/ftpserver/site_cmd.html

Similar Messages

Receiver File channel for XML files: with carriage return

Hi all,
we are using a receiver FILE channel to generate an XML file that is sent to an external partner.
The XML file looks good in a parser (IExplorer). But in fact there are not carriage return / line feeds between the XML tags
of the XML payload in the file.
Our partner now requires the XML file in a more vertical structure which means: for every tag a separate line (like it is displayed in a parser)
Does anybody know a more general way to convert to a vertical XML structure (so with carriage return line feed).
There is one entry in the SDN dealing with this topic but suggesting using an UDF. I think this is a very specific way.
I don't think it is a good way to change/enhance the message mapping just because of a general formating change.
Is it better to use an XSLT mapping as a second step in the interface mapping or a JAVA adapter module to convert ?
any experiences? suggestions? examples?
Thank you very much
best regards
Hans
examples:
original by XI receiver FILE adapter
<?xml version="1.0" encoding="UTF-8"?>
<MT_batchStatus><type>BS</type><header><message><messageSender>SENDER</messageSender><messageDate>20090723143720</messageDate> ... and so on
required:
<?xml version="1.0" encoding="UTF-8"?>
<MT_batchStatus>
<type>BS</type>
<header>
<message>
<messageSender>SENDER</messageSender>
<messageDate>20090723143720</messageDate>
... and so on

>
Hans Georg Walter wrote:
> Is it better to use an XSLT mapping as a second step in the interface mapping or a JAVA adapter module to convert ?
> any experiences? suggestions? examples?
In such a case, the best is to write an generic XSLT or Java mapping that will attempt to do the pretty printing/formatting of the xml.
The advantage of a generic one is that you can reuse the same class/jar for many other scenarios.
so the flow will be as below in your interface mapping;
1. your specific source to target mapping
2. the generic formatting class

Receiver file channel with ANSI format.

Hi,
I have developed file to file scenario for which sender file format is unicode and receiver file format is ANSI.
There is no FCC at sender and receiver site. In interface we are just bypassing the file in PI, there is no ESR objects.
I have configured sender channel for unicode in following way:
File Type : Text
file encoding : UTF-8
I have configured receiver file channel for ANSI in following way:
File Type : Text
file encoding : i have tried with cp1252 and ISO8859-1
When I run the interface I received receiver file in ANSI format. But when I open that file in notepad the content in the file is having spaces in between 2 characters like below.
V O L 1 0 0 0 0 0 9
Is any bady having idea about this problem?
Thanks.
Edited by: darshana-PI on Jan 23, 2012 6:32 PM

Hi,
The blanks in your target file might be created because your source file is encoded with UTF-16, not UTF-8. Try using one of these as an encoding in sender communication channel:
UTF-16BE (16-bit Unicode character format, big-endian byte order)
UTF-16LE (16-bit Unicode character format, little-endian byte order)
UTF-16 (16-bit Unicode character format, byte order)
Hope you'll find this useful,
Greg

'Use Temporary File' in Receiver File channel

hi all,
I am facing a strange issue with receiver file channel which I am not sure if somene had already faced. I couldnt find any help from blogs..!
I have configured the Receiver File channel with Write mode as 'Use Temporary File' with a temporary file name(say tmp.xml) scheme and Empty-Message Handling set to 'Write Empty File'
When the scenario is executed, its so happening that the temporary file of 0 bytes(empty file) is being created as tmp<msgID>.xml before the actual file is being completely written. It is expected that once the Actual file is completely written, the tmp file should be deleted, but here is not the case.Thus causing both the files being present in the target location. This is not happening often though.
As the receiving application is processing all files from the target direcotry, the file is getting errored out in the target application.
I think the 'Write Empty File' has nothing to do with this as the option 'Write Empty File' is for empty payloads resulting from the message mapping.
Please correct me if am wrong and also provide me the inputs on my issue. Am on PI7.0
thanks in advance,

Hi Tilak,
this is real time interface
real time by using a file... that's a non-sens according to me. You should use a non physical solution (web service, JMS, JDBC, etc...) but a not a file. well... Anyway, you can image that the receiver application schedule the folder every 30s or every 1min, that's almost a real time. Real time is mainly a conceptual view (only synchronous exchange needs really real time). Morevoer, if you really wanted a real time, you should not add a tool like PI (or other) between your source and your target system, the more we have systems, the less it's efficient (in term of delay and response time!).
Even if we propose that the receiver application should have a condition to its script to avoid picking the tmp*.xml files, after a period of time there would be a chance that the *tmp files may increase in number..
No ! coz if my theory is good, if your receiver application does not pick-up tmp.xml, that means this file is not currently treated and so PI is authorized to delete it. So no increase of tmp.xml files in this folder.
Another solution: to create the target file without option "temporary", but to create it in another folder than this one scheduled by your receiver application, and use an OS command AFTER processing, in your receiver CC, which move the created file from the "temp" folder to the target folder.
[http://wiki.sdn.sap.com/wiki/display/XI/SAPXIFileAdapterOSCommandLine+Feature]
regards.
Mickael

Error in Receiver File Channel...in MTB module (Urgent)

Hi,
I am working on a Proxy to File scenario. I am using Message Transformation Bean in receiver file channel to convert xml file into fixed length file. I am getting an error : Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: java.lang.Exception: Exception in XML Parser (format problem?):java.lang.NullPointerException'; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):java.lang.NullPointerException
in MTB step of audit log for comm channel.
Please help me resolve this.
Thanks,
Jaya

Hi ,
"Transform: failed to execute the transformation:"
Pls check ur data what u have to send .. any missing information or any special Chacters or any extra fields are available in the data, this type of transformation error raised.
check once again ur mapping transformation and test the mapping in INTEGRATION REPOISTERY with the same data(what u have to send Previously).
and also check ur adapter status in RWB.
Regards,
Sateesh N.
Edited by: Sateesh N on Apr 21, 2008 1:53 PM

Unwanted character in Receiving Files at FTP

Hi All,
We have scenario where I am sending the files(NFS) to FTP,just like file to file scenario. It seems to every thing is fine but when I look at that files in receiver side(FTP) there is a special charcter placed in end of each record. ^M
like this :
werrtt, 123224214, fsdaff,^M
dsfdsf,6756767,dsfsffdff,^M
Do you have any idea why it(^M) is coming, do I need to use Unicodes for aviod that ? currently I am using binary/format in channel. If I dont send those files to FTP , then I dont see that character.
Our FTP on Unix and Files picking from windows(NFS).
How to avoid this special character(^M)?, Is this based on FTP behaviour or environment problem?
Thanks,
Shankar

> This has resolved the issue but I believe instead of unix script if we can handle in XI itself, it will be too good.
You can do this in PI, but it is a cumbersome:
Put following modules in the module before the standard module:
1. Use the StrictXml2PlainBean instead of the content conversion in file adapter
http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/748d595dab6fb5e10000000a155369/frameset.htm
2.ConvertCRLFfromToLF
http://help.sap.com/saphelp_nwpi71/helpdata/EN/96/f04142099eb76be10000000a155106/frameset.htm

Error :Receiver File Channel not Initialized

Hi all,
I am using a file adapter at the receiver side with file content conversion option. When i post a message it shows an error in the message monitoring as "Reciever File Channel not initialized : Unable to proceed : null"
Please Help.....

Hi,
Check if the adapter is active or
check on this thread:
File Adapter Not Initialized Error
the error might be due to FCC. Jsut remove that and see ift he adapter works.
Regards
vijaya

SFTP receiver File channel

Hi,
I am doing a simple file pass through using PI (File-PI-SFTP) and not using ESR.
I have two requirements -
1. The target file name should be in the format xyz_yyyymmdd.dat
The standard function with the receiver SFTP channel is to get the timestamp but I don't require timestamp.
Could anyone please let me know if I can get the file name format (xyz_yyyymmdd.dat) without using any mapping?
2. I am using certificates, but still the channel requires a User Name (it is a mandatory field). I am unable to understand why I need User Name even if I am using certificates? Is there a way of avoiding that?
Any help will be highly appreciated.
Thanks,
Abhi

Question 1
Have you seen this wiki page?
http://wiki.sdn.sap.com/wiki/display/Snippets/DynamicfilenameinaFiletoFilepassthroughscenario
2. I am using certificates, but still the channel requires a User Name (it is a mandatory field). I am unable to understand why I need User Name even if I am using certificates? Is there a way of avoiding that?
You might want to try anonymous ssl mode. This might not require credentials. But certificate authentication looks for the user credentials. Take help from BASIS.
Edited by: Baskar Gopal on Mar 6, 2012 4:53 PM

Can we archive files using the receiver file channel

Dear all,
I'm looking for a option, where in I want to archive the files being sent to the target system.
Do we have that facility in XI Receiver File communication channel.
Can the same be achieved for JMS Receiver channel.
Kindly give your comments or responses.
Regards,
Younus

Hi,
AFAIK only the sender file adapter has such a functionality.
A workaround would be to send the file to a second receiver (for example a archive directory on your PI server).
Regards
Patrick

Variable Substitution in Receiver File Channel

Hi All,
Could you kindly help me with this?
Mine is File to File Scenario. ECC drops a XML file in AL11 directory and i send that file using FTP to a third party system. There is no mapping involved and i use ICO. I need to get a value from the payload dynamically for using it in my file name.
When i tried to use Variable Substitution Method i get this error : VariableDataSourceException: Caught SAXException while parsing XML payload: Content is not allowed in prolog.
This is the reference i have given in my variable substitution : payload:customerelement,1,customer,1,sender,1,dealercode,1
and my XML structure is as below and i am trying to access the dealercode field in the XML.
<?xml version="1.0" encoding="UTF-8"?>
-<ns0:CustomerElement xmlns:ns0="http://www.xxxxxx.com/customer">
<recordCount>34</recordCount>
<Customer>
<Sender>
<transmitDate>ddmmyy</transmitDate>
<dealerCode>N050</dealerCode>
<DMSSystem>ABC</DMSSystem>
<DMSReleaseNumber>1.0</DMSReleaseNumber>
</Sender>

Hi Amit,
Yeah that is correct. But in my case the XML structure was not properly formed and i hwas frequently getting this error " Content is not allowed in Prolog" for which i tried all the solutions in SDN and nothing worked out. So i had no other option and had to go for adapter module.
Now the issue is solved and the interface is working as expected with the adapter module.
Thanks for your valuable inputs.
Regards,
Prabhu V

Capture Ackonwledgment from receiver file channel

Hi Friends,
I'm doing a scenario proxy-> file and then mail. I have to post a file to ftp folder and if the posting is succesfull I have to trigger a mail.
I have tried this using bpm since I have decison step in between. I'm using send step with transport ack, but I'm not able to capture the acknowledgment status message. I need this to chk the status and then trigger another send step for mail.
Please suggest how do I do this and is this possible without bpm.
Thanks in advance.
Pragati.

Hi,
the code to ask for technical ack is here:
http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
so is the part at the end to query ack and you should get the details with get_status_detail( )
then you can send the mail
Regards,
Michal Krawczyk

Receiver File Adapter: FTPS Error

On sending a text file to a trading partner the log in the communication channel shows the following:
Connecting to FTP server - success
Write to FTP server - success
Transfer: "TXT" mode - success
Exception caught by adapter framework:connection timed out - Error
The FTP connection Parameters have:
Data connection = Passive
Connection security = FTPS (FTP using SSL/TLS)
Command order AUTH TLS, USER, PASS, PBSZ, PROT
Use of X509 cert for Client Authentication is checked
Keystore = service_ssl
x.509 Cert and private key = *******.crt
When I look in the NWA logs for default trace I see several messages with the text "Rolling back transaction for message..." plus a FILE_ERR_211
What is a FILE_ERR_211?
Thanks
Mark

hi mark,
To configure a timeout for the FTP connection, please enable the "Advanced Mode" for the respective FTP communication channel in the Integration Directory and add an entry "ftp.timeout"=timeoutSecs
(without any quotation marks) to the "Additional Parameters" section, where timeoutSecs is the desired FTP timeout in seconds.
regards
kummari

Receiver File Channel is green but not working

Hi,
I have a service which receives the data form a sender channel and send the same data after content conversion to a reciever channel.
In the communication channel monitoring I can see the log for the sender channel and the processing log is displayed even if no file is there in the specified location for the channel to pick up.
For the Received channel, no processing log is being displayed and it is not processing the file even though the same service is being used.
What am i missing here?
Can you please advice?
Regards,

Hi! Archana,
Just check once again the below mentioned steps..even though u have configured correctly...
Do one thing..
1) go to Rwb > Component Monitoring>Select Adapter Engine> below that Select TEST MESSAGE tab-> there enter your PAYLOAD and also give your scenario details once again and try to test the scenario again.
2) You can also do the same test at the Integration Engine level instead of selecting Adapter ENgine u need to seleect Integration Engine ok
3) By doing this the PI Server will took the payload directly from the RWB instead of Sender ADapter so that you can come to know where exactly you strucked whether at adapter engine or Integration Engine level.
4) Also you can check your messages in the below URL at MEssage Display tool other than SXMB_MONI and RWB in detail..
[http://Host:Port/MessagingSystem/monitor/systemStatus.jsp]
5) Also monitor your message at Ingration as well as Adapter Engine level in Message MOnitonig at RWB.
6) Try to check both the queues at SMQ1 and SMQ2.
7) If possible refresh your CACHE once at SXI_CACHE.
Regards::
Amar Srinivas Eli

Multiple Locations in Receiver File channel

Hi Experts,
Can i give multiple locations to pick the file in receiver filec hanel depending on some condition.
Thanks
Ajay Garg

Hi,
Definately you can....
in sender Communication channel check the ADVANCED SELECTION FOR SOURCE FILES.......
Thanks,
Madhu

Receive file by FTP (Server is restricted to get command only)

Dear all,
I would like to receive a file from a very special FTP server. And I am not sure if the File Adapter is able to handle this:
The FTP server I wand to connect to is a very special one. This server allows only to log in and to receive a specific file. This means that the only allowed command is
get file.dat
It is not possible to change directory or to get the directory listing. When the file was received it is not necessary (and not possible) to delete the catched file. The FTP server notices that the file was received and removes its content. This means that the file will not be removed. So it is always possible to get the file. But in most cases the file is empty (but that should not be a problem - the File Adapter can handle or ignore empty files.).
From my point of view it seems that SAP XI 3.0 SPS17 does not support to interact with this special kind of FTP Server. In RWB I can see the following error message:
"An error occurred while connecting to the FTP server 'XXX.XXX.XX.X:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 500 -3002 : command : invalid command'. For details, contact your FTP server vendor."
I connected to this FTP server manually. I get this error message when I try a command which is not allowd by the FTP server ("ls" for example). So I guess that SAP XI uses "ls" before catching the file.
Do you have an idea how I can configure the File Adpater to work with this FTP Server properly?
Many thanks
Michael

Hi Michael,
This is a tricky one. The set of required ftp commands that need to be supported to be RFC compliant is quite small (see RFC 959) but it seems that the file adapter assumes a certain minimum set (including CWD and LIST, both of which are optional).
There are several options, varying in complexity immensely:
1) Scripting the transfer process so that files are transferred to a local filesystem, from where they can be processed by XI
2) Adjusting the "special ftp server" so that it ignores commands it doesn't understand - I'm guessing this isn't possible?
3) Creating a "more relaxed" ftp JCA adapter, one that doesn't assume a certain minimum set of commands
4) Something else I'm not thinking of so early in the morning
Hope that helps a little...
Regards, MJ

Receiver file channel-FTP

Similar Messages

Maybe you are looking for