Recevier adapter empty message-handling ignore

Hi all,
I configured file receiver adapter with file content conversion (comma separated).
In processing parameters Empty-message handling is set to Ignore.
Payload that is in message generated from SAP is:
<?xml version="1.0" encoding="utf-8" ?>
<mt_ap_invoice xmlns:prx="urn:sap.com:proxy:DES:/1SAI/TAS128FC2C2C3C8E901DC22:700:20 08/06/25" />
There are no any data that is filling structure (structure main node is defined as 0...unbounded) and still empty file with 0 bytes is created.
Please can you tell what is wrong in this setup as In case of empty message I don't want that file is generated?
Regards,
Nenad

- open Integration Builder
- open your file receiver adapter
- go to tab Processing
- change Empty Message-Handling to 'Ignore'
Cheers,
André

Similar Messages

Receiver File adapter - 'Empty Message Handling' option to ignore not worki

Hi,
I am trying to create the Files in receiver based on condition.But I am gettiung error in communication channel when there is no payload. Receiver I am usuing FCC and processing tab I selected -'Empty Message Handling' option to ignore .
one source -> Target 1 (0..1 occurance in signature tab changed, message mapping and operation mapping)
and Target 2 (0..1 occurance in signature tab changed)
and I put the message type level condition. While creating first message If did not create the Message type in my maaping still my Receiver File communication channel is giving error. even thow I my receiver interface occurance is 0..1
Right now I am in PI7.1 and SP7 is the bug for support pack do I am missing any thing. and do I need to upgrade any nwe patch. appreciate your help.
Regards,
Venu.

Hi,
here is the my requirment one source -> two target interfacess (0..1)
If u have 2 target interfaces,then this is not suffice..... u should make it as 0..unbounded both in operation mapping and message mapping.
But based on ur requirements posted above i guess u have only one inbound interface at a time based on some conditions....
But,
<messages>
<messages1>
based on condition first message type not created in mapping.
<messgaes2>
The error u r getting is because.... u want only one interface in target at a time....
Then u should not generate Message1 also in the target.
So avoid mapping to message1 if u want only message2.
If both message1 and message2 are created in target means... it is triggering for two interfaces.... so avoid one message1 or message2... based on some conditions u have..
Still nt solved do post...
Babu

Receiver AS2 Adapter : Empty Message Handling

Hello Experts ,
We are trying to work on following requirement .
File -> PI -> AS2 ( File) ( We are using Pranke to drop our message to the receiver system) (MDN ack too is in place )
There are times when none of the source records are valid and we have an empty payload post mapping.
In AS2 adapter we are using StrictXML2Plain.
Scenario works fine for all target messages which have data and a file is created at the receiver end. MDN ACK works fine too.
Problem is when we have empty target payloads , We get following error in communication Channel monitoring.
Information
SEEBURGER/AttribMapper: Finished succesfully, 1 properties set or deleted
Information
MP: processing local module localejbs/ModuleProcessorExitBean
Information
Message entered AF MP exit bean and will be passed to the JCA adapter now.
Information
SEEBURGER/AS2: Received order from system.
Error
Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond # , SEEBURGER AS2: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond #
Error
MP: exception caught with cause javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond # , SEEBURGER AS2: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond #
Error
Adapter Framework caught exception: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond # , SEEBURGER AS2: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond #
Has anyone handled such situation ? Is there any workaround at the SAP end to handle this issue ?
Or is this to be handled at the Pranke end ?
Attaching the Seeburger AS2 monitor error as well for empty messages ,
State
Error on send, will be retried
Status Description
Could not deliver as2 message to partner: org.apache.commons.httpclient.NoHttpResponseException: The server as2gw.pranke.com failed to respond # null
Little urgent and your expertise is appreciated PI geeks
Sayalee

