MQSeries.net :: View topic

smeunier · Posted: Tue Sep 06, 2005 12:06 pm Post subject: Proper technique Message parsing

I'm looking into converting R3Link data to/from SAP by using the WBI mySAP.com adapter. I already use this adapter for an number of messages just fine. The R3Link migration, however prsents a different case.

For Outbound messages, the mySAP.com adapter will receive the message from SAP. The adapter will convert the message to XML with namespace prefix. This is fine. I can receive the message and address field names within. No Problem. The RFH2 header that accompanied the message from the adapter is stripped and the message is forward to a processing message flow, where the XML message needs to be converted to an IDOC structure format. This is where I run into problems. Using the IA0F suprt pack and the IDOC documentation in the Help context, i'm unable to resove the problems I have during this secondary processing.

The Input Node to the secondary process, has a Domain=IDOC, Message ID= <message set id>, message type='', message format=CWF

With this, the message appears to come in as BLOB. I have tried it as Domain-MRM and it become readable. Eaither way, I get a message stating something like: The bitstream, as presented to the 'IDOC' parser, is too small to contain the 'IDOC' structure. The length of this structure as given in the structure header is '5441'

I think this is due to the fact that the inbound IDOC, is in XML format with namespace prefixes which does not map to the Message Set Definition. I have tried various suggestions in the forum, but am stuck on this size issue. This leads me to beleive, my approach is wrong.

In essence I'm converting an XML inbound message to a CWF structure message. That is the goal. Any suggestions?