| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Generating Documentation on the Mapping Node |
« View previous topic :: View next topic » |
| Author |
Message
|
| lonesheep |
 Posted: Tue Sep 12, 2017 6:49 am Post subject: Generating Documentation on the Mapping Node |
 |
|
Novice
Joined: 12 Sep 2017
Posts: 21
|
Hi,
Relatively new to using IBM technologies and the broker. Using IIB 10.0.0.2.
I've written a small service receive a JSON request, map that to the WSDL for another SOAP web service - call that SOAP web service and then map that response to the response JSON object.
I'm using the mapping node to do the data transformation. Whilst the service is working, I'd like to generate documentation for it. I can see that their is an option to generate documentation for the mapping - but this doesn't seem to generate anything to too much detail. I was hoping for a document to detail the input and output fields based on the input/output data structures (like the graphical display of the mapping node)
If there anything around to do this (or a plugin) - or am I complete overestimating the IIB documentation features?
Many thanks
Matt |
|
| Back to top |
|
 |
| martinb |
| Posted: Wed Sep 13, 2017 1:45 am Post subject: |
|
|
Master
Joined: 09 Nov 2006
Posts: 210
Location: UK
|
Good to hear you've got your IIB solution up and running.
I'm afraid the IIB Toolkit generate documentation action does not provide a detailed field to field tabulation of the Graphical Map transformation.
The related IIB Request for Enhancement on this aspect has not received a lot of support, I guess perhaps because the Graphical Map transformation is itself visual. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Sep 13, 2017 3:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Also, typically, IIB solutions are developed from documented message models - i.e. some kind of document that includes field level information.
So there usually isn't a need to generate documentation when it already exists.
If you do not have existing documentation, it's better to use the message schemas for the input to the map and the output from the map to at least list the fields and submit a document to the relevant architects, message owners for additional documentation.
Or put in wild guesses and mark the document "very likely to be wrong".
_________________
chmod -R ugo-wx / |
|
| 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
|
|
|
|
