| Author |
Message
|
| Marek |
 Posted: Mon Mar 12, 2007 2:02 am Post subject: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
 |
|
Apprentice
Joined: 30 Jun 2004
Posts: 32
Location: Edinburgh
|
After upgrading from WMB v.6.0.0.1 to v.6.0.2 all keywords stored in the 'Long Description' of a Sub Flow (i.e. common/subroutine flow) are no longer available in the Main Flow's properties window (... of the Execution Group in the Broker Admin perspective). In other words BAR file creation is no longer including Subflow keyword values even though they are available.
The keywords fuctionality is being used to track CVS version numbers.
See pre and post upgrade screen shots on: http://markymos.freewebspace.com
For clarification, main flow SLI_MILLENNIUM_POSTREASURY_SUB no longer shows the version numbers of the 7 Sub Flows that it calls (Main Flow long description data is available).
Thanks for any advice.
IBM Manual ref:
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/index.jsp?topic=/com.ibm.etools.mft.doc/ac26550_.htm |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Tue Mar 13, 2007 6:33 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| What happens if you set the keywords in the short description instead? |
|
| Back to top |
|
|
| Marek |
| Posted: Wed Mar 14, 2007 6:08 am Post subject: |
|
|
Apprentice
Joined: 30 Jun 2004
Posts: 32
Location: Edinburgh
|
Tried the Short Description instead but the keywords were still not picked up.
Thanks for your suggestion. |
|
| Back to top |
|
|
| spriet |
| Posted: Wed Mar 14, 2007 8:05 am Post subject: We have identified the problem and we are investigating |
|
|
Newbie
Joined: 15 Apr 2004
Posts: 4
Location: Toronto
|
We have identified the problem and we are investigating a potential fix for WMB 602 iFix005
Dave Spriet
spriet@ca.ibm.com
_________________
WebSphere Business Integration Application Connectivity Tools,
IBM Canada Lab,
email: spriet@ca.ibm.com |
|
| Back to top |
|
|
| Marek |
| Posted: Thu Mar 15, 2007 2:41 am Post subject: |
|
|
Apprentice
Joined: 30 Jun 2004
Posts: 32
Location: Edinburgh
|
Dave, many thanks for the update.
We've raised PMR 43858 with IBM at our end.
Regards. |
|
| Back to top |
|
|
| spriet |
| Posted: Thu Mar 15, 2007 3:25 pm Post subject: Can you please include a screen cap of what you mean... |
|
|
Newbie
Joined: 15 Apr 2004
Posts: 4
Location: Toronto
|
Can you please include a screen cap of what you mean by this
>are no longer available in the Main Flow's properties window (... of the Execution Group in the Broker Admin perspective). In other words BAR file creation is no longer including Subflow keyword values even though they are available.
Are you referring to the Broker Archive editor or not showing the keywords/long description in the Admin perspective somewhere. If it is in the Admin perspective then can you show me where you are talking about by a screen cap?
Dave Spriet
_________________
WebSphere Business Integration Application Connectivity Tools,
IBM Canada Lab,
email: spriet@ca.ibm.com |
|
| Back to top |
|
|
| Marek |
| Posted: Fri Mar 16, 2007 4:53 am Post subject: |
|
|
Apprentice
Joined: 30 Jun 2004
Posts: 32
Location: Edinburgh
|
Hi Dave
Thanks for your mail.
I mean not showing the keywords/long description in the Admin Perspective (... Properties tab relating to a Message Flow in an Execution Group).
As requested, please see the following screen captures (also incl. above):
http://markymos.freewebspace.com
For clarification, the first pic shos everything ok under 6.0.0.1 whereas the second pic shows the missing data under 6.0.2.
Kind Regards.
Mark. |
|
| Back to top |
|
|
| dorian |
| Posted: Fri Mar 16, 2007 6:57 am Post subject: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
|
|
Newbie
Joined: 16 Mar 2007
Posts: 3
|
Hi Marek,
One thing you could try is copying the long description from a subflow to any of the nodes in that subflow.
I believe this is what the problem is:
Prior to 602, there was a bug in which the long description text from a flow would override the long description text from the nodes in the flow when the flow was added to a bar file. The original .msgflow still keeps the correct descriptions, but the compiled flow inside the bar has all the node long descriptions overriden.
This was fixed in 602, but the side effect of it is that long description of a subflow is no longer present in the compiled flow in the bar. The reason is that all the subflows are flattend out inside the bar, so only their nodes are listed, but not the subflow itself.
So, with the 602 fix you should still be able to get all your keywords if the long description is set on any of the nodes of your subflow.
Would it be possible to verify this?
Thanks!
-Dorian |
|
| Back to top |
|
|
| Marek |
| Posted: Mon Mar 19, 2007 5:36 am Post subject: |
|
|
Apprentice
Joined: 30 Jun 2004
Posts: 32
Location: Edinburgh
|
I inserted a Passthru node into my Subflow SLI_SUBFLOW_IL_EXCEPTIONHANDLER.
Then, I pasted the following keyword into the Long Description and redeployed:
| Code: |
| $MQSI_SLI_SUBFLOW_IL_EXCEPTIONHANDLER=MSGFLOW:1.4,ESQL:1.5MQSI$ |
Bad news is that this strategy does not work either. |
|
| Back to top |
|
|
| dorian |
| Posted: Thu Mar 22, 2007 3:54 pm Post subject: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
|
|
Newbie
Joined: 16 Mar 2007
Posts: 3
|
My bad, it is not just "any" node that this works on. For example long description on Compute node should be preserved.
Passthrough is special, need to add the comments on the label property.
See http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/topic/com.ibm.etools.mft.doc/ac26550_.htm, in particular:
Keywords
Keywords are extracted from the compiled message flow (the .cmf file) rather than the message flow source (the .msgflow file). Not all of the source properties are added to the compiled file. Therefore, add message flow keywords in only these places:
The label property of a Passthrough node
ESQL comments or string literals
The Long Description property of the message flow
If you read the last line as being main flow, not subflow, then all of those cases should work. Additionally, long description is also preserved on other nodes, such as Compute.
Hope this works for you! |
|
| Back to top |
|
|
| Marek |
| Posted: Mon Apr 02, 2007 6:53 am Post subject: |
|
|
Apprentice
Joined: 30 Jun 2004
Posts: 32
Location: Edinburgh
|
| Quote: |
If you read the last line as being main flow, not subflow, then all of those cases should work. Additionally, long description is also preserved on other nodes, such as Compute.
Hope this works for you! |
Thanks. Tried 'label' property of Passthru node. Works now. |
|
| Back to top |
|
|
| Marek |
| Posted: Mon Apr 02, 2007 7:30 am Post subject: |
|
|
Apprentice
Joined: 30 Jun 2004
Posts: 32
Location: Edinburgh
|
... ref. Passthru nodes ... I don't intend creating any connections to/from the Passthru node ... just intend to leave it standalone in each flow. Are there any issue with this?
Thanks. |
|
| Back to top |
|
|
| dorian |
| Posted: Mon Apr 02, 2007 9:57 am Post subject: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
|
|
Newbie
Joined: 16 Mar 2007
Posts: 3
|
| I believe the Passthrough node can just sit happily there without being connected to anything. Unless you get a validation error when saving the flow, unconnected passthrough nodes should be fine. |
|
| Back to top |
|
|
| EddieA |
| Posted: Mon Apr 02, 2007 1:37 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Marek wrote: |
... ref. Passthru nodes ... I don't intend creating any connections to/from the Passthru node ... just intend to leave it standalone in each flow. Are there any issue with this?
Thanks. |
Why. What would this achieve.
The Passthrough node is designed to put a line of user data, into a Trace, so that you can identify which version of a flow you are running. With no connection to the node, it can't do that.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Marek |
| Posted: Tue Apr 03, 2007 12:34 am Post subject: |
|
|
Apprentice
Joined: 30 Jun 2004
Posts: 32
Location: Edinburgh
|
| Quote: |
| Why. What would this achieve. |
Complete clarity of what esql and msgflow CVS versions are running in Production incl. all external components (e.g. subflow and global variable libraries).
The BAR file will contain version details of all components. Once deployed this data can be viewed via the Admin Perspective properties tab of a Message Flow in an Execution Group. |
|
| Back to top |
|
|
|
|
