| Author |
Message
|
| jharringa |
 Posted: Fri May 02, 2008 12:00 pm Post subject: FileOutput node FTP in WMB 6.1 |
 |
|
Acolyte
Joined: 24 Aug 2007
Posts: 70
|
I am using the FileOutput node for a flow in WMB v6.1.0.1 to FTP a file to a server. It works great, however, I started testing failure scenarios and I'm a little curious about the behavior that I see. I put in a bad host name and deployed the flow and it did not move to the failure terminal. Instead, it created the file on the local file system and then continued on down the flow. I did not have the failure terminal wired but I would have expected that I would have received an error telling me that my ftp host was junk.
Is my expectation correct or should I be doing something else here? |
|
| Back to top |
|
 |
| EAI Developer |
| Posted: Fri May 02, 2008 12:23 pm Post subject: |
|
|
Centurion
Joined: 30 Nov 2005
Posts: 101
Location: US
|
Hi jharringa,
You said "Instead, it created the file on the local file system and then continued on down the flow " .What is the meaning of the down the flow here ?? FileOutput node will be last node of the message flow,which do not have any output terminals.So I didn't understand ,from where you can get failure terminal and output terminal.
Which nodes you are talking about ? Is it File Extender or some thing else ??
Regards,
EAI Developer. |
|
| Back to top |
|
|
| jharringa |
| Posted: Fri May 02, 2008 12:34 pm Post subject: |
|
|
Acolyte
Joined: 24 Aug 2007
Posts: 70
|
| I am using the new FileOutput node for 6.1 so this is not FileExtender. The output terminals for FileOutput are: Failure, Out, and End of Data. So in this case it is going through the Out terminal instead of the Failure terminal. I would have expected that it would have gone through the failure terminal since the data didn't reach the ultimate destination (FTP server). Instead, my regular processing occured because it went through the out terminal. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 02, 2008 1:33 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I believe this behavior of the node is somewhat well documented... FTP is a secondary step to the processing of the file node, and it will be retried unless you configure the node not to retry it.
On the other hand, every time I open my mouth about the File nodes, mqpaul is forced to correct me.
So it's really likely you shouldn't take much heed of what I've just said.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jharringa |
| Posted: Mon May 05, 2008 12:22 pm Post subject: |
|
|
Acolyte
Joined: 24 Aug 2007
Posts: 70
|
I don't see anywhere where this would retry. I know that the FileInput has retry logic.
I just figured that this would go out of the failure terminal for those of us who want to know if the FTP failed.  |
|
| Back to top |
|
|
| mqpaul |
| Posted: Tue May 06, 2008 1:11 am Post subject: There's an APAR IC55034 |
|
|
Acolyte
Joined: 14 Jan 2008
Posts: 66
Location: Hursley, UK
|
(Jeff's going to hate me for this  His answer was correct, but the FileOutput node wasn't!)
A problem similar to this was reported a couple of months back, and fixed in the subject APAR. The FileOutput node produced error messages when FTP failed, but didn't throw an exception. With the APAR, it throws an exception if, say, a flow can't connect to the FTP server, and as a result you'll get retry or failure processing as appropriate.
_________________
Paul |
|
| Back to top |
|
|
| rknox |
| Posted: Tue May 06, 2008 7:14 am Post subject: |
|
|
Apprentice
Joined: 28 Aug 2007
Posts: 34
|
| I do infrastructure work with jharringa. I cannot find this APAR that is referenced. I have searched google and IBM but come up with nothing. Any help would be appreciated. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue May 06, 2008 7:17 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| IC55034 isn't part of a fixpack yet. If you'd like this APAR, ask IBM support. |
|
| Back to top |
|
|
| jharringa |
| Posted: Tue May 06, 2008 10:29 am Post subject: |
|
|
Acolyte
Joined: 24 Aug 2007
Posts: 70
|
| Sounds good. Thank you all for your help. |
|
| Back to top |
|
|
| sknrt1 |
| Posted: Tue May 20, 2008 5:31 am Post subject: |
|
|
Apprentice
Joined: 22 Jan 2003
Posts: 39
Location: USA
|
we reported the problem abt FileOutput node in January and got the fix APAR:IC55034 in February
1.not throwing Exception in case of a problem
2.and file remains in mqtransmit folder, causing problem for retry
The provided fix solved both the problems.
There is one more problem with FTP put by file output node:
As the nature of FTP, while File is being put to the remote server, the file is not locked and the receiving application can get the unfinished (incomplete transfer) file. Generally this is avoided by having some commands in the FTP script, such as
1. placing the file in a temporary directory on the remote server and move to the directory where needed, move operation locks the file.
2. placing the file with a different name on the remote server and rename to the required, rename locks the file.
It would be desired, for the FileOutput Node to have configurable options for the above.
Thanks
_________________
------------------------------------------
sk
MQ User since 2001
Message Broker User since 2001
IBM Certified
Solution Designer - WebSphere MQ
Solution Developer - Message Broker |
|
| Back to top |
|
|
|
|
