Seeburger X.400 messages stuck in SXMB_MONI

[peter_wallner2]

Dear experts,

I am getting order messages from a partner who sends those via X.400.

So I do have a Seeburger X.400 sender adapter:

Payload Mode: "Attachment"

Attachment alias: "attachment"

Encoding: "binary"

MODULE: only "localejbs/CallSapAdapter"

But the messages are always stuck in SXMB_MONI!

I get the MONI error:

Runtime exception occurred during application mapping com/sap/xi/tf/_X_ORDERS_TO_I_ORDERS02_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Parsing an empty source. Root element expected!

But when I look at the payload the XML file is displayed correctly, it is encoded in ISO-8859-1.

Where I double click the payload entry in MONI it says "attachment#0001 ( application/octet-stream )" though. Normally it should say

"attachment#0001 (application/xml)"!

I have already taken the XML message and tested it in message mapping and operation mapping and both work fine!

Does anyone have an idea? Why would PI not find the root element?

Thank you very much for any hints and best regards,

Peter

[Former Member · Accepted solution]

Hi,

There should be a module processor for converting the file type. soon after the classifier module make use of that module.

Regards,

Pavan

[peter_wallner2 · Accepted solution]

Hello Pavan, Hello experts,

I solved the problem by using the Seeburger "CharsetConversion"-module

Module

localejbs/Seeburger/CharsetConversion	Local Enterprise Bean	conversion

Configuration

conversion	sourseDest	attachment#0001
conversion	targetEnc	ISO-8859-1

Best regards,

Peter

[Former Member]

Hmm, if you have only the CallSAPAdapter module in the chain, how can the sender adapter convert the data from EDI to XML ?

The error message sounds like the input message(after having passed the adapter) is not even XML.

CSY

Edited by: Christian Sy on Mar 30, 2010 9:21 AM

[peter_wallner2]

Hello Christian,

Thanks for your answer but the sender is sending plain XML, no EDIFACT - therefore I do not need any E_TO_X converting (BIC Mapping) in the Module of the X.400 sender!

Best regards,

Peter

[Former Member]

I have had the same problem before where it works in the mapping test, but not in the runtime.

it said there was a blank field so i had to do a if field is blank - set blnak constant, else send value.

although the message mapping works locally, i think if you do the test configuration in the ID it will fail.

[Former Member]

Hi Peter,

Check this link

Restart the Java engine and try to execute, one more option is edit the mapping and activate again and execute.

Check the payload from the mapping test tab and send it to the Integration engine through RWB- -> component monitoring --> Integration engine --> test tab. If this is success then the problem at the sender side.

Regards

Ramesh

[peter_wallner2]

Hello Ramesh,

Thank you for your help.

This worked:

Check the payload from the mapping test tab and send it to the Integration engine through RWB- -> component monitoring --> Integration engine --> test tab.

So the problem might be on the sender side.

But how should I approach the sender side? I mean what could they do wrong when sending the message? A wrong encoding? What other mistakes could there be?

Thank you again for your help!

Best regards,

Peter

[peter_wallner2]

Hello Ramesh, Hello experts,

I now got an answer from the sender.

They set "application/octet-stream" for each message they send because they mostly do not know what file type the messages are.

I assume if this was "application/xml" I would not have a problem. The sender says he can not change this though. They do get a new X.400 system middle of 2010 and might be able to do more settings then but I do not want to wait so long.

-

---

> Is there anything I can do to change the file type "application/octet-stream"?? <----

---

Thank you again or anyone that has an idea!

Best regards,

Peter

Edited by: Peter Wallner on Mar 31, 2010 3:25 PM

[Former Member]

Hi Peter,

you might be able to use the MessageTransformBean to change the ContentType.

Module: AF_Modules/MessageTransformBean

Parameter: Transform.ContentType

Value: application/xml

http://help.sap.com/saphelp_nw04/Helpdata/EN/57/0b2c4142aef623e10000000a155106/frameset.htm

regards,

Daniel