Job Controller default configuration

The MTA is distributed with an initial Job Controller configuration that is a suitable starting point for most sites. The default configuration defines three pools: (1) one named    with a job limit of ten, to be used for miscellaneous channels, (2) one  named   with a job limit of two, to be used for  running   channel jobs,  and (3) one named    with a job limit of ten, to be used for outbound  TCP/IP SMTP/LMTP channel jobs.

The following figure shows a default configuration in Unified Configuration.

Sample Job Controller option settings in Unified Configuration

msconfig&#x3e; show job_controller role.job_controller.tcp_ports = 27442                                           (3) role.job_controller.job_pool:DEFAULT.job_limit = 10                             (5),(6) role.job_controller.job_pool:IMS_POOL.job_limit = 2 role.job_controller.job_pool:SMTP_POOL.job_limit = 10 role.job_controller.channel_class:bitbucket.master_command = IMTA_BIN:bitbucket (7) role.job_controller.channel_class:bsmtp&#x2a;.master_command = IMTA_BIN:bsout_master (8) role.job_controller.channel_class:bsmtp&#x2a;.slave_command = IMTA_BIN:bsin_master   (8) role.job_controller.channel_class:conversion&#x2a;.master_command = IMTA_BIN:conversion role.job_controller.channel_class:defragment.master_command = IMTA_BIN:defragment role.job_controller.channel_class:filter_discard (novalue)                      (11) role.job_controller.channel_class:hold.master_command = IMTA_BIN:reprocess role.job_controller.channel_class:ims-ms&#x2a;.master_command = IMTA_BIN:ims_master  (9) role.job_controller.channel_class:ims-ms&#x2a;.max_life_askwork = 20000              (9) role.job_controller.channel_class:ims-ms&#x2a;.max_life_time = 14400                 (9) role.job_controller.channel_class:native.master_command = IMTA_BIN:l_master role.job_controller.channel_class:pipe&#x2a;.master_command = IMTA_BIN:pipe_master role.job_controller.channel_class:process&#x2a;.master_command = IMTA_BIN:reprocess role.job_controller.channel_class:reprocess&#x2a;.master_command = IMTA_BIN:reprocess role.job_controller.channel_class:sms&#x2a;.master_command = IMTA_BIN:sms_master role.job_controller.channel_class:tcp_&#x2a;.master_command = IMTA_BIN:smtp_client   (10) role.job_controller.channel_class:uucp_&#x2a;.master_command = IMTA_BIN:uucp_master role.job_controller.channel_class:uucp_&#x2a;.slave_command = IMTA_BIN:uucp_slave instance.job_controller.secret (suppressed)                                     (1) In legacy configuration, the Job Controller configuration is stored in a file,. And in legacy configuration, this Job Controller configuration file is required. If it is not present or its contents are incorrect the Job Controller will not start.

There is no need to modify the Job Controller configuration settings (the Job Controller configuration file in legacy configuration), unless  you choose to add pools, modify pool parameters, modify global Job  Controller settings (such as debugging), or add processing information  for locally developed channels.

In legacy configuration, if you do wish to make such modifications, you should not alter the Job Controller configuration file itself (since it  will be replaced when you upgrade the MTA and in legacy configuration  you will lose your modifications), but rather should create a    file in the MTA table directory  containing your own definitions. The Job Controller configuration file will read in this site supplied file, if it exists.

