| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Using TDS to Parse X12 Messages |
« View previous topic :: View next topic » |
| Author |
Message
|
| wyatt |
 Posted: Tue Aug 29, 2006 4:33 pm Post subject: Using TDS to Parse X12 Messages |
 |
|
Voyager
Joined: 28 Nov 2004
Posts: 76
|
Can anyone describe their experience using TDS to model/parse EDI X12 messages.
Did you model your X12 message or use service like Dublin Adapters.
Is is easier to use an XSD editor like xmlspy to model these messages or should modeling activity only be done within the message broker toolkit.
Did you find any product limitations when modeling parsing EDI data...
...Looking to parse EDI X12 and EDIFACT messages to XML structure for backend application. The sample X12 message set/flow that comes with MB V6.0 looks pretty slick, my short experience modeling TDS messages has so far been painful. Is there a good intro type documentation? |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Aug 30, 2006 1:33 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Is is easier to use an XSD editor like xmlspy to model these messages or should modeling activity only be done within the message broker toolkit. |
Message Broker toolkit adds product-specific annotations to the XSD which describe the physical ( on-the-wire ) format of the EDI messages. You could do that using XMLSpy, but you would need to know the exact format and content of the annotations, and even then it would be very painful. If you really wanted to, you could use XMLSpy to create the logical ( pure schema ) structure as an XSD, then create a message definition file (.mxsd) from it and add the annotations. But I don't recommend it. |
|
| Back to top |
|
|
| msukup |
| Posted: Fri Sep 01, 2006 6:51 am Post subject: |
|
|
Acolyte
Joined: 11 Feb 2002
Posts: 56
|
wyatt,
you should ask your IBM sales rep about this -- we have had many conflicting statements from IBM about EDI capabilities in message broker, and, frankly, EDI in msg broker has been an unhappy experience for us. On the one hand, it is stated that it is supported. Yet, our rep pointed us to DataStage TX as a perhaps more appropriate solution for EDI than MB. I do know that the Dublin Adpater group has a set of X12 txns (and EDIFACT), but not a full set. Furthermore, you should take a much closer look at the example in the sample gallery -- the element names do not make as much sense when you really analyze the txn (they are based on reference types in EDI rather than reference names, which will get very confusing). good luck. |
|
| Back to top |
|
|
| wyatt |
| Posted: Fri Sep 01, 2006 7:31 am Post subject: |
|
|
Voyager
Joined: 28 Nov 2004
Posts: 76
|
...IBM has directed us to use DTX to perform our EDI parsing and translation. So far we have been less than impressed with the DTX product, specifically its ability (or rather inability) to integrate with message broker and java. DTX java adapter performance has been abysmal.
Has anyone had success modeling/Parsing EDI data within the message broker? All comments welcome |
|
| Back to top |
|
|
| wyatt |
| Posted: Fri Sep 01, 2006 7:34 am Post subject: |
|
|
Voyager
Joined: 28 Nov 2004
Posts: 76
|
| Quote: |
| and, frankly, EDI in msg broker has been an unhappy experience for us. |
Can you elaborate |
|
| Back to top |
|
|
| msukup |
| Posted: Fri Sep 01, 2006 8:09 am Post subject: |
|
|
Acolyte
Joined: 11 Feb 2002
Posts: 56
|
generally speaking, MB requires too much coding, either through eSQL or Java to perform mapping. Coding seems great for development, because it is often quick and dirty. But maintenance can become a headache (especially after several years and several cycles of personnel). This is especially true for EDI, where so much valuable information could be better represented in a visual map. It is true that Mercator (now DTX) has a reputation for not performing well, but it is user-friendly and very visual. You have to weigh the two, and not just for immediate needs but for long-term. You might want to press IBM on what direction DTX will take now that it is in the IBM Websphere line . . . perhaps if they focus on performance, you get the best of both worlds: good mapping, and scaleable interace. It's a tough choice.
As for EDI in MB -- you will face memory issues when dealing with large EDI txns, or batches. You will have to break apart batches of txns: We receive up to 5000 txns in one batch; for every one of these requirements, we have had to split the batch, either in EDI translator or when broker receives. Once the batch has been split, you must put in place something for reconciliation. MB chokes on this, as it is not designed for batch. And then the aspect of code maintenance, many business partner conditions, mentioned above, etc. There is also no compliance-check of the txn in the broker (the sample they provide in the gallery would fail compliance if you ran it through an EDI translator, btw). It would be much better if EDI translator (whether DTX, Gentran, or other) does the translation to XML, and then sends to broker single txns. You can then apply many fancy things in broker once in xml. hope this gives you some impressions around the obstacles. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Sep 01, 2006 8:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
WMB has had strong visual mapping in both v5 and v6.
A visual mapping tool is no replacement for good documentation on business messages, business transformations and business processes. Neither is an XSLT.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
