File adapter (sender) module throws exception, but adapter proceeds again

Hello dear reader,
I wrote a module that converts a flat file into XI-XML and tested it within the file adapter. It works fine so far. But if I force the module to throw an exception to handle an erroneous flat file, the file adapter tries to proceed the erroneous file again and again. Not very nice, isn´t it?
Has anybody an idea, how to configure the file adapter to stop the processing of an erroneous file?
Thank you in advance
Yours
Frank Waskow

Hello Satish,
the weblog doesn´t describe my problem correctly. Let me show you the Audit Log from the Messeage Display Tool of the Adapter Engine:
Audit Log for Message: 06ff54a0-a258-11db-b9e2-003048226013
Time Stamp     Status     Description
2007-01-12 16:14:49     Success     Send text file "Invoice_error_wf.edi" from FTP server "HH-168:/XI_Infotag_Testdaten/EDIX/In", size 27993 bytes with QoS EO
2007-01-12 16:14:50     Error     Attempt to process file failed with null
2007-01-12 16:15:00     Success     Send text file "Invoice_error_wf.edi" from FTP server "HH-168:/XI_Infotag_Testdaten/EDIX/In", size 27993 bytes with QoS EO
2007-01-12 16:15:00     Error     Attempt to process file failed with null
2007-01-12 16:16:00     Success     Send text file "Invoice_error_wf.edi" from FTP server "HH-168:/XI_Infotag_Testdaten/EDIX/In", size 27993 bytes with QoS EO
2007-01-12 16:16:00     Error     Attempt to process file failed with null
2007-01-12 16:17:00     Success     Send text file "Invoice_error_wf.edi" from FTP server "HH-168:/XI_Infotag_Testdaten/EDIX/In", size 27993 bytes with QoS EO
2007-01-12 16:17:00     Error     Attempt to process file failed with null
2007-01-12 16:18:00     Success     Send text file "Invoice_error_wf.edi" from FTP server "HH-168:/XI_Infotag_Testdaten/EDIX/In", size 27993 bytes with QoS EO
2007-01-12 16:18:00     Error     Attempt to process file failed with null
It seems to me that the Adapter gets the error of the module, but it is not handled as an error like shown in the blog <a href="/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically:///people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically.
The adapter tries to proceed the same file again and again, till I delete it from the source directory.
Any more idea?
Frank

Similar Messages

Custom adapter module throwing exception

Hi,
We have written an adapter module (EJB) to convert a file structure into XML for conversion in XI. Using file adapter(FTP), we are getting the files converted into XML without any problem. However, when there is no file in the directory the module is throwing an exception and writing an entry into the log (polling interval is 1 minute).
The requirement is when there is no file in the directory, the adapter should keep on polling, but without generating any exception or making an entry in the log.
Can anyone help out with this please?

strange...
if a file is not found in the specified directory where your file adapter is polling, it is not possible that the control comes to the adapter module you have specified in the module chain.
have you done something unusual in your CC config i.e. added only your module in the module chain and removed CallSAPAdapter

File adapter sends return message to SOAP adapter

Hi,
I have managed to send a message using a SOAP sender adapter to a file using the file adapter. The respective message is written to a file. Though both adapters are configured to work in an asynchronous way, the file adapter seems to try to return as message. This results in an error message: "Das Interface-Mapping ... ist nicht im Laufzeit-Cache vorhanden". I have updated and checked the runtime cache. The respective mapping program is available and working, since the file adapter writes the send date to the file. So why this message?
Kind regards,
Heiko

The file adapter replies the sent message, when it is addressed in sync mode.
Set in the SOAP sender channel the Quality-of-Service to Exactly-Once to avoid this behavior.
Regards
Stefan

Issue while archiving the processed file in sender communication channel using SFTP adapter

Hi All,
In one of my scenario (File to IDOC), we are using SFTP sender communicationchannel.
we are facing an issue while archiving the processed file. Some times PI processed the file successfully but unable to archive it and in the next poll PI process & archives the same file successfully which will creates duplicate orders in ECC.
Please let us know how to resolve this issue.

Hi Anil,
Refer Archiving concepts in below links.
http://help.sap.com/saphelp_nw73/helpdata/en/44/682bcd7f2a6d12e10000000a1553f6/content.htm?frameset=/en/44/6830e67f2a6d12e10000000a1553f6/frameset.htm
http://scn.sap.com/docs/DOC-35572
Warm Regards,
DNK Siddhardha.

Why jsp throw exception , but error page can' t catch it .

