| Author |
Message
|
| billybong |
 Posted: Tue Nov 20, 2007 6:50 am Post subject: Bug in toolkit while using subflows? |
 |
|
Disciple
Joined: 22 Jul 2005
Posts: 150
Location: Stockholm, Sweden
|
Hi all!
I'm starting to go nuts on what I think is a bug in the message broker toolkit. It seems that when I create subflows for grouping my input MQ nodes to a subflow the wrapper flow continiously wires the output terminal wrong.
I've created two output terminals in the subflow, one for the output wiring and one for the failure and what happens is that once I save, close and open the wrapping flow all of my wires go from i.e. the FAILURE terminal instead of from both. When I deploy the actual runtime wiring is the same as in the "faulty" wrapper flow. Has anyone else noticed this?
I'm running the 6.0.2 toolkit version.
_________________
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere DataPower |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Nov 20, 2007 8:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Sorry but not enough detail.
Anyways make sure you enter and exit the subflow only with the IBM provided connectors. As such I do not understand you comment about closing and opening the wrapper flow.
My understanding of the subflow is that it is a black box with ONE entry and ONE exit... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Bill.Matthews |
| Posted: Tue Nov 20, 2007 8:34 am Post subject: |
|
|
Master
Joined: 23 Sep 2003
Posts: 232
Location: IBM (Retired)
|
Actually a subflow can have multiple Input nodes (i.e entry points) and multiple Output nodes (i.e exit points).
Each Input node and Output node must have a unique name.
This has been true for quite a while.
For an example of the multiple Outputs, take a look at the subflow that gets generated with a drag and drop of a WSDL file (via IA9O on V6 and built into V6.1) - it has multiple Output nodes.
_________________
Bill Matthews |
|
| Back to top |
|
|
| billybong |
| Posted: Tue Nov 20, 2007 8:45 am Post subject: |
|
|
Disciple
Joined: 22 Jul 2005
Posts: 150
Location: Stockholm, Sweden
|
Ok, guess I was a bit unclear in my first message.
The subflow is a black box which contains some of our input queues and is used in a general main wrapper flow that all queues connect to. In order to not clutter the main flow with 10-100 queues I've separated them based on business use into several subflows containing a bunch of queues from i.e. the same system.
The subflows all have two output nodes, which is supported by the toolkit. One node is called OUT which all queues output terminals are connected to, and the other node is called FAIL which the failure terminals are wired to. In the wrapper flow which has all these subflows I wire all subflow OUT terminals to the main flow and all FAIL terminals to our general failure handling in the same flow.
The problem is that once I save the wrapper flow and reopen it, all wires from the subflows are wired to only one terminal. I.e. I might end up with 2 wires from the OUT terminal, one to the general failure handling and one to the general flow.
Too bad you cant paste images in the forum, a picture would explain this clearer.
Am I making sense?
---Edit
BTW, if anyone wonder why I'm using a single main flow its because we're using the IBM EPP framework which separates the business usage by looking at the originating queue to determine a transaction type and from there taking different actions based on that. So all queues are grouped into a big general main flow.
_________________
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere DataPower |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Nov 20, 2007 10:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That's a toolkit bug. Upgrade to the most recent iFix.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Tue Nov 20, 2007 8:58 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
MAy be you can try rebuilding the project or opening the toolkit with -clean option...
if nothing works... then PMR is the way forward
_________________
Cheers |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 21, 2007 5:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I've seen this at earlier iFixes.
Apply at least iFix 06 of 6.0.2 Toolkit.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
