| Author |
Message
|
| sudheer7700 |
 Posted: Wed Feb 01, 2017 4:51 am Post subject: Difference between File Input and FTE Input nodes |
 |
|
Novice
Joined: 01 Feb 2017
Posts: 17
|
| Hai, can any one explains me about File Input and FTE Input nodes. I worked on MQFTE and configured FTE OUT node successfully. But I didn't found much difference between File Input and FTE Input nodes. Who are working on FTE Input node can help me? |
|
| Back to top |
|
 |
| zpat |
| Posted: Wed Feb 01, 2017 4:55 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Fileinput nodes deal with "standard" file transfer based on arrival of files into the local file system, or the use of FTP / SFTP to access them.
FTEInput nodes relate to the IBM MQ FTE product, which transfers files over MQ to avoid the limitations of "standard" file transfer.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| sudheer7700 |
| Posted: Wed Feb 01, 2017 5:04 am Post subject: |
|
|
Novice
Joined: 01 Feb 2017
Posts: 17
|
| Zpat, Thanks for your reply. Can you explain limitations of File input when compared to FTE input node? |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Feb 01, 2017 5:26 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
You mean the limitations of standard file transfer compared to use MQ FTE?
The nodes just interface to these protocols - they don't of themselves cause limitations.
There are many issues with ordinary file transfer, which is why better protocols exist (like FTE, Connect Direct and so on).
You can't just code the FTE node - you also need a full FTE infrastructure behind it and FTE agents at the other end.
The choice of using FTE over FTP/SFTP is unlikely to be that of the flow developer.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| sudheer7700 |
| Posted: Wed Feb 01, 2017 6:08 am Post subject: |
|
|
Novice
Joined: 01 Feb 2017
Posts: 17
|
| My major question is, we didn't have any options to set agents in FTE input node. We have only option to add location and file name, then how FTE input node works based on MQFTE concepts? Whatever location we specified in FTE InputNode, we are able to pick that file like normal file input node works. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Feb 01, 2017 6:20 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Directory in FTEinput is a FTE directory (it can be left blank).
I presume this is somehow different from a standard file system directory, but I don't know - perhaps someone who has used FTE can help?
There is a sample FTE flow in the toolkit.
However if you are not using FTE, don't use the FTE node.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