I use japanese Unix.
          so must add follow
          <%@ page contentType="text/html;charset=SJIS" %>
          then error happen
          Jim Clark wrote:
          > I'm not sure what the problem is, but the following works for me in WL5.1
          > SP3 on NT:
          >
          > <%@ page errorPage="testerror.jsp" %>
          > <h1>hello</h1>
          > <%
          > String yes = "yes";
          > if ( yes.equals("yes")) throw new IllegalStateException("yes");
          > %>
          >
          > The page that shows is my testerror.jsp. Double check your page directive
          > specifying your error page.
          >
          > --
          > Jim Clark
          > Idea Integration
          > http://www.idea.com
          >
          > "yang" <[email protected]> wrote in message news:[email protected]...
          > > I use error page , but jsp have exception . error page not catch it.
          > >
          > > throw follow exception only
          > >
          > > ? 6 19 19:01:03 JST 2000:<E> <ServletContext-General> Servlet failed
          > > with Exception
          > >
          > > java.lang.IllegalStateException: Attempt to change ContentType after
          > > calling getWriter() (cannot cha
          > > nge charset from 'SJIS' to 'null')
          > > at java.lang.Throwable.fillInStackTrace(Native Method)
          > > at java.lang.Throwable.fillInStackTrace(Compiled Code)
          > > at java.lang.Throwable.<init>(Compiled Code)
          > > at java.lang.Exception.<init>(Compiled Code)
          > > at java.lang.RuntimeException.<init>(Compiled Code)
          > > at java.lang.IllegalStateException.<init>(Compiled Code)
          > > at
          > > weblogic.servlet.internal.ServletResponseImpl.setEncoding(Compiled Code)
          > >
          > > at
          > > weblogic.servlet.internal.ServletResponseImpl.setContentType(Compiled
          > > Code)
          > > at
          > > weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
          > > at
          > > weblogic.servlet.internal.RequestDispatcherImpl.forward(Compiled Code)
          > > at weblogic.servlet.jsp.PageContextImpl.forward(Compiled Code)
          > > at
          > > jsp_servlet._aeonmarket._loan._W_95_AEL032._jspService(Compiled Code)
          > > at weblogic.servlet.jsp.JspBase.service(Compiled Code)
          > > at
          > > weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
          > > at
          > > weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
          > > Code)
          > > at
          > > weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
          > > Code)
          > > at
          > > weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
          > > Code)
          > > at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled
          > > Code)
          > > at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
          > > at weblogic.kernel.ExecuteThread.run(Compiled Code)
          > >

File 2 IDOC scenario-throwing exception

Hi friends,
Please help me to resolve the following error:
when I am executing the scenario,I am getting the following error in sxmb_moni:
Runtime exception in message mapping transformation
Also observed the following error message when testing in message mapping:
Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3) com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:832) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3)(:main:, row=3, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:832) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:832) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:832) Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3)
11:58:05 End of test

Hi Chirag,
When I tested with payload from sxmb_moni,I got the following error message in MM.
RuntimeException in Message-Mapping transformation: Runtime exception during processing target field mapping /WPUFIB01/IDOC/E1WPF01/E1WPF02/KNTOBJECT. The message is: Exception:[java.lang.NumberFormatException: For input string: "CBD163"] in class com.sap.aii.mappingtool.flib3.Arithm method formatNumber[CBD163, com.sap.aii.mappingtool.tf3.rt.Context@571d571d]
Thanks,
Srinivas.

Sender File Adapter Bespoke Module Development

I have been following the How To ... Create Modules for the J2EE Adapter Engine to create a bespoke module for the Sender File Adapter.
Initially all the module does is write a message to the Augit Log. The module has been deployed to XI successfully. When I add the module to the sender file adapter the adapter is green in the adapter monitor but I get the following message in the message monitor ....
"Attempt to process file failed with Path to object does not exist at com.kk.FileAdapter, the whole lookup name is localejbs/sap.com/com.kk.FileAdapter/WriteToLog."
com.kk.FileAdapter is the package. All of the required files have been built as per the How To pdf.
Does anyone have any ideas??

Hi Satish,
Thanks for the quick response.
Using the fully qualified name I get the following error in the adapter monitor.
"Last message processing started 18:32:11 2005-09-19, Error: Module Exception 'com.sap.aii.af.mp.processor.ModuleProcessorException' found, cause: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at BANKSenderFileAdapterEAP, the whole lookup name is localejbs/sap.com/BANKSenderFileAdapterEAP/WriteToLog."
If is use the JNDI name I do not get an error in the Adapter Monitor but get the following error in the Message Monitor.
"Attempt to process file failed with Path to object does not exist at BANKSenderFileAdapterEAP, the whole lookup name is localejbs/sap.com/BANKSenderFileAdapterEAP/WriteToLog."
The rest of the message seems to be successful, only the run of the module.
Any ideas??
Many thanks
Gary

