| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Autonomous Processes |
« View previous topic :: View next topic » |
| Author |
Message
|
| michaelfrancis |
 Posted: Thu Jan 02, 2003 9:54 am Post subject: Autonomous Processes |
 |
|
Newbie
Joined: 02 Jan 2003
Posts: 2
|
Can a Workflow process include a sub-process that is autonomous, that is, it is spawned with control returning to the parent process which continues according to all other EXIT and TRANSITION conditions?
We have tried this but even though the sub-process has no transitions from it, the parent process (or block within the parent process) does not complete until the sub-process has completed. The parent process CAN be deleted manually without affecting the sub-process, but this does not happen automatically.
We are trying to loop through a block, iteratively creating multiple sub-processes without having to wait for each sub to complete before creating the next.
Thanks,
mf |
|
| Back to top |
|
 |
| educos |
| Posted: Thu Jan 02, 2003 10:06 am Post subject: |
|
|
Apprentice
Joined: 18 Jul 2001
Posts: 34
Location: Salt Lake City, UT
|
I would suggest you have a simple UPES activity that would use the MQWF API or the XML interface to start the process.
The advantage is that the activity implementation returns immediately (so your process moves on to the thing it needs to do). Of course, you can still have your activity fail its exit condition if the process fails to start.
The downside is that you don't have a parent-child relationship between the 2 process instances - which could be useful in you audit trail for example. You could still work around this by naming your spawned process instance in a way that still implies some kind of relationship with the process instance that spwaned it...
_________________
Eric Ducos
EmeriCon, LLC.
Phone: (801) 789-4348
e-Mail: Eric.Ducos@EmeriCon.com
Website: www.EmeriCon.com |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Jan 02, 2003 10:53 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
If you need to tie the spawned process to the parent, I would suggest the use of the new Process context field which I believe is written to all audit records.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| michaelfrancis |
| Posted: Thu Jan 02, 2003 10:54 am Post subject: |
|
|
Newbie
Joined: 02 Jan 2003
Posts: 2
|
Thanks for the reply.
Yes, a UPES would work and could use a naming pattern to imply the relationship. We were hoping to spawn the process without using (another) UPES. We were hoping for a mechanism driven by the workflow model itself without programming. |
|
| 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
|
|
|
|
