| Author |
Message
|
| gmmqnet |
 Posted: Wed Sep 15, 2004 2:46 am Post subject: SWIFT Message transformation |
 |
|
Novice
Joined: 12 Feb 2004
Posts: 18
|
After having seen the postings related to SWIFT transformation would like some more information.We are about to develop a solution using WBIMB 5.0 for a client where in we will be accepting the message in SWIFT formats MT200,MT210 and MT300.
The messages in MQ would be in flat text format.My dilemma is to how to transform a flat file(with those tags) into a message format that can be used to map to already defined message sets.
Thanks in advance. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Sep 15, 2004 4:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You should ask this in the WBIMB forum.
Basically, the answer is you need to model your SWIFT messages.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Sep 15, 2004 3:31 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Moved to WMQI Forum.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Lisa |
| Posted: Thu Sep 16, 2004 5:45 am Post subject: SWIFT |
|
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
Take a look at IBM's tagged/delimited support pac id05.
Lisa |
|
| Back to top |
|
|
| kingsley |
| Posted: Thu Sep 16, 2004 6:12 am Post subject: |
|
|
Disciple
Joined: 30 Sep 2001
Posts: 175
Location: Hursley
|
Use input as tagged delimited and convert it into XML in the compute node.
Once you have the format in XML, you can play it with around .
Don't try to attempt to pass the message in SWIFT format across the flow. It will be tough to update database, convert it to GLOSS or EDI or FIX standards.
Or use the input format as SWIFT and convert it to XML. No need for anyone to write XML in this case. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 16, 2004 6:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| kingsley wrote: |
Use input as tagged delimited and convert it into XML in the compute node.
Once you have the format in XML, you can play it with around .
Don't try to attempt to pass the message in SWIFT format across the flow. It will be tough to update database, convert it to GLOSS or EDI or FIX standards.
Or use the input format as SWIFT and convert it to XML. No need for anyone to write XML in this case. |
Within the same message flow, what physical parser is being used to describe the message doesn't matter.
The logical message tree will still be just that, a logical message tree. And it's no harder or easier to work with a logical message tree with an XML physical parser than it is to work with a logical message tree with a TDS phsyical parser.
Unless the output format is going to be XML, I wouldn't recommend creating an XML model.
If, on the other hand, the intent is to transform an incoming message into a standard format for use with many different processes... then XML is a good choice.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