Hadeling multiple files in sender and receiver adapter

Hi ,
In my sender FTP server multiple files gets created at a same time i want to send this same files to the target FTP server am not doing any file content conversion. Just pick this multiple files at a single poll and drop it in the target FTP system.
I gave . in the as file name parameter in the sender file adapter..PI system picks all the files as separate message but if i give . in the receiver adapter itu2019s not creating the file and its giving Java exception..
Is there any other method to do this without having File content conversion... ?
Regards
Shakfie

I gave *.* in the as file name parameter in the sender file adapter..PI system picks all the files as separate message but if i give *.* in the receiver adapter itu2019s not creating the file and its giving Java exception..
For receiver adapter you have to give some file name, '.' will not work for receiver adapter. So give any temporary name just to satisfy the mandatory field. And when you selet the ASMA settings in both SENDER & RECEIVER adapter then your Receiver File adapter will write the same file name which it has picked up and NOT the one which you have written in your receiver adapter.
Note: Set ASMA setting in both else you will not get the same file name at receiver. You can see the same in blog given by Siva. You need not to create any UDF since you are not using any mapping. Just use the ASMA settings.. that's it.
> Is there any other method to do this without having File content conversion... ?
You can go through this blog for the same...
/people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-without-using-the-integration-repository
Regards,
Sarvesh

Cannot process a Fixed Field Length file using the File Adapter (Sender)

Hi -
I have checked throughout these posts and blogs but I still have not been able to find a solution to my issue. When using the File Adapter (Sender) I get a Conversion initialization failed with "xml.keyfieldName", no value found. Why would I require a key field when I am using fixed field lenghts? The file is comprised of 2 structures - 1 header and multiple details (see below). There are no key fields in the flat file that I would be able to use. Any suggestions?
011000390      Customer Americas        20080605164317 000000000000000800000008000000000016000000
12345678          100500       100500       Supplier 1                         0000000000030000002008040400
12345678          100501       100501       Supplier 2                         0000000000052000002008042100
The File Adapter is configured as follows:
Document Name = Rfchke00
Document Namespace = 'my namespace'
Recordset Name = Rfchke00
Recordset Structure = Dtachkh,1,Dtachkp,*
Recordset Sequence = Ascending
Recordsets per Message = 1
Key Field Type = String (Case-Sensitive)
Dtachkh.fieldFixedLengths = 15,25,8,6,1,8,8,8,15,3,31
Dtachkh.fieldNames = F1,F2,F3,F4,F5,F6,F7,F8,F9,F10,F11
Dtachkh.processFieldNames = fromConfiguration
Dtachkp,fieldFixedLengths = 18,13,13,35,15,3,8,2,21
Dtachkp,fieldNames = F1,F2,F3,F4,F5,F6,F7,F8,F9
Dtachkp,processFieldNames = fromConfiguration
Thanks,
Dave

Hi,
you can use the module from which u can convert your structure to
H011000390 Customer Americas 20080605164317 000000000000000800000008000000000016000000
D12345678 100500 100500 Supplier 1 0000000000030000002008040400
D12345678 100501 100501 Supplier 2 0000000000052000002008042100
Please note the extra H,D in the struture added by the module.
You can then use them as your key fieldValues.. The module should be deployed in Visual Admin and then can be used in the Module tab of your adapter CC
While writing the content conversion after that please dont forget about the added new characters
Please note also that i can find that the word supplier kept repeating in all the Dtachkp records
Please use that
Also if you feel that the field is of 13 characters and that would cause a problem dont worry... create a dummy field eg split tht 13 to two fields and use the common one as key field Value and identifier... as i see in ure case its like 500 Supplier , 502 Supplier . u can split the first 4 char and the remaing 9 char are key field value.
try this out
Rgds
Aditya

How to fetch XML file thru Sender File adapter

Dear friends,
I am having a scenario of fetching an xml file through sender file adapter. When i am testing my mapping in Test mode of message mapping it is working fine but when i fetch the real source xml file which is not having the XML namespace and Source Message type.
It is throwing error in Runtime.
At the same time when i edit the source xml file with the XML NAMESPACE & Source Meessage type it is passing successfully to the target system.
Kindly tell me friends how to solve this problem.
Take care,
Karthik

