Task Manager configuration

A single configuration file contains parameters that govern various aspects of the Task Manager behavior, including the Task Manager queue process.

com.ibm.mdm.mds.task.manager.cfg

The configuration file is available at <WAS_INSTALL_HOME>/AppServer/profiles/<YOUR_APP_SERVER>/InstalledApps/<CELL_NAME>/MDM-native-<INSTANCE_ID>.ear/native.war/conf/com.ibm.mdm.mds.task.manager.cfg.

The parameters in the table are available if the enabled parameter for the Task Manager is set to true.

Table 1. com.ibm.mdm.mds.task.manager.cfg
Parameter Description Default and examples
enabled Determines whether this operational server instance uses a Task Manager. true
threadCount Determines the number of background Task Manager threads.
Important: Do not change the default value (1). Doing so will negatively impact system performance.
1
pollInterval If the previous attempt to select rows from the input queue returned no results, pollSeconds determines the number of seconds to wait before attempting the request again. 60
tskexp.enabled Enables the Task Manager to poll for expired tasks. false
tskexp.invokeInterval Determines the polling interval for expired tasks, in seconds. This is only applicable if tskexp.enabled is set to true. 3600
tskexp.expTskStat Determines the task status to used if a task is identified as expired. This is only applicable if tskexp.enabled is set to true. 6
fbbrebkt.enabled Enables the Task Manager to poll for newly added frequency strings. false
fbbrebkt.invokeInterval Determines the polling interval for newly added frequency strings. It cross matches the affected members. This is only applicable if fbbrebkt.enabled is set to true. 3600
fbbrebkt.lastMaudRecno Determines the audrecno starting point to use to identify new frequency strings. A value of 0 indicates that the Task Manager uses the current maximum audrecno. Any non-zero value is used as a threshold to re-evaluate strings added after that audrecno. This is only applicable if fbbrebkt.enabled is set to true. 0
workManagerName The jndi service name that background manager executes work under. The full service name would be osgi:service/wm/workManagerName. In general, you should not need to change this parameter. default
workManagerUserName Determines the user name used to run the queue manager background threads. In general, you should not need to change this parameter. (blank)
workManagerPassword The password for the user. In general, you should not need to change this parameter. (blank)
workManagerRealm The authentication realm that the workManagerUserName is authenticated against. In general, you should not need to change this parameter. defaultWIMFileBasedRealm