on 06-13-2013 3:56 PM
Hi
I tried searching a lot but didn’t get the answer for the following:
Scenario : Proxy to Flat File (Multiple messages creating a single Flat file using Append option).
Message mapping : 1 to 1
Target has two child nodes (RecordSet) which get created based on mapping conditions.
If any one of two node created for target the message processed without error to flat file.
But if when nodes fails to get created because of condition,
We just got the Message Type element which fails at FCC and following error message receives in message monitoring:
Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure '' found in document', probably configuration error in file adapter (XML parser error)'.
Is there a way to avoid this error ?
I tried keeping target message as optional.
In this case the following error come for integration engine:
Split mapping created no messages
Regards,
Hitesh
Thanks All,
I had find out and alternate approach.
May be not gr8 but simple.
I used 1:N mapping with a second additional message.
This message is created on opposite condition of first one.
So if my first one is invalid second one is valid and writes a one line file in any PI folder.
Thus no condition resulting in "Split mapping created no messages".
Single line append in same file doesn't create any inconvenience in my scenario.
Better than changing any mapping or configuration of working interface.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Hitesh,
I deleted my earlier post since you have already gone past the integration engine error. I found a post which is relevant to your scenario.
http://wiki.sdn.sap.com/wiki/display/NWTech/Empty-Message+Handling+-+Receiver+File+Adapter
Hope it helps!
Ambrish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Hitesh,
The way to handle such scenarios is that you use a java mapping.
Java mapping , can create a blank file without any XML element if Recorsets are not formed in message mapping. You can include java mapping in the same OM/IM after the existing message mapping so that it creates a blank file content in case recordsets are not present.
Regards
Anupam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Hitesh,
In receiver file channel processing tab put empty-message handling property to "write empty file".
Thanks,
Dhanish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.