Hi Friends,
My Source XML file:
<?xml version="1.0" encoding="UTF-8"?>
<PeopleMsg>
   <Records>
      <Record>
            <FirstName>Dawei</FirstName>
            <LastName>He</LastName>
            <MiddleNameOrInitials>D</MiddleNameOrInitials>
            <IDs>
                <IDType>
                      <IDTypeName>Employee ID (Country Equivalent)</IDTypeName>
                </IDType>
                <IDs>999999999999</IDs>
            </IDs>
       </Record>
   </Records>
</PeopleMsg>
My xml file in the Test Tab of Message mapping:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Source_MT xmlns:ns0="http://kpmg.com/ibs/mdm">
<PeopleMsg>
   <Records>
      <Record>
            <FirstName>Dawei</FirstName>
            <LastName>He</LastName>
            <MiddleNameOrInitials>D</MiddleNameOrInitials>
            <IDs>
                <IDType>
                      <IDTypeName>Employee ID (Country Equivalent)</IDTypeName>
                </IDType>
                <IDs>999999999999</IDs>
            </IDs>
       </Record>
   </Records>
</PeopleMsg>
</ns0:Source_MT>

File adapter in comm.channel green, but no message collecting

Hello,
looks like this is something really at the roots.
Ok, we are in NW2004s PI 7.0.
One IDOC process is successfully implemented.
Now we started with a file to file communication!
File sender adapter is configured and shown in status green in comm.channel monitoring which would bring me to the idea that the comm.channel is configured well (To be sure we changed the directory path in the comm.channel to a wrong one which results in an error. Ok, corrected. Now all lamps are green). Comm channel is activated and polling.
But... nothing happens. The Adapter is not collecting the file in the source directory (existing) and there is no entry in monitoring on RWB or SXMB_MONI.
In Adapter monitoring all adapters except the JPR (red) are with a GREY lamp!
As we had an issue with activating the adapters (adapter monitoring before did not show any adapter (except JPR) ) two days ago we are not sure if the current issue belongs to a mistake in the configuration or in basis environment.
From XI 3.0 side we would expect that the adapter monitoring should show adapters used in green.
Do you have experience with such a behaviour?
Any help is welcome!
regards
Dirk

Hi Bhavesh,
we are near to bumping our heads against the server.
In comm.channel:
directory is : / (as simple as possible)
file name is : *.001
The file in the directory is named it_test.001 so it should be catched.
What can we do wrong?
By the way: If we change the directory to /out which is existing we have an (file is in this directory too) error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 /out: The system cannot find the file specified. '.
Cache is fine!
regards
Dirk

Soap Adapter not Picking up files from sender

Hello All,
I have configured a SOAP Adapter and started it. When i place a file in the appropriate directory, it is not getting picked up. Are there any reasons this could happen ?
I would really appreaciate it if someone can help me with this !!!
Below is the log:
17:26:27 (3812): Enabling service ToWS
17:26:27 (3812): Enabling service FromWS
17:26:27 (3823): SOAP adapter initialized
17:26:27 (3830): Starting the server at 8660:/XIservices/MXS/xmb
17:26:27 (3830): Starting the server at 4444:/XIservices/MXS/ws
17:26:27 (3807): SOAP adapter started
Below is part of the config file:
The port and path where the adapter waits for web service messages from clients.
XMBWS.WSPort=4444
XMBWS.WSPath=/XIservices/MXS/ws
XMB.SenderBusinessSystem=WLX_100
#XMB.ReceiverBusinessSystem=MD1_400
XMB.User=XIAPPLUSER
XMB.Password=********
XMB.Client =100
XMB.Language=EN
XMB.SenderInterfaceNamespace=http://xi.sap.com/wlx
XMB.ReceiverInterfaceNamespace=urn:sap-com:document:sap:idoc:messages
XMB.SenderInterfaceName=ProcesseFT
XMB.ReceiverInterfaceName=Z_SERVICE_ENTRY.ZSERVICEENTRY01
XMB.TraceLevel=0
XMB.LoggingLevel=0
XMB.QualityOfService=EO
XMB.ContentType=text/xml

