| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Scheduling server/ BT verify question |
« View previous topic :: View next topic » |
| Author |
Message
|
| newbiedude |
 Posted: Wed Jan 15, 2003 1:22 pm Post subject: Scheduling server/ BT verify question |
 |
|
Voyager
Joined: 22 Dec 2002
Posts: 87
|
okay i am a little confused. can someone please explain
is the scheduling server responsible for having work items suspended/started or both? I understand that the actual work is being done by the exec servers but what is the scheduling server do?
second question i had was about the buildtime verify function? i have looked through the documentation but am not clear on it. does it prevent infinite looping, what exactly are the things it's checking for.
appreciate any help~ 
_________________
Newbiedude |
|
| Back to top |
|
 |
| jmac |
| Posted: Wed Jan 15, 2003 2:06 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
The scheduling server takes care of 1) Sending Notifications; 2) Activity Expirations; 3) Suspend for a certain time interval. In short it handles all of the MQWF timing functions.
You must remember that the Scheduling server is not started by default, so if you want to use these features you must be sure to get it started.
The Buildtime Verify only parses the FDL for errors. I.E. it does the same (or at least pretty close to the same) parsing of the FDL that is done when you do a Translate (-t) on import.
MQWF has no tools that will help you validate a model. You would need to develop your own.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Wed Jan 15, 2003 3:15 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
Below is some information, I had sitting on my desktop from a while ago. It's Just a summarization from the ibm notes/manuals out there(more of a short version). Hope this helps clear a few doubts on the scheduling server...
| Code: |
Scheduling server:
=====================
The Scheduling server controls and manages notification for activities that must be performed within a certain time frame. For example, it items are overdue for a process; the Scheduling server sends notifications to the work list of the relevant persons.
It is the component that schedules actions based on time events, such as resuming suspended work items, or detecting overdue processes
NOTE: Within an MQ Workflow system group, only one Cleanup Server and one Scheduling Server are needed to serve all the systems within this system group.
How the Scheduling Server works
===================================
The scheduling server scans several tables in the database to see whether processes have to be resumed (suspend until..) or whether notification for overdue work items have to be generated. Each time the scheduling server runs, it accesses the database, which degradates the overall performance and also might lead to temporary locks of tables or rows. This might cause the execution servers to wait.
With the scheduling server running every 5 minutes, the client response time increases while the server is running. If it is not necessary to repeat the scheduling-related work very often, the scheduling server can be customized according to the requirements. For example, the server can be set to run once every hour or once every two hours. It can also be set to run only once a day. If notifications and the suspended are resume workitems are not used, it is even possible to work without the scheduling server.
Details Scheduling server properties
=========================================
Name & Description
(Check interval):
============================
for scheduling server Specifies the time intervals that the administration server checks whether the scheduling server is still active or not.
(Scheduling server start option):
================================
Specifies whether the scheduling server should be started during startup of the MQ Workflow system.
(Scheduling start time):
===============================
Specifies when the scheduling server should start automatically.
(Scheduling stop time):
================
Specifies when the scheduling server should stop. A value must be provided when a value has been specified for the scheduling start time.
(Notification check interval):
==================================
Specifies the time interval after which the scheduling server checks again for notifications.
(Delete notification items):
==================================
Specifies the number of notification items deleted by the scheduling server in one transaction.
(Create notification items):
=====================================
Specifies the number of requests to create notification items sent to the execution server in one transaction.
|
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
| newbiedude |
| Posted: Wed Jan 15, 2003 9:41 pm Post subject: |
|
|
Voyager
Joined: 22 Dec 2002
Posts: 87
|
Jmac, Praveen:
thnx for the all the great info here. From all the info posted, what I am understanding is that the scheduling server is the time management part of workflow.
Jmac's
| Quote: |
You must remember that the Scheduling server is not started by default, so if you want to use these features you must be sure to get it started. |
Jmac, you are correct. The scheduling server feature was not started, until we started it ourselves in BT.
We didn't realize this until we accidentally re-started  our pilot imaging server system after turning this feature on, but apparently you are supposed to restart the workflow service for workflow to pick up the change.
At first it was confusing understanding the various scheduling server check intervals and it had to take a few tries but with your help and from us banging our heads it now seems to fit in the picture.
thank you very much
_________________
Newbiedude |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Jan 16, 2003 6:00 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| newbiedude wrote: |
| We didn't realize this until we accidentally re-started our pilot imaging server system after turning this feature on, but apparently you are supposed to restart the workflow service for workflow to pick up the change. |
Everything in the Network tab of Buildtime, is read by the Admin Server at startup. Thus anything that is changed via Buildtime for the Network Objects requires a restart of MQWF.
I am sure you realize this, but you can also start the Scheduling Server using the admin utility.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Jan 16, 2003 7:02 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
[quote="newbiedude]At first it was confusing understanding the various scheduling server check intervals and it had to take a few tries but with your help and from us banging our heads it now seems to fit in the picture. [/quote]
You think you have lumps... you should have tried this 4 years ago.... 
_________________
John McDonald
RETIRED |
|
| 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
|
|
|
|
