| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Result file to a FTP Server other than the source FTP |
« View previous topic :: View next topic » |
| Author |
Message
|
| nelson |
 Posted: Wed Mar 18, 2015 6:56 am Post subject: Result file to a FTP Server other than the source FTP |
 |
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
Hi all,
I have a Multi-Protocol Gateway, with a FTP Poller Front Side Handler. It reads a file from a FTP Server, transforms the content and generates a result file with different name, in the same directory. This is working fine.
Is there any way to store this file into another FTP Server different from source FTP Server? Field "Result File Name Pattern" doesn't allow remote directory in the form: ftp://x.x.x.x:21/target/
Any hint?
Thanks in advance |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Mar 18, 2015 8:01 am Post subject: Re: Result file to a FTP Server other than the source FTP |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| nelson wrote: |
Hi all,
I have a Multi-Protocol Gateway, with a FTP Poller Front Side Handler. It reads a file from a FTP Server, transforms the content and generates a result file with different name, in the same directory. This is working fine.
Is there any way to store this file into another FTP Server different from source FTP Server? Field "Result File Name Pattern" doesn't allow remote directory in the form: ftp://x.x.x.x:21/target/
Any hint?
Thanks in advance |
When you define your Multi-Protocol Gateway, don't you define each ftp destination / source individually? As such all you'd have to do is use the correct place holder for the correct destination, namely the one you defined... right? What you seem to be attempting is to send the file to a rogue / undefined ftp host. I doubt very much datapower would allow you that... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| nelson |
| Posted: Wed Mar 18, 2015 8:45 am Post subject: Re: Result file to a FTP Server other than the source FTP |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| fjb_saper wrote: |
| nelson wrote: |
Hi all,
I have a Multi-Protocol Gateway, with a FTP Poller Front Side Handler. It reads a file from a FTP Server, transforms the content and generates a result file with different name, in the same directory. This is working fine.
Is there any way to store this file into another FTP Server different from source FTP Server? Field "Result File Name Pattern" doesn't allow remote directory in the form: ftp://x.x.x.x:21/target/
Any hint?
Thanks in advance |
When you define your Multi-Protocol Gateway, don't you define each ftp destination / source individually? As such all you'd have to do is use the correct place holder for the correct destination, namely the one you defined... right? What you seem to be attempting is to send the file to a rogue / undefined ftp host. I doubt very much datapower would allow you that... |
Well... you only define the Target Directory within the FTP Poller Front Side Handler in this way: ftp://x.x.x.x:21/source/. The front side handler is designed to place the result file in the same server.. So I was wondering how to "redirect" this file to another FTP Server. I'm thinking of using the "Default Backend URL" to send the file, but, not sure of how to handle the "Result File Name Pattern". |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Mar 18, 2015 10:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Looking that you have a backend url for the destination, does this backend url involve the filename or just the path? I'd say you build the filename like before and then look at how to pass it to your backend handler...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| nelson |
| Posted: Wed Mar 18, 2015 6:03 pm Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| fjb_saper wrote: |
| Looking that you have a backend url for the destination, does this backend url involve the filename or just the path? I'd say you build the filename like before and then look at how to pass it to your backend handler... |
I'll try dynamic URL backend. Thanks for your help! |
|
| Back to top |
|
|
| mayheminMQ |
| Posted: Fri May 20, 2016 4:42 am Post subject: |
|
|
Voyager
Joined: 04 Sep 2012
Posts: 77
Location: UK beyond the meadows of RocknRoll
|
Hi Nelson,
Dynamic Backend URL is the way to go.
Taking FTP/SFTP FSH as example:
Front side handler is only for front side of things i.e for picking a file to initiate It does not naturally control what should happen to the file once picked. All activities post validating and verifying the initial connection and file pickup happens later and with other objects.
One of the best practices is to have a file where you store a keyword:endpoint pair and use the keyword in transform function within a policy. This way you get flexibility on end points as well. Once you pick the required endpoint, add that to the URL out system variable and set the Route function to look at that particular variable. There are definitely some examples out there if you search in google for your scenario. Let me know if you dont find any and Ill try and share what I have later.
_________________
A Colorblind man may appear disadvantaged but he always sees more than just colors... |
|
| 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
|
|
|
|
