JobDispatcherConfig.properties file
The parameters in this file affect the following settings for the dynamic workload broker server installed on a master domain manager or dynamic domain manager:
- Encryption of any passwords sent in the JSDL definitions
- Time interval for retrying the operation after a Job Dispatcher failure
- Time interval for retrying the operation after a client notification failure
- Archive settings for job data
- Job history settings
- Gateways and dynamic workload broker server connection settings.
After modifying the file, you must stop and restart the IBM® WebSphere® server.
During the upgrade from version 8.5.1 the values you set for the properties for version 8.5.1 are preserved. The default values for the properties for version 8.6 are different from those in version 8.5.1. If you want to use the version 8.6 defaults, change them manually.
In the JobDispatcherConfig.properties file,
the following parameters are available:
- DatabaseCheckInterval
- Specifies the time interval within which the dynamic workload broker server checks the availability of the database. The default value is 180 seconds.
- EnablePasswordEncryption
- Specifies that any user passwords contained in the JSDL definitions are to be encrypted when the definitions are sent to the agents. The default is true. Setting this property to false forces the dynamic workload broker server to send the passwords in plain text. This applies to any password field.
- RAEndpointAddress
- Specifies the URL of the Resource Advisor.
- JDURL
- Specifies the URL of the Job Dispatcher.
- FailQInterval
- Specifies the numbers of seconds for retrying the operation after
the following failures:
- Client notification.
- Allocation, Reallocate, Cancel Allocation requests to Resource Advisor.
- Any database operation failed for connectivity reasons.
- MaxCancelJobAttemptsCount
- The maximum number of times the Job Dispatcher attempts to cancel a shadow job or a job running on a dynamic agent when a request to kill the job is made and the kill request cannot be immediately processed. The default is 1440 attempts. The Job Dispatcher attempts to cancel the job every 30 seconds for a maximum number of times specified by this parameter.
- MaxNotificationCount
- Specifies the maximum number of retries after a client notification failure. The default value is 1440. For example, if the workload broker workstation is processing a new Symphony file, this operation might require some time, so you should set this parameter to a high value. If you are not using the workload broker workstation, this parameter can be set to a lower value.
- MoveHistoryDataFrequencyInMins
- Specifies how often job data must be deleted. The unit of measurement is minutes. The default value is 60 minutes. Increasing this value causes the Job Dispatcher to check less frequently for jobs to be deleted. Therefore, the volume of jobs in the Job Repository might increase and all queries might take longer to complete. Dynamic workload broker servers with high job throughput might require lower values, while low job throughputs might require higher values.
- SuccessfulJobsMaxAge
- Specifies how long successfully completed or canceled jobs must be kept in the Job Repository database before being archived. The unit of measurement is hours. The default value is 240 hours, that is ten days.
- UnsuccessfulJobsMaxAge
- Specifies how long unsuccessfully completed jobs or jobs in unknown status must be kept in the Job Repository database before being archived. The unit of measurement is hours. The default value is 720 hours, that is 30 days.
- AgentConnectTimeout
- Specifies the number of minutes that the dynamic workload broker server waits for a scheduling agent response after it first attempts to establish a connection with that agent. If the agent does not reply within this time, the server does not open the connection. Values range from 0 to 60 (use 0 to wait indefinitely). The default is 3.
- AgentReadTimeout
- Specifies the number of minutes that the dynamic workload broker server waits to receive data from established connections with a scheduling agent or a gateway. If no data arrives within the specified time, the server closes the connection with the agent. Values range from 0 to 60 (use 0 to wait indefinitely). The default is 3.
- GatewayPollingTimeout
- Add this parameter to specify the number of minutes that the gateway waits to receive data from established connections with a dynamic workload broker. If no data arrives within the specified time, the gateway closes the connection with the dynamic workload broker. Values range from 1 to 60. The default is 1 minute.
- GatewayConnectionTimeout
- Add this parameter to specify the number of seconds that the dynamic workload broker server waits for a gateway receiving data after the dynamic workload broker first attempts to send data to the gateway. If the gateway does not reply within this time, the dynamic workload broker does not open the connection. Values range from 1 to 60. The default is 10 seconds.
- MaxNumberOfParallelGateways
- Add this parameter to specify the number of gateways that dynamic workload broker server can manage without lack of performances. Values range from 3 to 100. The default is 3.
Note:
You can use this file to configure the product behavior when archiving job data. For more information about archive tables, see Historical database tables created during installation.
If an unexpected job workload peak occurs and a cleanup of the database is required earlier than the value you specified in the MoveHistoryDataFrequencyInMins parameter, you can use the movehistorydata command to perform a cleanup before the scheduled cleanup is performed.