| Author |
Message
|
| ghoshly |
 Posted: Tue Nov 24, 2009 5:06 am Post subject: Multiple type of SWIFT message parsing through a single node |
 |
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
In my single flow, multiple type of SWIFT messages would come and I need to validate them with the help of message set.
My question is that is there a way by which I do not need to specify the message format in the MQInput node and broker identifies the correct message format based on available message types (mxsd) in the message set for the incoming message?
Does Multipart messaging concept applies here properly ?
I know that I can parse the message through esql PARSE statement in runtime, but still there I need to identify the incoming message type first which would be a concern.
Please help. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Nov 24, 2009 6:55 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Yes, you need to model the SWIFT envelope as a separate message definition. SWIFT messages contain a message identifier in the envelope. You can use that as the Message Identifier to select the correct inner message.
I can tell you from personal experience that it is not straightforward to model SWIFT messages. You might want to consider purchasing a ready-made solution - either the SWIFT message sets from Dublin or WTX industry pack. |
|
| Back to top |
|
|
| ghoshly |
| Posted: Tue Nov 24, 2009 8:51 am Post subject: thanks Kimbert.. |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
Actuallly plan is there and we are trying to insist client to buy MB support pack for SWIFT messsages.. In the mean while I was going through the sample provided with message broker, where MT103 is used with the envelope.
There could be other message types as well in the same message set..right ? Or for each message type I need to have separate message Set to serve for all the message types I am expecting in my flow..
Thanks a lot in advance for your response... |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Nov 24, 2009 11:22 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Message format Blob, ESQL cast as string, look for the tag indicating the Swift message type number, extract the number and act upon it by routing to label or even sending to different queues before processing it with a message set. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Nov 24, 2009 1:33 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| No need for multiple message sets. Each inner message must have the Message Alias property set unless the message names correspond exactly to the expected values in the header. |
|
| Back to top |
|
|
| ghoshly |
| Posted: Tue Nov 24, 2009 11:42 pm Post subject: proved with small POC |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
Just performed small POC with two types of SWIFT messages in a message set. Its working fine with message name or Message Alias...thanks again Kimbert..
Is it possible that a SWIFT message arrives without the standard header mentioning the message type ? In that case challenge still persists. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Nov 25, 2009 12:13 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
If this happens then it is obviously not a valid swift message.
SWIFT are at fault and you should reject the message. There is a mechanism to do this.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
