| Author |
Message
|
| mahek |
 Posted: Mon Jan 03, 2005 9:16 am Post subject: scheduling server problem |
 |
|
Voyager
Joined: 10 Sep 2004
Posts: 87
|
Hi all,
I am trying to set the expiration of a activity to 30 seconds i am setting the scheduling server notification check interval to 5 seconds and i have imported the fdl in to run time and have restarted the workflow server, and the scheduling server is running but the activity is not expiring.I have seen the scheduling server settings it shows like this
Scheduling server settings
Check interval PT5M
Start mode Deferred
Server start time not set
Notification check interval PT1H
Create notification items threshold 10
Delete notification items threshold 100
I have no clue why the Notification check interval of the scheduling server is not getting changed. |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Jan 03, 2005 9:30 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Never messed with scheduling server settings but
| Quote: |
| Create notification items threshold 10 |
Doesn't this matter?
Can you change it to 1 and see if it works? |
|
| Back to top |
|
|
| mahek |
| Posted: Mon Jan 03, 2005 9:39 am Post subject: |
|
|
Voyager
Joined: 10 Sep 2004
Posts: 87
|
| Hi Venella but the what changes i am making to the scheduling server are not getting reflected. When ever i see the info of the scheduling server it shows the same thing (nothing changed) I dont know why the changes are not getting reflected i am using worklow(3.5) does any of the fix packs if not installed cause this problem |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Jan 03, 2005 10:20 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I have 3501 and it is working fine. I can change the setting.
Probably you need to apply the fixpack.
Are you getting any errors on the FDL import?
_________________
-Ratan |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jan 03, 2005 11:20 am Post subject: Re: scheduling server problem |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| mahek wrote: |
Scheduling server settings
Check interval PT5M
Start mode Deferred
Server start time not set
Notification check interval PT1H
Create notification items threshold 10
Delete notification items threshold 100
|
Your problem is that your notificaction check interval is 1 hour and your Scheduling server is not running.
You can start the Scheduling server with fmcautil, but I would recommend to change the value to Start mode Automatic using Buildtime or Modeler.
If you did change the notification check interval to 5 seconds, did you import that FDL? Then you need to restart mqwf, as the only time it reads the network settings is at startup.
ALso, if you are going to have a heavily loaded system, you really need to think through this 5 second noitification check interval, as it is going to add a lot of overhead to your system to check that frequently. General rule of thumb is to go no lower than 5 minutes.
_________________
John McDonald
RETIRED
Last edited by jmac on Mon Jan 03, 2005 11:31 am; edited 1 time in total |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jan 03, 2005 11:30 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| vennela wrote: |
| Can you change it to 1 and see if it works? |
Vennela: Best description of these settings is this technote:
http://www-1.ibm.com/support/docview.wss?rs=795&context=SW920&uid=swg21188010
At one point there was a bug in Modeler whereby they flipflopped the CREATE_NOTIFICATION_ITEM_THRESHOLD and DELETE_NOTIFICATION_ITEM_THRESHOLD default values.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| mahek |
| Posted: Mon Jan 03, 2005 12:10 pm Post subject: |
|
|
Voyager
Joined: 10 Sep 2004
Posts: 87
|
| Hi ratan venella and jamac, I am not getting errors while importing the fdl every thing is fine i have made the start mode also as automatic but after importing the fdl file with out errors and even after restarting the wf server the changes are not been reflected |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jan 03, 2005 12:17 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
If you have imported the proper FDL into the proper system and then restarted MQWF and the Scheduling server still shows the attributes you posted earlier, then there must be a bug.
I don't believe this to be the case. Post the FDL that you are importing and let's have a look. Also, post the output from fmcautil that you get when you select the options m;s;i
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| mahek |
| Posted: Mon Jan 03, 2005 12:31 pm Post subject: |
|
|
Voyager
Joined: 10 Sep 2004
Posts: 87
|
Hi all,
I have now just imported the domain in to an fdl with out talking the process model staff etc. The fdl is
/*
*
* FDL definitions generated by MQ Workflow at 2004-12-03, 2:17:31 PM.
*
*/
CODEPAGE 1252
FM_RELEASE V3R5 0
/*
* DOMAINs
*/
UPDATE DOMAIN 'DOMAIN'
DESCRIPTION "Default domain"
DOCUMENTATION "Default domain (documentation field)"
MAXIMUM_MESSAGE_SIZE 1000000 B
SERVER TYPE EXECUTION_SERVER
CHECK_INTERVAL 300 SECONDS
NUMBER_OF_INSTANCES 2
EXTERNAL_CONTROL NO
NO IMMEDIATE_CLEANUP
NAVIGATION_TRANSACTION_THRESHOLD 1999999999
SERVER TYPE SCHEDULING_SERVER
START_MODE IMMEDIATE
CHECK_INTERVAL 5 SECONDS
CREATE_NOTIFICATION_ITEMS_THRESHOLD 10
DELETE_NOTIFICATION_ITEMS_THRESHOLD 10
NOTIFICATION_CHECK_INTERVAL 5 SECONDS
SERVER TYPE CLEANUP_SERVER
START_MODE DEFERRED
CHECK_INTERVAL 300 SECONDS
CLEANUP_TIME 604800 SECONDS
CLEANUP_DELAY_TIME 3600 SECONDS
SERVER TYPE PROGRAM_EXECUTION_SERVER
NUMBER_OF_INSTANCES 5
EXTERNAL_CONTROL NO
SUPPORT_MODE SAFE
PLATFORM OS390
IMPLEMENTATION_SUPPORT EXTERNAL
USER_SUPPORT AGENT
PROGRAM_EXECUTION_AGENT
DLL_LOAD_MODE UNLIMITED
PROCESS
NO AUDIT_TO_DB
NO AUDIT_TO_MQ
NOTIFICATION_MODE RUN
REFRESH_POLICY PULL
KEEP_PROCESSES NEVER
KEEP_WORKITEMS NEVER
NO AUTONOMY
ACTIVITY
CHECKOUT_POSSIBLE
INCLUDE_PROCESS_ASSIGNMENT
PREFER_LOCAL_USERS
PREFER_NON_ABSENT_USERS
NO SUBSTITUTION
NOTIFICATION_SUBSTITUTION
NO DUPLICATE_NOTIFICATION
PROGRAM
FENCED_MODE
KEEP_LOADED
EXECUTION_MODE NORMAL
EXECUTION_USER AGENT
INPUT_CONTAINER_ACCESS
OUTPUT_CONTAINER_ACCESS
NO DLL_V2_COMPATIBILITY
NOT TRUSTED
IMPORT
DO NOT OVERWRITE
OPERATION
SYSTEM_QUALIFIER "FMC"
OPERATION_MODE ROBUST
EXTERNAL_RESTART NO
MAXIMUM_QUERY_MESSAGE_SIZE 1000000 B
CLIENT_MESSAGE_EXPIRATION_TIME 900 SECONDS
MESSAGE_RETAIN_PERIOD 604800 SECONDS
ERROR_RETAIN_PERIOD 604800 SECONDS
MESSAGE_RETRY_LIMIT 5
SESSION
SESSION_EXPIRATION_TIME 72000 SECONDS
SESSION_EXPIRATION_CHECK_INTERVAL 3600 SECONDS
NO UNIFIED_LOGON
END 'DOMAIN'
/*
* GROUPs
*/
UPDATE GROUP 'FMCGRP'
DESCRIPTION "Default system group"
RELATED_DOMAIN 'DOMAIN'
OPERATION
SYSTEM_QUALIFIER "FMC"
END 'FMCGRP'
/*
* SYSTEMs
*/
UPDATE SYSTEM 'FMCSYS'
DESCRIPTION "Default system"
RELATED_QUEUE_MANAGER 'FMCQM'
RELATED_GROUP 'FMCGRP'
SYSTEM_IDENTIFIER 1
PRIMARY_SYSTEM
VERSION 3
RELEASE 5
LEVEL 0
SERVER TYPE SCHEDULING_SERVER
START_MODE IMMEDIATE
CHECK_INTERVAL 5 SECONDS
NOTIFICATION_CHECK_INTERVAL 60 SECONDS
END 'FMCSYS'
SYSTEM 'FMCSYS2'
DESCRIPTION ""
RELATED_QUEUE_MANAGER 'FMCQM4'
RELATED_GROUP 'FMCGRP'
SYSTEM_IDENTIFIER 2
NO PRIMARY_SYSTEM
VERSION 3
RELEASE 5
LEVEL 0
END 'FMCSYS2'
/*
* SERVERs
*/
UPDATE SERVER 'CLEANSVR'
DESCRIPTION "Default cleanup server"
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE CLEANUP_SERVER
END 'CLEANSVR'
UPDATE SERVER 'EXECSVR'
DESCRIPTION "Default execution server"
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE EXECUTION_SERVER
END 'EXECSVR'
UPDATE SERVER 'SCHEDSVR'
DESCRIPTION "Default scheduling server form rahman"
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE SCHEDULING_SERVER
END 'SCHEDSVR'
UPDATE SERVER 'PESERVER'
DESCRIPTION "Default program execution server"
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE PROGRAM_EXECUTION_SERVER
END 'PESERVER'
SERVER 'TEST'
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE USER_DEFINED_PROGRAM_EXECUTION_SERVER
MQSYSTEM MQSERIES
MESSAGE_FORMAT XML
PHYSICAL_QUEUE_NAME "UPES.QUEUE"
QUEUE_MANAGER_NAME "FMCQM"
VERSION 3
RELEASE 5
LEVEL 0
END 'TEST'
SERVER 'NOOP'
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE USER_DEFINED_PROGRAM_EXECUTION_SERVER
MQSYSTEM MQSERIES
MESSAGE_FORMAT XML
PHYSICAL_QUEUE_NAME "lo"
VERSION 3
RELEASE 5
LEVEL 0
END 'NOOP'
SERVER 'UPES1'
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE USER_DEFINED_PROGRAM_EXECUTION_SERVER
MQSYSTEM MQSERIES
MESSAGE_FORMAT XML
PHYSICAL_QUEUE_NAME "UPES1.QUEUE"
QUEUE_MANAGER_NAME "FMCQM"
VERSION 3
RELEASE 5
LEVEL 0
END 'UPES1'
SERVER 'UPES2'
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE USER_DEFINED_PROGRAM_EXECUTION_SERVER
MQSYSTEM MQSERIES
MESSAGE_FORMAT XML
PHYSICAL_QUEUE_NAME "UPES2.QUEUE"
QUEUE_MANAGER_NAME "FMCQM"
VERSION 3
RELEASE 5
LEVEL 0
END 'UPES2'
SERVER 'UPES3'
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE USER_DEFINED_PROGRAM_EXECUTION_SERVER
MQSYSTEM MQSERIES
MESSAGE_FORMAT XML
PHYSICAL_QUEUE_NAME "UPES3.QUEUE"
QUEUE_MANAGER_NAME "FMCQM"
VERSION 3
RELEASE 5
LEVEL 0
END 'UPES3'
now i can see the changes in the sheduling server but instead of 5 seconds the for the notification check interval i am seeeing 1 MINUTE
s
FMC15053I Scheduling Server Commands Menu:
i ... Info
u ... Startup
d ... Shutdown
q ... Query
w ... Wait
x ... Exit Scheduling Server Commands Menu
i
- Scheduling server settings
- Check interval PT5S
- Start mode Immediate
- Notification check interval PT1M
- Create notification items threshold 10
- Delete notification items threshold 10
FMC15053I Scheduling Server Commands Menu:
i ... Info
u ... Startup
d ... Shutdown
q ... Query
w ... Wait
x ... Exit Scheduling Server Commands Menu
> 12/3/2004 2:22:10 PM FMCSYS: FMC00100E Internal error |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jan 03, 2005 1:01 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| Code: |
SERVER TYPE SCHEDULING_SERVER
START_MODE IMMEDIATE
CHECK_INTERVAL 5 SECONDS
CREATE_NOTIFICATION_ITEMS_THRESHOLD 10
DELETE_NOTIFICATION_ITEMS_THRESHOLD 10
NOTIFICATION_CHECK_INTERVAL 5 SECONDS |
Change CHECK_INTERVAL 5 seconds back to 300 seconds. This is the interval that the ADMIN server uses to check the health of the other Servers. It has nothing to do with the problem you are having and may in fact cause some problems.
Why do things look different if you restarted the system?
The only thing I can think of is that you have Scheduling Server info specified under your SystemGroup or System. Please dump the fdl for those from this system so we can have a look
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| mahek |
| Posted: Mon Jan 03, 2005 1:35 pm Post subject: |
|
|
Voyager
Joined: 10 Sep 2004
Posts: 87
|
Hi jamac ,
I think you are right we have the domain properties in that i have selected the complete scheduling server seetings and given check interval as 5 seconds and server start as automatic and for the serve specific tab i have given notification check interval as 5 seconds.
Now in the DOMAIN in FMCGRP,FMCSYS then SCHEDSVR properties(the scheduling server properties inside the FMCSYS) THE INHERITED tab is not checked for the scheduling server and it is checked forall other servers in this for the scheduling server properties the check interval as 5 seconds and server start as automatic and for the serve specific tab it is given notification check interval as 1 minute. I am just confused where to make the changes for the scheduling server in the domain or in the FMCSYS .
HERE IS THE FDL WHICH I IMPORTED FOR THE PROCESS
/*
*
* FDL definitions generated by MQ Workflow at 2004-12-03, 2:38:54 PM.
*
*/
CODEPAGE 1252
FM_RELEASE V3R5 0
/*
* STRUCTUREs
*/
UPDATE STRUCTURE 'Default Data Structure'
END 'Default Data Structure'
/*
* PROGRAMs
*/
PROGRAM 'rahman'
STRUCTURES_FROM_ACTIVITY
NOT UNATTENDED
WINNT EXE PATH_AND_FILENAME "C:\Program Files\IBM WebSphere MQ Workflow\BIN\fmcnshow.exe"
INHERIT ENVIRONMENT
STYLE VISIBLE
START FOREGROUND
END 'rahman'
/*
* PERSONs
*/
UPDATE PERSON 'ADMIN'
AUTHORIZED_FOR STAFF
AUTHORIZED_FOR AUTHORIZATION
AUTHORIZED_FOR OPERATION
AUTHORIZED_FOR TOPOLOGY
AUTHORIZED_FOR PROCESS_MODELING
AUTHORIZED_FOR PROCESS_CATEGORY ALL AS_ADMINISTRATOR
AUTHORIZED_FOR WORKITEMS_OF ALL
RELATED_ROLE 'System administrator'
PASSWORD %F5E2FF2FA2F06A33133BEE48DB1ED773
IS_NOT_ABSENT
DO NOT RESET_ABSENT
GROUP 'FMCGRP'
SYSTEM 'FMCSYS'
END 'ADMIN'
/*
* SERVERs
*/
UPDATE SERVER 'CLEANSVR'
DESCRIPTION "Default cleanup server"
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE CLEANUP_SERVER
END 'CLEANSVR'
UPDATE SERVER 'EXECSVR'
DESCRIPTION "Default execution server"
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE EXECUTION_SERVER
END 'EXECSVR'
UPDATE SERVER 'SCHEDSVR'
DESCRIPTION "Default scheduling server form rahman"
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE SCHEDULING_SERVER
END 'SCHEDSVR'
UPDATE SERVER 'PESERVER'
DESCRIPTION "Default program execution server"
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE PROGRAM_EXECUTION_SERVER
END 'PESERVER'
/*
* QUEUE_MANAGERs
*/
UPDATE QUEUE_MANAGER 'FMCQM'
DESCRIPTION "Default queue manager"
QUEUE_MANAGER_NAME "FMCQM"
RELATED_SYSTEM 'FMCSYS'
SYSTEM MQSERIES
END 'FMCQM'
/*
* NODEs
*/
UPDATE NODE 'Default Node'
RELATED_QUEUE_MANAGER 'FMCQM4'
OPERATING_SYSTEM WINNT
END 'Default Node'
/*
* PROCESSes
*/
/*
* PROCESS NOTIFICATION
*/
PROCESS 'NOTIFICATION' ( 'Default Data Structure', 'Default Data Structure' )
CATEGORY 'A'
DO NOT PROMPT_AT_PROCESS_START
WINDOW VIEW_REFERENCE_POINT XPOS -8 YPOS 502
WINDOW SHOW ALL CONNECTORS
WINDOW SHOW ALL CONDITIONS
SOURCE 1 XPOS -900 YPOS 800
PROGRAM_ACTIVITY 'NoResponseFollowup' ( 'Default Data Structure', 'Default Data Structure' )
START MANUAL WHEN AT_LEAST_ONE CONNECTOR TRUE
EXIT AUTOMATIC
LAYOUT XPOS 100 YPOS 0
NAME_POSITION XPOS 100 YPOS -75
PRIORITY DEFINED_IN INPUT_CONTAINER
PROGRAM 'rahman'
SYNCHRONIZATION NESTED
END 'NoResponseFollowup'
PROGRAM_ACTIVITY 'ProcessQuestionnaireResult' ( 'Default Data Structure', 'Default Data Structure' )
START MANUAL WHEN AT_LEAST_ONE CONNECTOR TRUE
EXIT AUTOMATIC
LAYOUT XPOS 700 YPOS 600
NAME_POSITION XPOS 700 YPOS 525
PRIORITY DEFINED_IN INPUT_CONTAINER
PROGRAM 'rahman'
SYNCHRONIZATION NESTED
END 'ProcessQuestionnaireResult'
PROGRAM_ACTIVITY 'SendQuestionnaireToCustomer' ( 'Default Data Structure', 'Default Data Structure' )
START MANUAL WHEN AT_LEAST_ONE CONNECTOR TRUE
EXIT AUTOMATIC
LAYOUT XPOS -600 YPOS 600
NAME_POSITION XPOS -600 YPOS 525
PRIORITY DEFINED_IN INPUT_CONTAINER
PROGRAM 'rahman'
SYNCHRONIZATION NESTED
END 'SendQuestionnaireToCustomer'
PROGRAM_ACTIVITY 'WaitForCustomerResponse' ( 'Default Data Structure', 'Default Data Structure' )
START MANUAL WHEN AT_LEAST_ONE CONNECTOR TRUE
EXIT AUTOMATIC
LAYOUT XPOS 100 YPOS 600
NAME_POSITION XPOS 100 YPOS 525
PRIORITY DEFINED_IN INPUT_CONTAINER
NOTIFICATION TO 'ADMIN'
AFTER 9 SECONDS
EXPIRATION AFTER 30 SECONDS
PROGRAM 'rahman'
SYNCHRONIZATION NESTED
END 'WaitForCustomerResponse'
CONTROL
FROM 'SendQuestionnaireToCustomer' TO 'WaitForCustomerResponse'
CONTROL
FROM 'WaitForCustomerResponse' TO 'NoResponseFollowup'
WHEN "_STATE() = _Expired"
XPOS 100 YPOS 275
CONTROL
FROM 'WaitForCustomerResponse' TO 'ProcessQuestionnaireResult'
WHEN "_STATE() <> _Expired"
XPOS 400 YPOS 575
DATA
FROM SOURCE 1 TO 'SendQuestionnaireToCustomer'
MAP '_STRUCT' TO '_STRUCT'
DATA
FROM 'SendQuestionnaireToCustomer' TO 'WaitForCustomerResponse'
MAP '_STRUCT' TO '_STRUCT'
LAYOUT
XPOS -300 YPOS 800
DATA
FROM 'WaitForCustomerResponse' TO 'NoResponseFollowup'
MAP '_STRUCT' TO '_STRUCT'
LAYOUT
XPOS -300 YPOS 400
XPOS -200 YPOS 300
DATA
FROM 'WaitForCustomerResponse' TO 'ProcessQuestionnaireResult'
MAP '_STRUCT' TO '_STRUCT'
LAYOUT
XPOS 400 YPOS 800
END 'NOTIFICATION' |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jan 03, 2005 1:42 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
First, if it is possible, simply delete this configuration and start over, that will be a lot easier. You probably should NEVER make any changes to Network objects at a level other than that of the Domain. It just will make things easier for you.
If it is not possible for you to do this you will need to get rid of the items lower in the hierarchy than that of the Domain (i.e SystemGroup and System). Since you did not post the FDL for those 2 objects I do not know what you need to change... Like I said, it will be a lot easier to start over if possible.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| mahek |
| Posted: Mon Jan 03, 2005 1:50 pm Post subject: |
|
|
Voyager
Joined: 10 Sep 2004
Posts: 87
|
| Hi jmac i have changed the properties of the scheduling server in the FMCSYS the properties of scheduling server in the DOMAIN and at the FMCSYS level are same now i have imported just the domain into the fdl and have imported it in to the runtime now it is reflecting the changes made to the scheduling server thanks a lot fo the help. |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jan 03, 2005 1:54 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
If you do not delete those extra parameters they may come back and bite you later. It's your call....
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| sac |
| Posted: Mon Jan 03, 2005 9:11 pm Post subject: |
|
|
Apprentice
Joined: 10 Feb 2003
Posts: 44
|
Hi mahek,
Just one suggestion...it' snot relating to the problem that you posted.
The process FDL that you posted,you also had the network topology definitions merged in your process FDL. The good practice is that you should keep separate FDL's for your Process, Staff, Network and Program Definitions. This is a better approach to keep things more modularised.
For e.g If tomorrow there is change in your Staff defintions, you need to to import only the Staff FDL rather than importing all the defined objects. |
|
| Back to top |
|
|
|
|
