File to File Scenario - NFS

Hi,
We are busy with a very simple file-to-file scenario using NFS transport protocol.
The source directory that I enter was as follows i.e. //xx.xxx.xx.xx/directoryname, but I keep on getting a configuration error on the adapter engine with the following message: 'Configured source directory '//xx.xxx.xx.xx/directoryname' does not exist'.
What are the rules for connecting to a different server using file systems (this is not on our PI server)?
I hope someone can assist with this.
Regards,
De Wet

Hi,
>> What are the rules for connecting to a different server using file systems (this is not on our PI server)?
you would required FTP server to connect with PI. for testing purpose you can dowload Guild FTP server.
If using NFS place the file to PI Application server by using /nSXDA_tools and /nAL11
>> 'Configured source directory '//xx.xxx.xx.xx/directoryname' does not exist'.
Cross check your source directory name, file name in the sender commuincation channel.
Difference b/w NFS and FTP
NFS is used when the file folder is available on the XI Server.
NFS is used when we required to poll the files from local machines.
NFS: should be faster then FTP.
FTP: when it is at remote side.
FTP: when we required to poll the data from the FTP server which are in the remote side or outside of the firewall.
FTP: If you need logins/authorizations etc,go for FTP
Regards,
Abid

Similar Messages

Test a file to fle scenario using NFS in 7.1

Hi Experts,
I have one small confusion...
when testing a file to file scenario in PI 7.1 using NFS...im wondering what path should i specify for the source directory?
cos earlier in 7.0, i would have given /usr/sap....
but now i dont think 7.1 has visual admin..so what shoud i so?
ne suggestions?

Hi Ravinder ,
cos earlier in 7.0, i would have given /usr/sap....
but now i dont think 7.1 has visual admin..so what shoud i so?
> there is nothing to do with visual Admin ..
Just give a sharable folder path to pick and post the file as you were giving earlier. If your concern is file path ask basis person to help you.
Regards,

File to file scenario but transport protocol is NFS

send me step by step screenshot for file to file in sap pi 7.1 scenario but transport protocol is NFS

Hi,
Send your email id.
Sreeni.

File to File scenario

Hi,
I have a problem in file to file scenario in which the file is not getting transferred from source to target.
Source communication channel - Transport protocol - NFS | Process mode : Delete | The file is picked but not able to delete from the directory.
Error: File: d:\test\file.txt deleting after processing failed - retry
The file is not transferred to target is it because of this CC is not able to delete the file. Does windows also have any authorization issue if so how should one check the authorization. I have the admin access of my system.
Thanks.

Hi,
Firstly, Since the scenario works perfectly while using Test mode, so all your design & configuration are OK.
Now, there can be Two reasons why PI is not able to delete the file and process it (during Delete Mode):
(The Problem will persists if you use Archive Mode also)
Prob 1. The directory is write protected or read only
Prob 2. The file is write protected or read only
Solution:
If Unix System
Soln for Prob 1. - go to the directory structure
for ex: if directory where file is kept is /staging/Interface/PI/Test/inbox/
then go to /staging/Interface/PI/Test/ and give command ls -lrt
It will show the directory names with permisions.
use chmod 777 inbox and the permissions willl be changed ( drwxrwxrwx )
Soln for Prob 2. - Get inside /staging/Interface/PI/Test/inbox/ and give command ls -lrt
if the file does not have authorizations as (-rwxrwxrwx) give chmod 777 <filename> and then give command touch <filename>
If Windows System
Soln for Prob 1. - Goto the directoty and right click on the folder and deselect the Read Only Checkbox.
Soln for Prob 2. - Right Click on the file and deselect the Read Only Checkbox
Try again and the scenario will work surely. Let me know if any issues.
Regards,
Souvik
Edited by: Souvik Chatterjee on Mar 14, 2011 8:14 AM

Ftp for file to file scenario

