| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SWIFT MQ Host Adapter and XML v2 |
« View previous topic :: View next topic » |
| Author |
Message
|
| kevinobyrne |
 Posted: Fri Mar 14, 2014 3:40 am Post subject: SWIFT MQ Host Adapter and XML v2 |
 |
|
Voyager
Joined: 17 Jul 2007
Posts: 83
Location: Ireland
|
Hi,
Our SWIFT support team have informed us that as they are moving from Swifth Alliance to MQ Host Adapter, there will be a change in the format of the xml (MX) messages they send to our broker flows over MQ.
The format will change to "XML v2". This has leading characters, before the xml
e.g.
The character 0x1f
The length in bytes of the xml
A number of null characters
Followed by the xml:
"<?xml version="1.0" encoding="UTF-8" ?><Saa:DataPDU...."
Screenshot example:
http://www.boards.ie/vbulletin/attachment.php?attachmentid=298544&d=1394797039
I'm wondering if anyone else processing SWIFT xml with middleware encountered this request?
Our SWIFT support team have received a response from SWIFT support who insist that changing to this new format unavoidable.
It seems bizzare that an "upgrade" would change from XML to such an awkward format (we would have change our flows to parse as a BLOB)
Based on what SWIFT have told us, I would expect this to be an issue for anyone using SWIFT xml and Message Broker this year?
We're on WMB 7.0.0.6
Thanks  |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Mar 14, 2014 9:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Tell them to stop feeding you BS. WMQ is not changing anything in the content... Maybe they need to tune their adapter... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kevinobyrne |
| Posted: Mon Mar 17, 2014 4:49 am Post subject: |
|
|
Voyager
Joined: 17 Jul 2007
Posts: 83
Location: Ireland
|
| There's no suggestion that MQ is changing the message. MQ Host Adapter is a SWIFT component. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Mar 17, 2014 3:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
In any case it is not an XML format. It may be some kind of format that has fixed fields in front of the XML, and maybe fields after the XML?
Have them define the fields in front of the XML and parse them with DFDL. You can then treat the whole xml as 1 character field to be reparsed by XMLNSC...
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| LouML |
| Posted: Mon Sep 15, 2014 4:55 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
kevinobyrne, do you have an update to this?
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
| kevinobyrne |
| Posted: Mon Sep 15, 2014 5:07 am Post subject: |
|
|
Voyager
Joined: 17 Jul 2007
Posts: 83
Location: Ireland
|
We had a discussion with SWIFT who reiterated that this change was unavoidable. "XML v2" is SWIFT specific terminology.
We will be implementing a code change in our WMB flow to parse the "XML v2" as a BLOB, remove the leading characters and RCD to XMLNSC so that it can be processed as normal. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