A sample Job Controller configuration file is shown below. ! ! Global defaults ! SECRET=abc123      (1) SLAVE_COMMAND=NULL (2) TCP_PORT=27442    (3) ! ! Site specific pools and channnels are read ! indirectly if this include file exists. ! &#x3c;IMTA_TABLE:job_controller.site  (4) ! ! Pool definitions ! &#x5b;POOL=DEFAULT&#x5d;  (5) JOB_LIMIT=10   (6) ! &#x5b;POOL=IMS_POOL&#x5d; JOB_LIMIT=2 ! &#x5b;POOL=SMTP_POOL&#x5d; JOB_LIMIT=10 ! ! Channel definitions ! &#x5b;CHANNEL=bitbucket&#x5d;     (7) MASTER_COMMAND=IMTA_BIN:bitbucket ! &#x5b;CHANNEL=bsmtp&#x2a;&#x5d;        (8) MASTER_COMMAND=IMTA_BIN:bsout_master SLAVE_COMMAND=IMTA_BIN:bsin_master ! &#x5b;CHANNEL=conversion&#x2a;&#x5d; MASTER_COMMAND=IMTA_BIN:conversion ! &#x5b;CHANNEL=defragment&#x5d; MASTER_COMMAND=IMTA_BIN:defragment ! &#x5b;CHANNEL=ims-ms&#x2a;&#x5d;       (9) MAX_LIFE_AGE=14400 MAX_LIFE_CONNS=20000 MASTER_COMMAND=IMTA_BIN:ims_master ! &#x5b;CHANNEL=native&#x5d; MASTER_COMMAND=IMTA_BIN:l_master ! &#x5b;CHANNEL=pipe&#x2a;&#x5d; MASTER_COMMAND=IMTA_BIN:pipe_master ! &#x5b;CHANNEL=process&#x2a;&#x5d; MASTER_COMMAND=IMTA_BIN:reprocess ! &#x5b;CHANNEL=sms&#x2a;&#x5d; MASTER_COMMAND=IMTA_BIN:sms_master ! &#x5b;CHANNEL=tcp_&#x2a;&#x5d;         (10) MASTER_COMMAND=IMTA_BIN:smtp_client ! &#x5b;CHANNEL=reprocess&#x2a;&#x5d; MASTER_COMMAND=IMTA_BIN:reprocess ! &#x5b;CHANNEL=uucp_&#x2a;&#x5d; MASTER_COMMAND=IMTA_BIN:uucp_master SLAVE_COMMAND=IMTA_BIN:uucp_slave ! &#x5b;CHANNEL=hold&#x5d; MASTER_COMMAND=IMTA_BIN:reprocess ! &#x5b;CHANNEL=filter_discard&#x5d;  (11) The key items in the above examples are:



  This global option sets a "secret"   used on this host by the Job Controller to verify its internal    communications. 

  Set a default SLAVE_COMMAND for subsequent   &#x5b;CHANNEL&#x5d; sections. 

  This global option defines the TCP port   number on which the Job Controller listens for requests. 

  Attempt to include the optional,   site-supplied   file (in which sites may    place their site-specific customizations, so as to retain such    customizations after upgrading). 

  This &#x5b;POOL&#x5d; section defines a queue named   "DEFAULT". This pool will be used by all channels which do   not specify a pool name using the      channel option. 

 <span id='call_032'> Set the JOB_LIMIT for this pool to 10. </li>

 <span id='call_033'> This &#x5b;CHANNEL&#x5d; section applies to a channel   named bitbucket. The only definition required in this section is   the MASTER_COMMAND which the Job Controller issues to run this channel. (Note that the  channel normally never needs to run, so    normally this image is never executed, since in normal use messages    supposedly "enqueued" to the   channel are instead    merely deleted---however, a   channel image does exist to    delete messages, and if a message does exist in the     channel    queue, perhaps due to being manually placed there by the MTA    administrator, then this channel image can "process" it    ---that is, delete it.) Since no wildcard appears in the channel name,    the channel name must match exactly. </li>

 <span id='call_034'> This &#x5b;CHANNEL&#x5d; section applies to any channel   whose name begins with. For this channel, both a   MASTER_COMMAND and a SLAVE_COMMAND are necessary. Since this channel   name includes a wildcard, it will match any channel whose name begins    with " ". </li>

 <span id='call_035'> This &#x5b;CHANNEL&#x5d; section applies to any channel   whose name begins with. For this channel, used to   deliver to the Messaging Server Message Store, it is a good idea to set the      (formerly MAX_LIFE_AGE)   and     (formerly    MAX_LIFE_CONNS)     Job Controller (channel class) options to let the channel jobs    "persist" (rather than being "recycled" in favor of    a new channel job) for relatively extended periods. </li>

 <span id='call_036'> This &#x5b;CHANNEL&#x5d; section applies to any   channel whose name begins with  ;    this includes SMTP over TCP/IP    and LMTP over TCP/IP channels. This section only defines (the Job   Controller only knows/cares about) a MASTER_COMMAND defining the    SMTP/LMTP client "half" of any such channel; the slave    "half" of any such channel (SMTP servers or LMTP servers) is    handled by the Dispatcher. </li>

 <span id='call_037'> This &#x5b;CHANNEL&#x5d; section applies to the   filter_discard channel. The absence of any MASTER_COMMAND in this section is   intentional. </li>

</ol>

See also:
 * Job Controller
 * Job Controller options
 * slave_command Option
 * master_command Option
 * secret Option
 * job_pool
 * channel_class
 * job_limit Option
 * tcp_ports Option
 * Bitbucket channel
 * BSMTP channels
 * ims-ms channels
 * TCPIP channels
 * filter_discard channel