Posted: Thu Sep 07, 2006 1:43 am Post subject: WMB and Fileextender fileout questions
Newbie
Joined: 07 Sep 2006 Posts: 6
Hi,
I want to use file extender with message broker 6. I have installed the latest fixpacks I think. The flow I need is a M2F flow.
The flow contains a MQInputNode than the FileProxyNode nexrt a ComputeNode to create the output and at the end FileOutputNode.
Transaction=No
All terminals of the MQInputNode are connected with the FileProxyNode. At the FileproxyNode a error handling subflow is connected to catch and failoure.
All things went fine except the error case. If I test an error situation (for example I set a wrong path in the compute Node) nothing arrive at the catch terminal. You see the error in the log. But I see wakeup messages between MQInput and proxy. What is this?
Transaction=Yes
I see the message at the sync terminal but never at the catch terminal.
What should I do to make a correct error handling? _________________ Jochen Benke
WebSphere Business Integration Services
IBM Software Group Germany
you said that you have created the error situation setting a wrong path by the compute node.
I can suppose you have set the FileOutputNode "Destination mode" property to "Output directory list" and you have set by esql code the wrong output path.
If my assumption is correct you have to known that this is not a 'real' error situation. In this case the MBFE behaviour is the following:
- an error message is written on the system error log (event viewer on windows)
- no exception is thrown and so is not possible to managed it using the FileInputNode/FileProxyNode catch or failure terminal. FileOutputNode produces the output files in the other valid directories read from the LocalEnvironment.
This behaviour is the same of MQOutput node that it is configured to work with a destination list.
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