| Author |
Message
|
| kotha |
 Posted: Thu Oct 06, 2005 5:44 pm Post subject: synchronous activity |
 |
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
I've got a example worflow process from IBM site. In that process, the last activity is synchronous UPES activity with no end symbol and this process has no sub processes.
My question is: What happens when it recieves a message (or triggered by ) from MQ??. what is the use of making last activity synchronous because the process will end any way.?? |
|
| Back to top |
|
 |
| supreeth |
| Posted: Thu Oct 06, 2005 10:27 pm Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
Hi,
| Quote: |
| I've got a example worflow process from IBM site. In that process, the last activity is synchronous UPES activity with no end symbol and this process has no sub processes. |
I don see tat making the last activity synchronous is un necessary. The purpose of making a UPES activity synchronous is to get a response back from the activity.
So, consider a scenario where you take an action (say application database update) based on the response of the activity. SO, in this case, i think UPES activity being synchronous makes sense
Thanks and Regards,
Supreeth
_________________
Supreeth Gururaj
IBM Certified WMQ Solution Expert |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Oct 07, 2005 5:47 am Post subject: Re: synchronous activity |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| pachyderm wrote: |
| My question is: What happens when it recieves a message (or triggered by ) from MQ??. |
Since the activity is Synchronous, the activity and hence the Instance will be in a running state until the activity ends, at which time since you say this is the last activity the instance will also end.
| Quote: |
| what is the use of making last activity synchronous because the process will end any way.?? |
Perhaps there is something that must be done prior to instance completion, like updating some data store.... IMHO, this is VERY common
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| kotha |
| Posted: Fri Oct 07, 2005 6:01 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
| Quote: |
| So, consider a scenario where you take an action (say application database update) based on the response of the activity. SO, in this case, i think UPES activity being synchronous makes sense |
Let us take one scenario here:
A--->B (B is synchronous)
when the process flow starts at A and comes to B, a messege will be placed in MQ Queue(X) by B and wait for a message to in another/same queue(Y). lets say after procesessing(retrieving DB data) the message(X), another queue(Y) got the message(retrieved DB data) and now B activity takes the data and do what???. As the process going to end so the data will also expire. |
|
| Back to top |
|
|
| supreeth |
| Posted: Fri Oct 07, 2005 6:22 am Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
Hi,
I guess you are looking at MQ Workflow as a standalone unit. Take a scenario where u need to integrate workflow with other applications.
| Quote: |
| when the process flow starts at A and comes to B, a messege will be placed in MQ Queue(X) by B and wait for a message to in another/same queue(Y). lets say after procesessing(retrieving DB data) the message(X), another queue(Y) got the message(retrieved DB data) and now B activity takes the data and do what???. As the process going to end so the data will also expire. |
Consider Workflow with another application App1. Say, App1 is triggering workflow. App1 looks into the application database (say, oracle) to proceed further. This database is being updated by the workflow activity processed in the end.
So, even if the workflow process is going to expire, the data is being feeded to the application App1.
This, i am talking from one of the real life scenarios 
Hope things are clear now
Thanks and Regards,
Supreeth
_________________
Supreeth Gururaj
IBM Certified WMQ Solution Expert |
|
| Back to top |
|
|
| kotha |
| Posted: Fri Oct 07, 2005 6:57 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
Thx Supreeth,
somewhat clear but stil hazy from my side. let me build a process and check it out. my external entity is ICS collab. |
|
| Back to top |
|
|
| fidelio |
| Posted: Mon Oct 10, 2005 2:41 pm Post subject: |
|
|
Apprentice
Joined: 14 Sep 2005
Posts: 45
Location: AttainBPM
|
Theoretically the process won't complete until the synchronous activity successfully completes. If you make the activty asynchronous, you won't have the opportunity to report the success/fail of the activity and handle it within the process.
In your situation, what happens if your ICS collab fails? If you have a synchronous invokation of the collab and it fails (and your collab reports the failure), you can model an error handling step in workflow that allows you to fix the problem and resubmit the job. |
|
| Back to top |
|
|
| BenBaumann |
| Posted: Tue Oct 18, 2005 11:31 am Post subject: |
|
|
Apprentice
Joined: 28 Jul 2005
Posts: 25
Location: Milwaukee
|
| exactly right, being synchronous allows you to handle errors. If the activity was asynchronous you would not even know if there was a problem with the service you are calling. |
|
| Back to top |
|
|
|
|
