| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Survey: Quality of documentation on the MRM |
« View previous topic :: View next topic » |
| Author |
Message
|
| kolban |
 Posted: Wed May 01, 2002 5:03 am Post subject: |
 |
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
Folks,
Accompanying the CSD 2 release of WMQI, a new set of manual refreshes were released. Among these were the "Working with Messages" manual which describes how to use the MRM to achieve message modeling.
I am looking for some feedback on the quality of documentation, within the manuals and elsewhere, on the subject of using the MRM.
Some basic questions:
o Are you able to achieve your tasks from the documentation supplied?
o What, if anything, would you like to see explained further about MRM?
o Would a manual of examples provide benefit?
o Do you understand all the different capabilities and functions of the MRM?
I sure would appreciate any feedback you have on this subject.
Neil Kolban, IBM Advanced Technical Support, Dallas TX.
[ This Message was edited by: kolban on 2002-05-01 06:04 ] |
|
| Back to top |
|
 |
| samimohd |
| Posted: Thu May 02, 2002 7:18 am Post subject: |
|
|
Novice
Joined: 25 Mar 2002
Posts: 21
|
Neil,
Since IBM is trying to get away from NEON support, most of the IDOC parsing, I believe should now be handled with MRM. The manual ' Working with messages' does not address the issue of repeating elements. An section of examples showing specifically how to handle IDOCs from SAP would be very helpful. Also most of the stuff in Chapters 3 & 4 can also be found in the control center help. A new chapter with information on translating between XML and all other supported formats and vice versa would be very beneficial to the whole MQSI community.
Thanks.
Sami Mohammed
mohammed@us.ibm.com
|
|
| Back to top |
|
|
| CodeCraft |
| Posted: Sun May 05, 2002 8:27 am Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
IDOCs are unusual in that their structure is partially self defining (segment hiearchy) and partially pre-defined (segment layout). A full SAP IDOC solution for WMQI is available from IBM.
Key to this solution is not just the ability to parse IDOCs in their hierarchical (rather than a flat) structure, but also to directly connect to a SAP system and extract IDOC metadata for direct import to the MRM repository.
The solution distinguishes clearly between the logical business data and the SAP IDOC control record information. It also allows for the defaulting of values.
For anyone interested in working with SAP IDOCs in WMQI, this completely eliminates any need for message modelling and allows you to get on with the job in hand in a simple and efficient manner.
More information at dubadapt@ie.ibm.com |
|
| Back to top |
|
|
| CodeCraft |
| Posted: Sun May 05, 2002 8:39 am Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
| P.S. I assume we are referring to CSD 02 for WMQI 2.1. |
|
| Back to top |
|
|
| mpuetz |
| Posted: Sun May 05, 2002 8:42 am Post subject: |
|
|
Centurion
Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services
|
Hello Neil,
overall, MQSI documentation has improved a lot since 2.0.1,
however the docs are still pretty low on real world examples
and best practices. Someone would have to dig through this
forum and collect all the good work and ideas people have
contributed here.
I want mention some specific points which I think could be
improved:
- the new SQL stuff is hard to understand, especially references
because there are so few examples (e.g. the extremely valuable
parsing functionality using the CREATE statement).
- Exception handling still leaves many newcomers in the dark.
A walkthrough discussion on a real world example would be
helpful here. For a newcomer some guidance on how to design
robust flows is in place here as well.
- Background information on how MQSI internally works is scattered
thoughout the various manuals and some crucial info is missing
(like the order in which flowbranches are processed)
(Maybe some of this info is now alread in their, but I don't read
all the docs anew when new release comes out -> better delta information
for upgraders, e.g. a what's new guide with crosslinks to the regular
manuals).
Many people believe the Programming Guide is only meant for people who
like to write plugins, but it isn't. A lot can be learned from about
how MQSI works which will make it so much easier to debug ones own flows.
How about an MQSI Primer for Developers which explains the important
concepts of MQSI in one place without hiding behind all the details.
- A searchable HowTo Database shipped with the product would definitely
be helpful.
- Major industry standard examples for working with messages are desperately
needed for : EDI, SWIFT, SAP IDOC, and so on.
(There is a support pack with examples for tagged delimited messages,
but it is practically unusable since it doesn't explain how things are
done and it's content is purely academic)
I know there will be a new Redbook coming out for MQSI 2.1 development,
but I feel most of this should be in the standard manuals.
_________________
Mathias Puetz
IBM/Central WebSphere Services
WebSphere Business Integration Specialist |
|
| 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
|
|
|
|