Hi Experts,
I have a simple file to file scenario where file has to be sent to ip address 10.1.2.3 (receiver machine).
So first I tried using NFS , sharing a folde ron 10.1.2.3 , but the sender channel in XI showed error and was unable to find the path.
So I installed Guild ftp pro on 10.1.2.3 .....the scenario was nw working fine...
all was well untill I discoverd
when i had to send a file from 10.1.2.3 wher the file name was fixed with the time stamp
that when I use filename*.txt in the sender channel , the sender channel shows error in the communication channel monittoring..
further posts on sdn concluded that wild character * cannot be used in guild ftp...
ne idea on how I can proceeed further??
are there other softwares like guild ftp?
help appriciated..
Regards,
Teja
Edited by: Ravindra Teja on Jan 10, 2012 3:14 PM

I had good experiences with WSFTP and Filezilla. You may try them.
>>further posts on sdn concluded that wild character * cannot be used in guild ftp
This is strange limitation of an FTP server.
Regards,
Prateek Raj Srivastava

How to specify source directory in File sender adpate using (NFS)?

Hello experts,
I am doing File-PI-Proxy scenario.
Input file is available on machine which is within the Network area and FTP is not available on that machine.
For this reason I am using the NFS Transport Protocol.
In ID File sender I have specified Source Directory:-
IP Address\Directory
I am geeting the Error in RWB as 'Configured source directory '
IP Address\Directory' does not exist'.
Please suggest how to specify the Source Directory path.
Regards,
Jagesh

Hi,
If you want to use NFS protocol, then the file needs to be within the a folder in the XI server and not outside it, In your case if you need to use the file in a different machine which is on a network then try to use the FTP protocol.
Refer this blog:
/people/shabarish.vijayakumar/blog/2006/08/01/along-came-a-file-adapter-mr-ftp-and-rest-of-the-gang which shows the details of how you can install a local FTP and use it
Regards,
Nithiyanandam
Edited by: Nithiyanandam A.U. on Mar 18, 2009 10:43 AM

Issue during File to File Scenario

Hi Folks,
    I am doing a file to file scenario in which I'm using the Transport protocol as FILE (NFS) and the source directory I'm trying to use is on my local system which is shared. But still i'm getting an error "Configured source directory '
1693.29.52.01\File\Input' does not exist" during the communication channel monitoring.
Regards,
   Santosh

Hi, santosh
rajesh is right   NFS stands for network file system which means your PI server only andf not any shared location
If you want file to be picked up from your local machine then create a FTP(file Transmission protocol ) location on your machine and create a shared folder there . this folder should have all the rights(read and write)
In your sender communication channel select option FTP in place of NFS
give details of your FTP location,user credentials then only your file will be picked
regards
sandeep

FILE 2 FILE SCENARIO

Hi All..
In file to file scenario I want to send the data from a flat file.
I used File content conversion perameters for the same.
My flat file has more than 1 record.
I have given all the file content conversion parameters as per the BLOG file 2 file Part#2.
But It will take only the first record.
I used transfer protocal type NFS not ftp
Can any one plz expalin where I am wrong.
Regards
Diva

Hi..Jai
I will keep row occurence as 1.1.
No I will make it to 1..unbounded.
And let u know if any problem occurs...
Assigned full points for that..
thanks & Regards
Diva

File-PI-RFC scenario with extraction of contents in the filename

Hi All,
I am working on File to RFC scenario.
Here the file name is like 'ABCD_XYZ_1234_DATE' where the date is in yyyymmdd format.
I have to read this filename & the date in the filename is to be mapped with one of the RFC parameter.
Also how would I trigger the Interface if the file resides in PI server or on local mchine.
How to configure the processing parameters in sender comm channel if I want to read the file after every 15 mins?
Thanks,
Amit Patil

Hi,
By writing simple UDF in your mapping you can Acheive this
Try this Once
DynamicConfiguration dynamicconfiguration = (DynamicConfiguration)param.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File", "FileName");
String MyFileName = dynamicconfiguration.get(key);
String str[] = MyFileName.split("_");
return str1[1];
Map this to the date parameter(RFC) in the mapping .
If the file resides on Local machine then you can use FTP and if it is on PI server then NFS as Transport protocol.
If you want read the file for every 15 min there are 2 options
1) Set the poll interval time to 900 sec
2) Configure ATP in RWB
Configuring ATP in RWB :
http://www.dataxstream.com/2010/11/configuring-availability-time-planning-in-sap-pi/
Thank & Regards,
Deepthi

