| Author |
Message
|
| w |
 Posted: Tue Jan 04, 2011 12:36 am Post subject: Manually triggering flow. :help: |
 |
|
Apprentice
Joined: 08 Nov 2010
Posts: 44
|
Hi all,
I have a requirement for a flow that should be triggered manually once in a while.The purpose of the flow is to transfer data from one queue to another after some transformation of the data. I can think of starting the flow with a file input node. That way the flow wud be triggered by dropping a file at a particular location.Is there a better way ? [using WMB 6.1]
 |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Tue Jan 04, 2011 1:23 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Drop any format of message onto an MQ Queue?
Simple and can be done remotely.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| w |
| Posted: Tue Jan 04, 2011 1:26 am Post subject: |
|
|
Apprentice
Joined: 08 Nov 2010
Posts: 44
|
| Well that seems the most logical but i forgot to mention that i cannot use a queue here. The client is not willing to let me use a queue for this purpose. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Jan 04, 2011 2:30 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
SOAP Message
HTTP Message
JMS Message
Why this aversion to a queue?
WMQ is used by WMB. WMQ Comes with amqsput. Wrap that in a script and away you go.
The WMQ Method is by far the simplest. Any message read as a BLOB would suffice as a trigger.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 04, 2011 5:08 am Post subject: Re: Manually triggering flow. :help: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| w wrote: |
| The purpose of the flow is to transfer data from one queue to another after some transformation of the data. I can think of starting the flow with a file input node. That way the flow wud be triggered by dropping a file at a particular location. |
If the purpose of the flow is to pick data up from one queue, transform it and put it on a separate queue, why won't the client let you trigger it with a queue?
Note also that you can't trigger a flow this way; using a FileInput or a MQInput will require the flow to be running, so if the requirement here is to start the flow (i.e. the WMQ sense of triggering) you'll need something different.
However you induce the flow to start processing the queue to transform the messages and place them on the target queue, if you're using the MQGet node to read the messages review some of the disscussion in here. Looping round a queue with an MQGet node has some pitfalls.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| w |
| Posted: Tue Jan 04, 2011 10:30 pm Post subject: |
|
|
Apprentice
Joined: 08 Nov 2010
Posts: 44
|
@vitor
The messages are put into that queue only when a system is down. So someone needs to fix the problem in the system before my flow starts reading the messages from the queue.Hence the requirement of manual triggering other than the same queue. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 05, 2011 5:06 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| w wrote: |
| So someone needs to fix the problem in the system before my flow starts reading the messages from the queue.Hence the requirement of manual triggering other than the same queue. |
Then you have a number of options, because the same "someone" can take action once they've fixed the problem. Here are some thoughts:
- The "someone" can literally trigger your flow by starting it. It's a fairly trivial task to script an mqsistart & put proper controls around it's use. This allows your flow to start with an MQIpnput node as normal.
- If messages flow to this queue when the system is down, "someone" can move them back to the correct queue when the system is up. Again, this is easy to script, easy to control and is a fairly common solution to the situation you describe.
Other, possibly better, solutions are undoubtably possible.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
