| Author |
Message
|
| manoj |
 Posted: Thu Jun 13, 2002 12:01 pm Post subject: Scheduling a UPES activity |
 |
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
Hi,
I want to schecule one of the UPES activities in my process.
This particular activity should start (or run) only within the time frame say 6:00 AM to 6:00 PM . From 6:00PM to 6:00AM if the process is "about to start" that particular actvity it should not be started untill 6:00AM. At 6:00AM that UPES activity should be started. Any idea ?
I 've specified start and exit both "automatic".
cheers
Manoj |
|
| Back to top |
|
 |
| jmac |
| Posted: Thu Jun 13, 2002 2:16 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Possibly I dont understand the question, but since the UPES is an MQ Queue, if you dont run the Queue Monitor program that reads from the UPES, then the messages cant be processed, but because they are on the Queue, they will be processed when you start your Queue Monitor. So, I would simply put the QueueMonitor stratup and shutdown on a cron.
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| manoj |
| Posted: Fri Jun 14, 2002 4:40 am Post subject: |
|
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
The UPES activity makes calls to an external system. That system goes down from 6:00PM to 6:00AM(say) . So i don't want to make any calls to the external system from this UPES activity. We use Message driven beans to process the message. As soon as the message comes to the queue the MDB picks up that message and process it. As part of the processing we call the external system. I canot do any thing on the queue because we use the same queue for other UPES activities those are continuosly run thro' out the day
regds
Manoj |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Jun 14, 2002 5:14 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Manoj:
I really dont think there is an MQWF solution. I am afraid that you are going to have to solve this on the app side of the fence.
Good Luck
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| manoj |
| Posted: Fri Jun 14, 2002 5:20 am Post subject: |
|
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
Thanx John. The last thing i want to do is to put this on my application code. Need to find some workaround for this.
Thx for the reply
Manoj |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Jun 14, 2002 6:16 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Manoj:
I just realized that you could potentially solve this by having a dummy activity in front that does not end unless it is during the hours that you can process.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| manoj |
| Posted: Fri Jun 14, 2002 7:03 am Post subject: |
|
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
I thought of that option , but i 've several similar kind of UPES actvity which updates external systems. So for every step if i add a dummy ( i believe this activity is a manual actvity and we sepecify the experation time for that actvity) activity before the actual UPES activity it will increase the cost (BWU) of my process.
thx John
Manoj |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Jun 14, 2002 7:20 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Manoj
You could have a UPES activity that writes to a queue and then the Queue Monitor NEVER responds. This should cause the Activity to Expire. The only thing you would need to think about is the ActivityExpired (probably not the exact name) XML message that would be sent to the original Queue. But since this is not an ActivityImplementaionInvoke message it should be pretty easy for your current app to simply discard it.
Let me know what you decide in the end.
We have developed a framework that allows us to communicate with External systems using MQ whereby we correlate Responses from the External System and at that point complete the original UPES activity that began the communication with the External system. This is however proprietary so I can not share all of the details with you. Just this big picture.
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| manoj |
| Posted: Fri Jun 14, 2002 7:27 am Post subject: |
|
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
I 've something in mind ,trying it . donno about how feasible it 's.
Get back to you once i tried that.
thx
Manoj |
|
| Back to top |
|
|
| manoj |
| Posted: Fri Jun 14, 2002 9:41 am Post subject: |
|
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
Hi,
i was thinking in this way. For the UPES activities which are to be scheduled will 've a maual "start" condition . i.e the UPES activity goes to "READY" state(The workitem is not yet started) . ( if it was automatic the state would 've been RUNNING and message would've been available in the request Queue).
I will 've a dedicated process which contains a block activity, inside the block there will be a dummy activity and a UPES activity. The block exit condition is such a way that the block will never exit. Expiration time will be specified for the dummy actvity so that the UPES activity can be started based on the experation time set for the dummy activity.
The job of this UPES activity is to drive our Message driven bean. The MDB will query for all the workitems ( UPES workitems which we wanted to schedule) which r in READY state and belong to a user called say "AUTO". The MDB uses the user "AUTO" to login and start the workitems.
please comment
thx
Manoj |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Jun 14, 2002 11:33 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I really don't know what an MDB is, but this is how I would approach your solution:
1. Have these UPES activities use Manual start as you said.
2. Have a daemon program that runs during the hours that you wish.
3. Every so often have the daemon wake up and start all of the activities.
This may be exactly what you are saying you will do.
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| manoj |
| Posted: Fri Jun 14, 2002 1:00 pm Post subject: |
|
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
Yes , only thing is the Daemon program is driven by a Workflow process. This process (single instance) will be continuously running and invoke the Daemon program on a timely basis.
regds
Manoj |
|
| Back to top |
|
|
|
|