Hi,
here is the my requirment one source -> two target interfacess (0..1)
If u have 2 target interfaces,then this is not suffice..... u should make it as 0..unbounded both in operation mapping and message mapping.
But based on ur requirements posted above i guess u have only one inbound interface at a time based on some conditions....
But,
<messages>
<messages1>
based on condition first message type not created in mapping.
<messgaes2>
The error u r getting is because.... u want only one interface in target at a time....
Then u should not generate Message1 also in the target.
So avoid mapping to message1 if u want only message2.
If both message1 and message2 are created in target means... it is triggering for two interfaces.... so avoid one message1 or message2... based on some conditions u have..
Still nt solved do post...
Babu

Empty-Message Handling is not working in receievr File Adapter

Hi All,
I have selected "Empty-Message Handling" = 'Ignore'in Receiver File adapter, but still empty files are creating in target directory.
Message mapping generates output based on the conditon, if the condition is 'false' mapping will generate empty file (no data is being mapped).
Why Receiver file adapter is processing empty fiels even i set 'ignore' empty fiels in configuration (ID)?
Hoe can i manage not to place empty fiels in target directory?
File type is '.txt'
Your help would be appreiciated greatly.
Thanks,
Rajesh

Not sure why is it not working. Make sure the channel is activated and cache is refreshed properly. But as a workaround you may use OS script checking for size of message and deleting it or configure a BPM to avoid the file creation. Or else an adapter module as shown
/people/gowtham.kuchipudi2/blog/2006/01/13/stop-creation-of-an-empty-file-from-file-adapter-using-module
Regards,
Prateek

Empty Message Handling with Receiver File adapter

Hi,
We were using the "Empty-Message-Handling" (status set to Ignore) of Receiver file adapter to stop a 0 KB file from being written to the specified directory.
However, inspite of this, a 0KB file continues to be written.
The specifications are given below-
File Construction Mode - Add Time Stamp
Put File - Directly
Empty Message Handling - Ignore
Maximum Concurrency - 1
File Type - Binary
Can anyone please help with this.
Thanks and Regards,
Shiladitya

HI,
In one of thread the same problem was coming. Just look at the thread.
Receiver file adapter creates empty files, Empty-Message Handling SP19
Or
Follow the weblog for the same requirement.
/people/gowtham.kuchipudi2/blog/2006/01/13/stop-creation-of-an-empty-file-from-file-adapter-using-module
Thnx
Chirag
Reward points if it helps.

File Receiver Adapter - writes empty message although ignore flag is set

Hi,
i have an file FTP receiver channel configured with content conversion. I also have set the "Empty-Message-Handling" flag to "Ignore", so empty messages with 0 kb are not written to the FTP server.
My problem is now: empty file are written to FTP server although this flag is set to "Ignore".
For example: A message with the following content arrives at my receiver adapter:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_ArticleMaster xmlns:ns0="http://ihle.com/tyredating/core"></ns0:MT_ArticleMaster>
The resulting file has 0kb.
Does anyone have an idea why empty message are not getting ignored by this setting? Although the flag is set?
Thanks in advance,
MS
System: PI 7.1 SP 7
Edited by: Manuel Schlestein on May 12, 2009 5:17 PM

>
Manuel Schlestein wrote:
> Hi,
>
> i have an file FTP receiver channel configured with content conversion. I also have set the "Empty-Message-Handling" flag to "Ignore", so empty messages with 0 kb are not written to the FTP server.
>
> My problem is now: empty file are written to FTP server although this flag is set to "Ignore".
>
> For example: A message with the following content arrives at my receiver adapter:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <ns0:MT_ArticleMaster xmlns:ns0="http://ihle.com/tyredating/core"></ns0:MT_ArticleMaster>
>
> The resulting file has 0kb.
>
> Does anyone have an idea why empty message are not getting ignored by this setting? Although the flag is set?
>
> Thanks in advance,
> MS
>
> System: PI 7.1 SP 7
>
> Edited by: Manuel Schlestein on May 12, 2009 5:17 PM
ideally the file adapter will expect a message with no content in it. so i suggest you use a simple java mapping to check if there is any content between the tags, if there is no content then write out an empty string to the outputstream else pass the same inputstream out