File-Xi-File scenario donu00B4t work.

Hi!!
We have a poblem with a FILE-XI-FILE scenario via NFS. We have a Flat File in a Xi directory (AL11) . The first process work correctly. The file is deleted from this directory and mapped to a XML file into Xi. SXMB_MONI shows the message is correctly (green flag). But i can´t generate a Receiver file. We want to create a new file in /tmp directory of Xi. For do this one , we have a Communication Channel type File, with NFS option.
Someone can help me?¿
Thanks for all.

Hi! vishal!
Thanks for your fast reponse!
Adapters are configured correctly. I throw a test in Integration Builder and encountered a fatal error in step interfase determination & mapping.
"Runtime error
During the application mapping com/sap/xi/tf/_FILE_TO_FILE_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: Fatal Error: com.sap.engine.lib.xml.parser.Parser~"
The trace saids.
<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace> <Trace level="2" type="T">......attachment XI_Context not found </Trace> <Trace level="3" type="T">Das Mapping wurde bereits in der Interface-Ermittlung bestimmt. </Trace> <Trace level="3" type="T">Object ID of Interface Mapping E5F0ADEF913F39CF82BC520FEBF6072A </Trace> <Trace level="3" type="T">Version ID of Interface Mapping FBF0D0004FBC11DABCBBE9C10A1F030C </Trace> <Trace level="1" type="T">Interface Mapping http://gencat.net/ics/xi/facturacio FILEINPUT_TO_FILEOUTPUT_INTERFACE </Trace> <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_FILE_TO_FILE_ </Trace> <Trace level="3" type="T">Dynamic configuration is empty </Trace> <Trace level="2" type="T">Mode 0 </Trace> <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_FILE_TO_FILE_. </Trace> <Trace level="3" type="T">Load fbf0d000-4fbc-11da-bcbb-e9c10a1f030c, http://gencat.net/ics/xi/facturacio, -1, com/sap/xi/tf/_FILE_TO_FILE_.class. </Trace> <Trace level="3" type="T">Search com/sap/xi/tf/_FILE_TO_FILE_.class (http://gencat.net/ics/xi/facturacio, -1) in swcv fbf0d000-4fbc-11da-bcbb-e9c10a1f030c. </Trace> <Trace level="3" type="T">Loaded class com.sap.xi.tf._FILE_TO_FILE_ </Trace> <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._FILE_TO_FILE_ </Trace> <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_FILE_TO_FILE_ </Trace> <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:66) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:77) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy32.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:130) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7)(:main:, row=1, col=7) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2009) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2657) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2009) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2657) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 3 more </Trace> <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_FILE_TO_FILE_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) </Trace> <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_FILE_TO_FILE_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy32.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:66) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:77) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy32.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:130) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7)(:main:, row=1, col=7) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2009) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2657) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2009) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2657) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 3 more </Trace> <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
Best regards....Help!!!!

Simple (File-XI-File)scenario

Hi,
I am going through Venkat Donela's simpe (File-XI-File)scenario Part1 and part2.
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1345. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
But my XI did not pick up the input file. I use SXMB_MONI and look at the message monitoring. It says "No message has been selected'. I don't see "adapter monitoring" option on my "Runtime WorkBench".
Is there anybody could tell me how I can monitor the scenario execution? I checked the every step states in Venkat Donela's sample.
Any comments and advice will be highly appreciated.
Meiying

