This section describes the Job Interaction Client which is an interface to the job processing engine of the CGI Advantage application that:
Can be used to submit jobs along with any required parameter values. This information is supplied to the job interaction client through a driver data file in a specific format.
Does not require you to log in to the application through a web browser. All job framework commands are sent using the job interaction client from the command line.
Can be used to control the job framework engine, such as starting and stopping regular job polling by the Job Manager. This periodic polling is used for picking up jobs that have been submitted by users through the online system and have met the scheduled criteria for job execution.
The Job Interaction Client is supported through an EJB client Java class, AMSJobInteractionClient.class, that accesses the Job Manager EJB on the target VLS to provide the functionality outlined above. A number of parameters (both required as well as optional) can be passed to the job using the Job Interaction Client.
The recommended way of invoking the Job Interaction Client is through either a batch file (Windows platform) or a shell script (AIX and Linux platform). The script file sets up the required Java classpath and facilitates the passing of parameters to the Job Interaction Client. The script file acts as a driver for executing the actual Job Interaction Client Java class. Template script files for both platforms are included within the Job Interaction Client folder and can be used as a starting point for creating a site specific script. These template script files, runclient.bat and runclient.sh, are described in more detail in the following sections.
Note: The flags under the Actions section on the Access Control page determine whether a user assigned to a Resource Group/Security Role combination can perform the following actions: Approve (Approve Job), Schedule (Schedule Job), Edit (Edit Job), Submit (Submit Job), Discard (Delete Job), Kill Job, Restart Job, View Completed Jobs, View Pending Jobs, View Others’ Jobs, View Job Log, and View Job Report. Security is enforced for these actions irrespective of the medium through which they are executed (that is, through the Run Batch (BATRUN) page or through the Job Interaction Client). For the Administrator (ADMN) Role the system does not check the Access Control entries and there is no need to setup Access Control entries for this. If a job resource does not have a Resource ID defined on the Setup Batch Job (BATSETUP) page then only the users associated with the ADMN role can access it and perform actions on it.