Receiver file adapter creates empty files, Empty-Message Handling SP19

Hello,
We have just upgraded the system to SP19.
One of the new features is that it should be possible to determine how XI messages with an empty main payload are to be handled in the receiver file adapter.
If the parameter Empty-Message Handling is set to 'Ignore' no file should be created if the main payload is empty. In our case an empty file (size 0 kb) is still created even though the main payload is empty and the flag is set to 'Ignore'.
Has anybody experienced the same problem?
// Best regards Hans

This should work:
Use your own adapter module that parses incoming message and checks if it has any record sets in the document. If it does not have any record sets, then set the message to empty and then give this modified message to File receiver.
For example, see the example code below:
Module imports..
Audit log import..
DOM imports/SAX imports..
public ModuleData process(ModuleContext moduleContext, ModuleData inputModuleData) throws ModuleException {
          try {
               // get the XI message from the environment
               Message msg = (Message) inputModuleData.getPrincipalData();
               AuditMessageKey amk = new AuditMessageKey(msg.getMessageId(),AuditDirection.INBOUND);
               Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"RemoveRootTag: Module called");
               XMLPayload payLoad = msg.getDocument();
               Document doc = parseXmlFile(payLoad.getInputStream());
               if(doc != null){
                    if(!doc.getDocumentElement().hasChildNodes()){
                         Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS, "Document is empty!!");
                         payLoad.setContent("".getBytes());
                         msg.setDocument(payLoad);
               // provide the XI message for returning
               inputModuleData.setPrincipalData(msg);
               } catch (Exception e) {
               // raise exception, when an error occurred
               ModuleException me = new ModuleException(e);
               throw me;
               // return XI message
          return inputModuleData;
     private Document parseXmlFile(InputStream xmlpayload) {
          try {
               DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
               factory.setValidating(false);
               //        Create the builder and parse the file
               Document doc = factory.newDocumentBuilder().parse(xmlpayload);
               return doc;
          } catch (SAXException e) {
          } catch (ParserConfigurationException e) {
          } catch(IOException e){
          return null;

Empty File Handling in xLink adapter

Helloo Experts
I am doing a scenario, which creates an empty file(when some mapping condition doesnt satisfy).
I dont want to write this empty file in the target directory.
This can be handled if a file adapter is used, but I am using a SOAP AXIS adapter, so I dont know how to handle this here.
I alaso tried using the StrictXml2PlainBean to avoid the creation, it creates 0 documents and a 0kb empty file.
Can anyone please let me know how this can be solved????
Also if some one has done this empty file handling in J2SE file adapter...can you tell how it was done.
Thanks a lot!!!!!!
Regards
Shobha

Hi Gabriel,
You can write a simple script to copy a file from source folder to target in case the fiel size is ZERO bytes. The script will not copy the file if the filesize is more than zero bytes, This will be processed normally by PI server. You can call the script from sender communication channel parameter : "RUN OS command before message processing". Could you please specify the Operating System (OS) you are using in your PI server.
Regards
Anupam

BPM handle empty message in send step

Hi, Friends:
I have a following BPM sceario(PI7.1 EHP1)
It mainly has following steps:
Receive -> Transformation (Multi-Mapping) -> Fork (4 branches: one send step each branch)
The multi-mapping result is to generate 4 types of messages based on logic.
Sometimes all 4 types of message generated, and sometimes only one type of message generated.
When there is a message not generated, the send step generate error which is not caught in exception branch.
I searched forum, so far not lucky to find solution.
Any idea how to handle empty message (do not send it) in send step?
Regards
Liang
Edited by: Liang Ji on Dec 7, 2010 8:42 PM

Hi, Abhishek:
The reason to use Fork is that all the branches can be reached.
By using switch, it only judge one input value and only one condition turns true.
Actually in most cases, the number of my input value is more than one, saying two or more message types generated.
And this is not multi-line situaion, because the messages generated are different types.
Your reply remind me to add switch inside fork.
Regards
Liang
Edited by: Liang Ji on Dec 8, 2010 5:32 PM

Empty File Handling : Do Not Create Message

Hi,
I have set this option in Sender CC - file.
Parameters --> Processing.
I dont want to pass file to reciever , when file is empty.
Will the above option "Do Not Create Message" do the trick.
OR do i need to choose something else??
-santosh.

Santosh,
Yes. The trick will work for empty file handling.
When your incoming file is empty then will be no xml message posted to IE and hence receiver will not get any message.
FYI: Also you can use skip empty files which will do the same but here the files will remain in your source directory.
Regards,
Prasanthi.

File adapter problem - message in RWB HOLDING msg status

Problem in XI File adapter recver comm channel.Getting msg in RWB Adapter Engine HOLDING status.
1. No explaination in RWB Details tab, of why status Holding.
2. File does not get created, because of Holding status.
3. Cannot Resend or Cancel in RWB the message.
<b>Sometimes the msg goes through and other times does not and is stuck.</b>
File Adapter Parms set as:
Connection Mode: Per File Transfer
Transfer Mode: Text
File Adapter setting Max concurrency = 1 would that have anything to do with it?
File Construction Mode:Create
Put Name: Direct
Empty msg-handling: Write Empty File
Type: Text
<b>Any ideas Why holding? and Where to see more details. </b>

Hey
exact same issue has been discussed today on SDN.anyways have a look at the following blog
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
Thanx
Aamir

JMS adapter: Adapter specific message attributes

Hi,
I have a synchronous SOAP to JMS (MQ series) scenario where Im using sync/async bridge (without BPM).
I need to correlate the message being put on JMS queue (JMS receiver adapter) and the response (JMS sender adapter).
The standard receiver JMS adapter only allows the JMS correlation ID to be set to one of three different values (excluding NULL). 2 of these (reference and conversation ID) will be empty in my scenario, leaving me with only the XI message ID. This ID however exceeds the length of ie. the JMS correlation ID and thus isnt suitable for correlating anything using the field JMS Correlation ID.
NB: it is of no use to try and set the conversation ID at mapping time (using container object) since the changed value only is available during mapping execution.
Surely one way of setting the conversation ID would be to use an adapter module in SOAP sender, but this is not an option. Also the sender system will not provide one either.
Now the problem isnt setting the JMS correlation ID dynamically at runtime (this is achieved without trouble using the dynamic configuration API with the key DCJMSCorreleationID). The problem is to actually have XI correlate the request with the response.
Since the JMS collelation ID is smaller than the XI message ID and the conversation and reference ID isnt available, what I figure is that I need to find a MQ message property to use and then use the Set MSProperty to part instead this property surely needs to be large enough to contain the XI message ID.
So what I did was I looked in http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqwak.doc/js50938.htm
where a list of fields in the message descriptor is available figuring I can just use one of these. Looking through the list I notice the field MDRQ (Name of reply queue, 48-byte character string) should be able to hold the XI message ID. So I add MDQR in the Specify additional JMS message properties and set the Java Type to String and also enter this field in the Correlation Setting of the receiver JMS adapter.
Runtime:
When looking in MDT I see:
New JMS message will be correlated with the XI message. Correlation rule: XI_MESSAGEID, correlated property: JMS property MDRM, correlation value: 36158680-5a0c-11dc-8c14-000f203cd3c8
I looks like a success! No data is however set in the field when looking at messages being put on MQ.
If I increase the trace level of the JMS adapter I can see (in defaultTrace) the following:
Cannot read the switch setting for property name DCJMSStringProperty0, switch name dynConfigDCJMSStringProperty0. It is switched off.
What does this error mean?
I have of course clicked Use adapter Specific Message-Attributes and also the Specify additional. In other words everything look ok in configuration.
Since Ive also put a check mark in Fail if adapter specific message attributes is missing I can see that I successfully put a value (using dynamic conf. at mapping time) in the field... but still something isnt right the value of the property never reached MQ.
Now Ive tried with a couple of fields in the message descriptor from the previous URL. XI complains all the time.
Anybody got some ideas?
Best Regards,
Daniel

Hi Vijay,
Thanks for your replay,as per your input i creted dynamic configuration method,
i taget structure luks like this
   <Data>
       <Mesage>
             <gl_update>
                  <header>
                        <ean1>
                        <ean2>
                  </header>
              <gl_update>
       <Message>
i written UDF and mapped to header element gl_update,
but i am getting below error message in MONI
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_ ffjms_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:MT_jms_ _a</SAP:P3>
<SAP:P4>sync_out/Data/Message/ GLUpdate. Values missi~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_ ffjms_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_jms_ asyncout/Data/Message/ GLUpdate. Values missi~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
i want to know i mapped to UDF to GL_Update is is correct, to which element i have to map.
i think there is no prob with UDF,its executing ,giving warning messages
help me on this,
Regaards
Raj

Problem with „Empty-File Handling" in PI 7.11

Hi,
Iu2019m working in PI 7.11 with file adapter, Sender CC, option: Empty-File Handling: Process Empty Files.
What I want to do is giving target file the system-date, if the source file is empty.
But I always get a mapping error in RTWB: Premature end of file.
It seems that the payload is empty.
Any idea?
Thanks a lot in advance!
Rene Dong
Edited by: Rene Dong on Aug 31, 2010 4:20 PM

What I want to do is giving target file the system-date, if the source file is empty.
The error you are getting makes sense. You should do a check in the mapping, if the payload is empty then use brute force to pass the system date.

Create Empty Messages --Not working

Hi All,
Iam trying to perfom file to file with content conversion
when there is an empty file is coming from source, i have to process it and create the file in target with empty file.
I setup the setting at sender file adapter saying that process empty file and in receiver file adapter i said that create empty messages.
i used FCC at sender side and it is failing in MONI saying that Parsing an empty source. Root element expected!
Regards

Hi,
i used FCC at sender side and it is failing in MONI saying that Parsing an empty source. Root element expected!
If there is an empty file, then there is no XML available for parsing. So, in this case your mapping will fail.
The best option is to write Java or XSLT mapping or write a module which will check for the empty file, and if that's the case it will write an XML with no values in the contents / fields.
Hope this helps.
regards,
Neetesh

Procedural message handling with Multiuser?

I am developing a multiplayer game. I am having issues structuring how to handle incoming messages from the Multiuser server to the client. At the moment I have a default message handler function that references the message subject using jump lists (case) and executes functions accordingly. However this doesn't seem efficient. For example, when I first connect to the server, I want the client to request a character's data from the server, which is fine and already implemented. The incoming message handler in the client checks for a "GetCharacterData_Response" and when it's received, I then need to request map data from the server, which is also fine. Here's some example code I have currently:
This is within the incoming message handler.
case (message.subject) of
"GetCharacterData_Response":
     _global.Character = message.content
     _global.Multiuser.sendNetMessage("system.script", "GetMapData_Request", message.content.mapCoords)
"GetMapData_Response":
     _global.Map = message.content
end case
However I may not necessarily always need to request map data directly after receiving the character data. I feel the way I am currently using this structure just isn't efficient and I will be doubling up on a lot of code because there is such a diverse range of situations of when to obtain data and then what to do with that data. Do you guys have any suggestions or feedback regarding this?
Thanks in advance.

If you want character data and map data, why not request both at the same
time (or just request one if you only need one)? If you need to make sure
you have character data before map data, then maybe have a check if
character data is empty not to request map, etc.
I've found it pretty efficient to code everything as object oriented and
modular as possible. Then you can set up your logic and use all of your
functions as need be. You might have extra code in doing that, but the
versatility and sleekness will pay off big time. The computer can execute
insane amounts of code per millisecond, so don't worry too much, although
cutting down on network traffic is cool.

Recevier adapter empty message-handling ignore

Similar Messages

Maybe you are looking for