Hi,
The best way to check if your file is being picked is to set the "Processing Mode to Delete"....So then you will know if your file is actually being picked...
Also go to Message Monitoring of RWB and check for the status. Because if you have content conversion problems then it will show there in MDT(Message Display Tool under Message Monitoring).
And if you are using NFS connection for Sender File Adapter, try to check for the checkBox "ReadOnly Files".
Pls go through the explanation of a simmilar scenario that i have explained below and compare it with what you have done..
Please go thru the following links and clear all your doubts.
Communication channel:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/65/b11c409ce22402e10000000a1550b0/frameset.htm">Assigning Communication Channels</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/2b/d5653fd1d3b81ae10000000a114084/content.htm">Communication Channel</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm">Configuring the Sender File/FTP Adapter</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm">Configuring the Receiver File/FTP Adapter</a>
Receiver agreement:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/56/02e63f48e58f15e10000000a155106/frameset.htm">Receiver Agreement</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/c1/5194426b44c56ae10000000a155106/frameset.htm">Creating a Receiver Agreement</a>
Sender agreement:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/db/73e03fc2269615e10000000a155106/frameset.htm">Sender Agreement</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/22/522041cfb7f423e10000000a155106/frameset.htm">Creating a Sender Agreement</a>
For detailed info, I would suggest that you go through these weblogs:
<a href="/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1">Introduction to simple(File-XI-File)scenario for Starters</a>
<a href="/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2">Introduction to simple (File-XI-File)scenario for starters part2</a>
I hope it helps.
Regards,
Abhy
Message was edited by: Abhy Thomas

Sample Scenario For File To File.

Hi All,
I just wanted to know if I can create a sample File to File scenario using a file placed in local hard disk i.e. in C: Drive (Source) and D: Drive (Target)?
If no, please suggest me some steps to do a File to File scenario without accessing any other servers or systems?
Regards,
Sreedhar, Av

Hi Sreedhar,
Yes its possible,You can install your own FTP in your system and can use the same as file sender and receiver.You have to choose FTP option instead of NFS and specify those FTP log on details in Your communication channels.You can make use of GUILD FTP which is free ware.
Please follow the below thread that helps you in doing that
File Adapter : Access Local Folder
Thanks,
Ram.

XI 3 File to IDoc scenario - Still referencing Old Logical system

Hi
Dont know if you can help. I have a file to idoc scenario using XI 3 to R/3 4.6c system.
I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
Regards
Daniel

hi daniel...
this thread wud answer ur query....
Re: IDOC Payload
regards..
vishal

Step by Step Guide Details for RFC to File and File to RFC scenario

Hi Guru's
Good day to you. I am tyring to develop some scenarios based on RFC adaptor. so i want to start up with basic scenarios like RFC to File scenario(Here i just want to pull some data from SAP using RFC and put it in destination folder as an text file) and FILE to RFC scenario (Here i just want to take some data from the file and update into SAP).
For doing these scenarios i would like to request you people to send me the step by step guide which explains me about the complete steps of configurations required to do the RFC to FILE scenario and FILE to RFC scenario.
I found some scenarios and i am in confused state. so i request you to please put your experience to help me out.
thanks in advance.
Regards
Raj

Hi Aaron,
I don't know your scenario and your ECC and PI versions but I learned how to use ABAP Proxy more than 1 year ago with the following tutorial:
Edit--> The forum doesn't allow me to post external link, just search "ABAP Proxy Communication Scenario" in google and visit the 1st result
The way to develop ABAP Proxys has changed a little if your PI is 7.1. In the ECC side, the transaction SPROXY looks much better too if you have a recent version of the ECC.
Edited by: Marshal on Oct 8, 2009 5:08 PM
I've found that SDN Document. Maybe the scenario is not the most simple to start with ABAP Proxy but is very well documented and is for PI 7.1. The document also handles the inbound and outbound proxys
[http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c00ca32e-f991-2b10-f5be-97114bd2b08f&overridelayout=true]
Edited by: Marshal on Oct 8, 2009 5:22 PM

Regarding Background Job scheduling for file to file scenario

Hi Guru's
Good morining all of u
I have one doubt on ...
can we do background job scheduling for file to file scenario?
Please give me response as early as possible.
thanks and regards
sai

background jobscheduling for file adapter...
you can schedule the file adapter according to your requirement as follows:
In the Communication Channel Monitoring Locate the link Availability Time Planning, In Availability Time Planning, choose the Availability time as daily and say create, give the time details, select the communication channel in your case file adapter , goto the Communication Channels tab and filter and add the respective channel, save it
/people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-

File to File Scenario - NFS

Similar Messages

Maybe you are looking for