| Author |
Message
|
| neo_revolution |
 Posted: Tue Jul 13, 2004 10:07 am Post subject: Generating documentation from msg flow ? |
 |
|
Voyager
Joined: 21 Oct 2003
Posts: 80
Location: NJ
|
Hello,
Did any tried to generate documentation based on the msg flow ? What I mean is for every node there is a "Description" tab where we can write comments or documentation.
Are there any tools or supportpacs that takes a msg flow (xml file) and generate documentation. or Did any one did something similar?
Thanks. |
|
| Back to top |
|
 |
| kirani |
| Posted: Tue Jul 13, 2004 12:46 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
What version of WMQI are you using?
I tried using Description Tab in WMQI 2.1. Everything looked good until I checked-in the message flow. I lost my <CR><LF> chars in description text after I checked-in the message flow.
If using WBIMB 5.0 you can write comments header in your .esql file.
I have written a C# program that will parse the Message flow (xml file) to extract ESQL code in each node and their properties.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| CoolDude |
| Posted: Tue Jul 13, 2004 12:50 pm Post subject: |
|
|
Apprentice
Joined: 17 Jan 2004
Posts: 39
|
I dont know any tools that would help us to retrieve the description. But my sincere advise would be not to use any sort of special characters as i have faced some issues some time back when i have some special characters in that pane.
Just wanted to caution you. Yes we will loose the <CR> and <LF> once we check in.
Thanks.
_________________
Correct Me from Wrong  . If i am correct Appreciate Me  |
|
| Back to top |
|
|
| neo_revolution |
| Posted: Tue Jul 13, 2004 1:02 pm Post subject: |
|
|
Voyager
Joined: 21 Oct 2003
Posts: 80
Location: NJ
|
We are using WMQI 2.1. We are trying to do is
> put description for each node in a msg flow
> write a msg flow to parse the xml-msg flows to create a HTML doc
listing nodes used, with the description and its properties.
I want to know how do we generate HTML files using WMQI. Apart from using trace node is there any other option (we are on z/os, trace node may be little complex)
Kiran, What I am trying to do is same as your C# program, instead I am using another wmqi msg flow to do it.
Thanks |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Jul 13, 2004 1:24 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
neo,
In that case in your message flow you should generate an XML like (html) message from input XML (message flow file). Before that you need to analyze the exported Message flow (XML file) to find out which tags you need to read in order to generate html page.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Michael Dag |
| Posted: Wed Jul 14, 2004 5:11 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| CoolDude wrote: |
Just wanted to caution you. Yes we will loose the <CR> and <LF> once we check in.
|
just a guess... the loss of <CR> <LF> in the description is probably caused by the XML parser handling the messageflow.
What if you add your descriptions like this: 
<![CDATA[your description etc....
and the next line
and the next line and ends with ]]>
Disclaimer... this is untested... 
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Jul 14, 2004 8:54 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
If that was the case then we would have lost the <CR><LF> in ESQL code too!
If you look at the exported XML file, in ESQL section <CR><LF> chars are replaced by \n in XML value. Whereas for the description text after you check-in the message flow it does not enter \n chars.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| neo_revolution |
| Posted: Wed Jul 14, 2004 9:13 am Post subject: |
|
|
Voyager
Joined: 21 Oct 2003
Posts: 80
Location: NJ
|
| Just ignorance what's <CR> & <LF> tags ? |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Jul 14, 2004 9:25 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
CR = Carriage return
LF = Line Feed
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| neo_revolution |
| Posted: Mon Nov 29, 2004 10:19 am Post subject: |
|
|
Voyager
Joined: 21 Oct 2003
Posts: 80
Location: NJ
|
What about WBIMB5.0, how are message flows stored? Is it a xml format?
I have a message flow which parses .xml file and generates documentation, can we use it with exported WBIMB message flow ?
Thanks. |
|
| Back to top |
|
|
| JT |
| Posted: Mon Nov 29, 2004 10:53 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
The file extensions for exported message flows under v5.0 are .msgflow, .mfmap & .esql.
I believe the one you need to parse is no longer .xml, but is now .msgflow file (which includes the description parameter of the nodes).
It is an XML structured file. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Nov 29, 2004 11:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can also generate some documentation automatically in the Toolkit in version 5.
Some.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| neo_revolution |
| Posted: Mon Nov 29, 2004 12:01 pm Post subject: |
|
|
Voyager
Joined: 21 Oct 2003
Posts: 80
Location: NJ
|
Thanks JT. It should not be problem as long as the format is XML.
Thanks |
|
| Back to top |
|
|
|
|
