| Author |
Message
|
| JLRowe |
 Posted: Mon Jul 05, 2004 5:15 am Post subject: Wait for an event in workflow |
 |
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
I think I've got this covered already, but I just wanted to check with the guru's who frequent this group.
I wish to have a process wait for an event from a UPES, the scenario is as follows:
1) Activity sends message to UPES
2) UPES acknowledges receipt of message (i.e. we are processing the message)
... and then ...
3) UPES acknowledges message has been actioned (i.e. thankyou, I have now processed the message)
4) continue...
From what I can see, there is a 1:1 relationship between a UPES activity invocation and the reply, and there is no way for an activity to just wait for a UPES event type message. Does this sound correct?
Thanks all |
|
| Back to top |
|
 |
| jmac |
| Posted: Mon Jul 05, 2004 7:27 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Jonathan:
I believe what you are saying is correct. Let me just recap what I hear...
You have a UPES activity "U1" that needs to wait for an outside event "E1".
This activity U1 receives an input message to indicate that it is "RUNNING"
The U1 activity then waits for the event E1 to happen
The event E1 happens, and the UPES U1 is notifiied
It then responds to MQWF with an Activity complete message which puts U1 into the Finished state
How you have U1 wait for the activity is the issue. Generally I have used another queue on which the outside event will put its completion message. The trick then is to correlate the incoming message with the proper instance of U1, since I assume there may be many running. In any case, it doesn't matter how U1 "finds out" that the event has occurred, it only matters that the proper ActivityImplInvokeResponse is issued with the proper MQWF correlation ID.
I hope this helps.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Jul 05, 2004 9:00 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| jlrowe wrote: |
2) UPES acknowledges receipt of message (i.e. we are processing the message)
|
Why do you have to do this. If MQWF puts a message on a UPES queue then that means we are processing the message? |
|
| Back to top |
|
|
| JLRowe |
| Posted: Tue Jul 06, 2004 12:51 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
Well, this is what I wanted:
Workflow --> UPES (Actvity invoke message)
Workflow <-- UPES (1st response)
Workflow <-- UPES (2nd response)
But I have to do it like this:
Workflow --> UPES
Workflow <-- UPES (1st response)
Workflow --> UPES
Workflow <-- UPES (2nd response) |
|
| Back to top |
|
|
| amittalekar |
| Posted: Tue Jul 06, 2004 5:19 am Post subject: |
|
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
If you really want to implement this using workflow you can think of following alternative.
1) Add exit condition to UPES activity.
2) for first responce manupulate the exit condtion so that a workItem will be created in ready state for that activity.
3) Whenever ur external event happens just query this workItem and start it.
4) You can use the exit condition (u have to map output container to input container) to identify and generate second response.
Hope this helps |
|
| Back to top |
|
|
|
|
