| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Overriding the FileInput node archive directory |
« View previous topic :: View next topic » |
| Author |
Message
|
| cutejigs |
 Posted: Sun May 23, 2010 5:46 pm Post subject: Overriding the FileInput node archive directory |
 |
|
Novice
Joined: 20 Jan 2010
Posts: 20
|
Good day Gurus 
I have a requirement to read each entry from a file then transform it to a message. I was able to accomplish this task using the FileInput node but an additional requirement has been added: if the processing is successful, move the file to ../OUTPUT else move the file to ../BACKOUT
I tried to wire the 'End of data' terminal to another processing (moving the file to a ../OUTPUT directory) but this is causing the FileInput node to throw an error because after the moving of the file, it goes back to the mainflow then deletes the file (it fails because the file is no longer in there).
I tried to change the approach by updating to copy the file instead of moving the file but the next issue is I need to create another flow to delete the mqsiarchive and mqsibackout directories (which I doubt the designer will agree to).
Do you guys know have an idea how to update the archive and backout directories of the FileInput node to a user-defined directory? In this way, I no longer need to create extra flows or my last resort is to use JavaCompute node.
Help is really appreaciated 
P.S.
The only changed I made in the FileInput node is the Basic/Input directory |
|
| Back to top |
|
 |
| Vitor |
| Posted: Sun May 23, 2010 6:27 pm Post subject: Re: Overriding the FileInput node archive directory |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| cutejigs wrote: |
| Do you guys know have an idea how to update the archive and backout directories of the FileInput node to a user-defined directory? |
I don't believe this is possible but someone else might know better. Why not just symlink the directories?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sushilishere |
| Posted: Sun May 23, 2010 7:53 pm Post subject: |
|
|
Apprentice
Joined: 27 Jul 2008
Posts: 36
|
Design wise.. In ur fileinput node im sure u wld have set the "Action on succesful processing" to archive and in Retry tab "Action on failing file" to backout. Have another bunch of flows to pick them from these folder locations and delete them once picked.
I don know whether this was the apporach u had mentioned before( the one which ur designer might not agree) Otherwise.. theres no direct solution for this as the Fileinput node is the first node and its properties cannot be tweaked in runtime .. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon May 24, 2010 3:02 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's not possible to adjust the node to put to any other directories like this, afaik.
I would use multiple FileOutput nodes. I would wire one up to the out of the FileOutput and one up to a try/catch situation.
The "main" FileOutput should not archive the file at all, merely send it to the final location. The other two will either write the file to /Output or to /Backout. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
