Configuring ART Batch Specific Servers

Server Template

The ART Batch related servers can be added using the server template.

The machine list contains all the machines that have been added into this domain.

Selecting one or more machines, and then click Apply Server Template. Following servers are added to the machine.

• JESQUEGRP

  • TMQUEUE

• ARTJESGRP

  • TMUSREVT

  • ARTJESADM

  • ARTJESCONV

  • ARTJESINITIATOR

  • ARTJESPURGE

Since the TMS_QM used by server TMQUEUE requires TLOG device, after applying the server template, TLOGDEVICE and TLOGSIZE parameter of the corresponding machine will be configured to $APPDIR/TLOG if no path is specified.

JES Configuration File

A JES configuration file is used by the TuxJES administration server ARTJESADM. You can configure the following parameters of the JES configuration file:

• JES Base Directory

  The base directory to store the JESROOT. If it is not set, the base directory is $APPDIR.

• JESROOT

  The root repository to store job information. This directory is created under the path set in JES Base Directory. For example, if JESROOT is set to jesroot and JES Base Directory is set to $APPDIR, the full path of the JESROOT directory is {$APPDIR}/jesroot.

  
  

  Note: If ART Batch related servers are configured on two Tuxedo machines, they must share the same JESROOT repository, which means only an absolute JESROOT path is acceptable and the directory should exist in Network File System.

  
  

• DEFAULTJOBCLASS

  The default job class if the job class has not been set in JCL. It is optional. The default job class is A if this option is not set.

• DEFAULTJOBPRIORITY

  The default job priority if the job priority has not been set in JCL. It is optional. The default job priority is 0 if this option is not set.

• DUPL_JOB

  If NODELAY is not checked, only one job can be in execution status for a job name. When it is checked, NODELAY will remove the dependency check.

• EVENTPOST

  Specifies whether events are posted for a job at particular stages.

  • S: Job submission event.

  • C: Job conversion complete event.

  • E: Job execution complete event.

  • P: Job purge event.

  • A: all supported events

  If EVENTPOST is not specified, no event is posted. The data buffer with event post is FML32 type and the fields are defined in tuxjes/include/jesflds.h.

• JOBREPOSITORY

  The path of the stored job repository. The job submitting script file path may be a relative path in JOBREPOSITORY if it is set.

• PRIVILEGE MODE

  Specifies whether and how to enable the user substitution.

  • NONE: Default value. Indicates jobs are executed by the OS user who starts JES system. This is compatible with all previous implementations on JES system.

  • USER_IDENTICAL: Indicates jobs are executed by the Oracle Tuxedo user with which JES client joins JES system. Make sure that each Oracle Tuxedo user corresponds to an existing OS user before you choose this option.

  • USER_MAPPING: When this option is selected, the JES system looks up the TuxJES user mapping file and finds out the OS user corresponding to the Oracle Tuxedo user with which JES client joins JES system, and then appoints this OS user as the job executor.

• USER MAPPING FILE

  This option is enabled when you choose USER_MAPPING as Privilege Mode. Specify the user mapping file name. User mapping file is put under $APPDIR directory by default.

  
  

  Note: User Mapping File name cannot be: one of Logs, QUE,TLOG, UBBCONFIG, acc, crlog, data, data_source, jesconfig, jesqinit, tools, tpacl, tpgrp, tpusr, and tuxconfig. same with JESROOT if JESROOT is under $APPDIR directory.

  
  

• USER MAPPING Table

  User mapping table displays the mapping relationship between Oracle Tuxedo users and OS users. When the Privilege Mode is USER_MAPPING, the user mapping table is enabled, allowing you to add, edit, or delete a user mapping entry. Every line in the mapping table is in the format as below:

  tuxedousername OSusername

  
  

  Note: No duplicated user pair is allowed. One Oracle Tuxedo user can only be mapped to one OS user.

  
  

Misc Configuration

There are several fields used for collecting ART Batch related information:

• JES queue init script

  The JES queue initializing script. The one provided in the JES simpjob sample is used as the default template. You can customize it in the text field, if you do so, the queue file name must be "QUE".

• JES install dir

  The ART Batch installation directory must be specified in the page. It is a mandatory option.

  There is a requirement here, when configuring a MP domain, the ART Batch installation directory path on all the machines must be the same.

• PDKSH

  The PDKSH executable file which is used for ART Batch running. This is an optional option. If it is not specified, the system default ksh command is used at runtime.