| Author |
Message
|
| WBISurvivor |
 Posted: Fri Jul 21, 2006 10:02 am Post subject: FTP Server Input Node |
 |
|
Novice
Joined: 22 May 2006
Posts: 17
|
I have a FTP server input node feEding to a MQget node which then routes the message to another subflow, which processes the message.
his is how my message flow looks.
FTP Sever Input Node --> MQGET Node --> Message Processing SubFlow
But I am running into an issue where when I ftp a file, I don't see the message being processed nor I don't see the message in the input queue I configured in the MQGet node or in the dead letter queue. I am not sure what/where I am wrong? Any help is truly appreciated.
Thanks
Last edited by WBISurvivor on Fri Jul 21, 2006 10:48 am; edited 1 time in total |
|
| Back to top |
|
 |
| wschutz |
| Posted: Fri Jul 21, 2006 10:12 am Post subject: Re: FTP Server Input Node |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| WBISurvivor wrote: |
| I have a FTP server input node fedding to a MQget node which then routes the message to another subflow, which processes the message....Thanks |
Well, you need to explain this a bit better...
Is the "ftp server input node" supportpac IA0X or something else?
What do you mean "fedding (sic) to a MQget node which then routes the message to another subflow"? MQGet nodes don't route to anywhere.
Have you tried using the interactive debugger or putting trace nodes in the flow to see what, if anything, is happening?
_________________
-wayne |
|
| Back to top |
|
|
| WBISurvivor |
| Posted: Fri Jul 21, 2006 10:19 am Post subject: Re: FTP Server Input Node |
|
|
Novice
Joined: 22 May 2006
Posts: 17
|
| wschutz wrote: |
| WBISurvivor wrote: |
| I have a FTP server input node fedding to a MQget node which then routes the message to another subflow, which processes the message....Thanks |
Well, you need to explain this a bit better...
Is the "ftp server input node" supportpac IA0X or something else?
What do you mean "fedding (sic) to a MQget node which then routes the message to another subflow"? MQGet nodes don't route to anywhere.
Have you tried using the interactive debugger or putting trace nodes in the flow to see what, if anything, is happening? |
Wayne,
Yes the ftp server input node is a supportpac IA0X
This is how my message flow looks.
FTP Sever Input Node --> MQGET Node --> Message Processing SubFlow
The problem I am having is, when I ftp the file there seems to be no processing of the message and I cannot find where the message in any of the queues either. |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Jul 21, 2006 10:26 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
I've not used that s/p, so forgive me if I ask a silly question: Why do you have an MQGet node after the ftp node?
In any case, put a trace node between the ftp node and the MQGet node and see if the flow is being activated.
_________________
-wayne |
|
| Back to top |
|
|
| WBISurvivor |
| Posted: Fri Jul 21, 2006 10:43 am Post subject: |
|
|
Novice
Joined: 22 May 2006
Posts: 17
|
| wschutz wrote: |
I've not used that s/p, so forgive me if I ask a silly question: Why do you have an MQGet node after the ftp node?
In any case, put a trace node between the ftp node and the MQGet node and see if the flow is being activated. |
I just want to queue up the messages before starting to process them. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Sat Jul 22, 2006 6:06 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi WBISurvivor,
| WBISurvivor wrote: |
| I just want to queue up the messages before starting to process them. |
You want the file to be read(perhaps line by line) and the messages to be put into the queue specified by the MQGet Node ?? 
Can u please be a little clearer on how ur managing the requirement with the current flow design.
Have u tried running the flow on the debugger....
If the file is not picked then u mean that the configuration on the FTP Server Node is not correct.....
Regards. |
|
| Back to top |
|
|
| TonyD |
| Posted: Sun Jul 23, 2006 12:43 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
|
| Back to top |
|
|
| WBISurvivor |
| Posted: Mon Jul 24, 2006 7:16 am Post subject: |
|
|
Novice
Joined: 22 May 2006
Posts: 17
|
| TonyD wrote: |
| Transactional? |
Tony I didn't get your question? What do you mean by transactional? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jul 24, 2006 9:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The FTP node will not put messages on a queue.
Connecting it to an MQGet node will not help that.
If what you want is FTP->Queue->Get->Flow, then you need to do
FTPServer -> Compute ->MQOutput
MQInput -> Compute....
Or you can do MQOutput->MQGet... but then you don't have any asynchronicity between FTP connection and MQ processing, and you haven't really helped much by going out to a queue.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| WBISurvivor |
| Posted: Mon Jul 24, 2006 9:14 am Post subject: |
|
|
Novice
Joined: 22 May 2006
Posts: 17
|
| jefflowrey wrote: |
The FTP node will not put messages on a queue.
Connecting it to an MQGet node will not help that.
If what you want is FTP->Queue->Get->Flow, then you need to do
FTPServer -> Compute ->MQOutput
MQInput -> Compute....
Or you can do MQOutput->MQGet... but then you don't have any asynchronicity between FTP connection and MQ processing, and you haven't really helped much by going out to a queue. |
That's exatcly what I figured out and when I tried FTPServer -> JavaCompute ->MQOutput I run into an exception which is caused by the routing of the message to the mqoutput node. Not sure why routing the message to the output node is causing an error. I am trying to figue out what properties in the MQMD header has to be created/configured for the message to be routed correctly to the queue. I could see that the MQMD header is null for the message I am trying to route. I am stuck there.
<com.ibm.broker.plugin.MbBrokerException source:BIPv600 key:2230 message:[BIPv600:2230]BIP2230E: Er
ror detected whilst processing a message in node 'Caught exception and rethrowing'.
The message broker detected an error whilst processing a message in node 'Caught exception and rethr
owing'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error. : Caught exception and rethrowing >
at com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)
at com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:140)
at com.united.cdh.test.RouteToLabel.evaluate(RouteToLabel.java:118)
at com.ibm.broker.javacompute.MbRuntimeJavaComputeNode.evaluate(MbRuntimeJavaComputeNode.jav
a:146)
at com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1222)
at com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)
at com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:140)
at com.ibm.broker.ftpnode.STORCommand.execute(STORCommand.java:170)
at com.ibm.broker.ftpnode.FTPDNode.runCommandSocket(FTPDNode.java(Compiled Code))
at com.ibm.broker.ftpnode.FTPDNode.run(FTPDNode.java(Compiled Code)) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jul 24, 2006 9:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You need to create a valid MQMD with at least a minimum set of headers.
There are lots of specific instructions for doing this when the input node is the HTTPInput node - so you should start by looking at those.
And then you will have to know how to translate those into Java, as they will be designed for ESQL programmers.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| WBISurvivor |
| Posted: Mon Jul 24, 2006 9:38 am Post subject: |
|
|
Novice
Joined: 22 May 2006
Posts: 17
|
| jefflowrey wrote: |
| You need to create a valid MQMD with at least a minimum set of headers. |
I can always use a compute node instead of a java compute node.But right now I am trying to figure out what are the exact headers and their values that needs to be created to get the messages routed. |
|
| Back to top |
|
|
| cressie176 |
| Posted: Mon Jul 24, 2006 11:40 pm Post subject: Alternatives |
|
|
Newbie
Joined: 24 Jul 2006
Posts: 1
|
It's a few years since I used the FTP Server Input Node so the following may be out of date...
While the FTP Server Input Node seems attractive if you take a look at the source code it's horrible. Unless you make changes you'll find that it will use 100% CPU on windows, corrupts incoming messages if they are a certain size, won't allow username / password authentication and issues a multi line "hello" message which is incompatible with some clients. The supportpac also requires SWING libraries (to enable sound!!!), so you'll probably have to remove this if deploying to UNIX. Also there's no way to obtain the incoming filename. All these problems (and a few others I didn't mention) are fixable, but you may decide you're better off with the one of the following alternatives...
MA01 (command line utility to read messages from the file system and put them on a queue)
Timer Node + Local File Watcher (Install a real FTP server on the same server as WBIMB)
Timer Node + FTP File Watcher (Use the Apache Commons Net package for the FTP) |
|
| Back to top |
|
|
| PieterV |
| Posted: Tue Jul 25, 2006 12:23 am Post subject: Re: Alternatives |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
| cressie176 wrote: |
... but you may decide you're better off with the one of the following alternatives...
MA01 (command line utility to read messages from the file system and put them on a queue)
Timer Node + Local File Watcher (Install a real FTP server on the same server as WBIMB)
Timer Node + FTP File Watcher (Use the Apache Commons Net package for the FTP) |
or take a look at the JText Adapter |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 25, 2006 2:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Or, really, the WMB File Extender nodes.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
