| Author |
Message
|
| YORCH |
 Posted: Wed Aug 06, 2014 10:24 am Post subject: Trasform my own format to SWIFT FIN |
 |
|
Newbie
Joined: 06 Aug 2014
Posts: 1
|
Hi to all,
If I have IIB V 9.0, should I need create my own DFDL to transform, purchase IBM Integration Bus SupportPac IA0T or IIB V9.0 brings the data sets for transformation? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Aug 06, 2014 2:45 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Nobody will actually do the mapping for you (unless you pay them for it).
What you can get are the schemas to map to. You need to reach you to your Swift partner. They may be available for SWIFT XML or SWIFT DFDL for free from the SWIFT organization. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Thu Aug 07, 2014 1:49 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| fjb_saper wrote: |
Nobody will actually do the mapping for you (unless you pay them for it).
What you can get are the schemas to map to.
You need to reach you to your Swift partner. They may be available for SWIFT XML or SWIFT DFDL for free from the SWIFT organization. |
You write your own transformation logic and you create a tree to tree mapping by doing so (in ESQL or Java).
XML and JSON already provide a tree structure. If you have flat file formats you have another step before and after: Parsing (to the tree) and serializing (from the tree).
So 3 tasks: The middle one is done in ESQL or Java.
The first and third: Create (or on complex structures buy/get) message sets / descriptions / schemas (for MRM or DFDL)
For SWIFT you should buy / get one from e.g. IBM imho
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Aug 07, 2014 5:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fjb_saper wrote: |
Nobody will actually do the mapping for you (unless you pay them for it).
What you can get are the schemas to map to. You need to reach you to your Swift partner. They may be available for SWIFT XML or SWIFT DFDL for free from the SWIFT organization. |
I don't read the original post as asking for mappings, merely asking for DFDL schemas.
I was expecting kimbert or shanson to pop in and mention the DFDL.org github, but I guess that's just not happened yet.
I'd point to it, but I don't remember the URL and I don't know if it covers SWIFT or not. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Aug 07, 2014 5:11 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
IA0T would be a good choice. SWIFT is a very difficult data format, and you would need to be very careful if you modelled it yourself.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Aug 07, 2014 7:42 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
It is a long time since I was involved with developing Swift interfaces but is recall that if you 'rolled your own' there was whole heap of very painful testing that you had to go through in order to be able to connect your system up to the Swift Network.
(perhaps Kimbert can correct me here)
It might well be better in terms of speed etc to go with a pre-defined set of message models/schemas. At least then if you pass output validation (content and value) the at least SWIFT aren't going to get annoyed at you for sending messages that are all screwed up in terms of format.
It is obviously your call but if I was asked, then I recommend the IBM Support pack solution.(FWIW)
_________________
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 |
|
|
|
|