Hi,
If you are using a Stand-alone J2SE Adapter Engine, you can create a SOAP adapter to pick a SOAP message from a file system and send it to the Integration Server. This is available with the XI3.0.
The configuration will look like this.
Bubble adapter java class
classname=com.sap.aii.messaging.adapter.ModuleBubble
This adapter instantiates a bubble bag for supporting
a soap file upload and sender. A bubble bag is a collection of Bubble
instances that form some processing chain of message objects.
Below parameter Bubble.Helper specifies the helper class that implements
the ModuleBubbleHelper interface. This class is used to instantiate
a bubble bag for this adapter.
Sets the bubble module helper that can instantiate your bubble bag
Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperSOAPFileSenderImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Below this line are the parameters specific to the ModuleBubbleHelperSOAPFileSenderImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
This module loads files from the local file system, consruct SOAP messages
(or SOAP with Attachments messages), and send them to the specified Web Service target URL.
Upon successful completion, response messages are stored in the file system.
Files stored can represent a plain payload, a SOAP envelope, or a SOAP with Attachments.
Plain payload files and SOAP envelope files may be packaged in MIME using some MIME headers.
SOAP with Attachments files must be packaged in MIME.
Specifies the type of the file. The available values are:
plain for plain; soap for soap envelope; swa for soap with attachments
SFSender.ContentMode=soap
Specifies the packaging
true for MIME packaged file; false for bare content
SFSender.MIMEPackaged=true
log everything (4-digit binary, where the bits indicate which
information is logged: req message, req context, resp request, resp context)
SFSender.Log=1111
The target URL to which messages are sent.
SFSender.TargetURL=http://p28848:4040/mysoaphandler
The upload directory on the local file system
This directory has six sub directories with names 0, 1, 2, 3, 4, 5, and 6. (they will be created)
The meaning of each sub directories are:
0 = inbox where you place messages to be sent
1 = trash box
2 = work box
3 = successfully completed (original) messages go in
4 = response messages come in (if any)
5 = undelivered (original) messages go in
6 = error messages come in (if any)
In these directories, the file names are used as key and there can be only one file with
the same name except in the trash box. So, when you place in the inbox a file with
the name identical to one of the files stored in another directory, it will not processed.
SFSender.Directory=/tmp/sfsender
The polling interval in milliseconds (default is 5000)
#SFSender.PollingInterval=5000
The retry delay after each failure in milliseconds (default is 5000)
#SFSender.RetryDelay=5000
The maximal retry count upon failures (default is 3)
After the maximal retry count is reached, the message is moved as undelivered.
#SFSender.RetryCount=3
The number of dispatchers to send requests (default is 3)
SFSender.DispatcherCount=1
END
Hope this helps.
@Ravi: You may call me at +91 9844167672.
Warm regards,
Venki.

XI File Adapter sending/receiving zip files

Can the XI File Adapter create a zip file to send outbound from XI and/or can it also translate a zip file inbound into XI?

Hi Kirk.
What you can do is use the OS command option on the adapter in order to unzip the file after the File\FTP adapter completes its file transfer to the specified path.One of my colleagues used a freeware zip app. that excepts an os command actions.
I know it works for file receiver but not sure about the sender. check SAP Note 801926 for more sender adapter parameters.
Regards
Nimrod Gisis

PDF files in sender file adapter

Hi,
Can XI pick up pdf files (.pdf) from a folder using File Adapter?
If yes can u send me some blogs on this?
Thanks in advance.

Hi,
It can be done by bypassing the payload from Integrationg engine.In this case this case XI will not process the PDF file but jus picks up the file from sender side and places it on the target side with no translations and message processing.No IR is required in this case.ID is enough.The file go thorough Adapter Engine it self.
Jus follow the link provided it works.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/filetofilewithoutusingwithIntegration+Repository
But if u want to read the contents of the PDF also then there is no other way than writing the Javabased Moudle and configure it .
Thanks,
Ram.

Additional Files in Sender File Adapter

Hi
I have to collect 2 files (IN.txt, IS.txt) and attach 2 files as an attachment to mail.
So I opted Additional Files in Sender File Adapter
Source Directory = D:\usr\sap\pitest\LoadTest\Output\Invoice
File Name = IN.TXT
Additional Files
File List <IS.TXT>
<IS.TXT>.namePart               ".TXT"=".TXT"
<IS.TXT>.optional                  NO
<IS.TXT>.type                       TXT
But I am able to Pick only one file (IN.TXT) from the Source Directory.
IS.TXT file is not at all picking.
Please give me your suggestion.

I reply just want to close this issue.
if file Name = Item.TXT and additional file name is ItemText.csv then configuration as following.
File List <Item.TXT>
<IS.TXT>.namePart               ".TXT"="Text.csv"
<IS.TXT>.optional                  NO
<IS.TXT>.type                       TXT
for namePart parameter, we should give the str which need to be replaced. for your example, we could give as <IS.TXT>.namePart               "IS.TXT"="IN.TXT"
replace all the file name.

File adapter (sender) module throws exception, but adapter proceeds again

Similar Messages

Maybe you are looking for