Job General Page

Name

Provide a descriptive name for the job (255 characters maximum). The name is used throughout adTempus to identify the job, and must be unique within the group that the job belongs to.

If you try to use a name that is already in use on another job, you will receive an error message when you try to save the job. Note that the other job with the same name may not be visible to you (based on security settings).

The name can be changed at any time without affecting links between jobs.

Job ID

The Job ID is a 38-character system-generated unique identifier for the job. This ID remains constant even if the name of the job changes. The Job ID is shown primarily for use in diagnostic situations but can be used instead of the name in command-line utilities such as adtExec.

Queue

Select the Queue to which this job is assigned.

Priority

Specify the priority of this job within the queue. In a queue that limits the number of jobs that can run simultaneously, jobs with higher priorities are executed before jobs with lower priorities. New jobs have a default priority of 100. A higher priority is indicated by a higher priority number: for example, a job with priority 200 has a higher priority (and will run before) a job with priority 100.

User Account

Specify the Windows user account that the job should be run under. See Entering User Credentials for more information on how to enter the credentials.

All tasks performed by this job will be run under the user account you specify. For example, when the job executes a program, the program will operate under the same security context (and restrictions) as if the specified user had run the job herself.

Run with highest privileges

If the specified User Account is an administrative account, check the Run with highest privileges option to have administrative privileges enabled when the program runs. This is equivalent to using the "Run as administrator" command in Windows. If this option is not checked, administrative privileges will not be enabled, and the program may not behave as you expect.

If theUser Account is not an administrative account, checking this option has no effect on program execution.

This option is not available if the adTempus server is running Windows XP, Windows Server 2003, or earlier.

User Interaction

New feature icon This option has been simplified from the settings available in adTempus 3.

Select whether a user needs to be able to see or interact with programs run by your job.

Each job runs in one of the following sessions:

Hidden. (Default and recommended setting) The job will be run in a hidden session. If the programs run by the job display a user interface, no user will be able to see them.
Interactive if available. If the user whose account is used to run the job is logged on interactively at the computer, adTempus will run the job in that logon session. The user will be able to see the user interface for any programs run by the job. If the user has more than one interactive logon session, the program will run in the logon session that was created first. If the user is not logged on, the job will run in a Hidden session.
Interactive required. This option is the same as Interactive if available, except that the job will fail if no interactive session is available.

A program that is properly designed for "batch" execution should not rely on direct interaction with users, and therefore should not need to display a user interface. For such programs, use the "Hidden" session whenever possible. This provides more security, and eliminates the annoyance of program windows popping up while a user is logged in to the computer.

Regardless of what interaction level is selected, if you run the job manually while logged in to the computer, you can choose to have the job executed in your current logon session. This is useful if you need to be able to see the user interfaces of the job's programs during job debugging.

If the adTempus administrator has disabled interactive job execution, only the "Hidden" option will be available.

Hold Status

The Hold Status determines whether and how the job can be executed.

Enabled (not held). The job can be run by Triggers, Responses, and on-demand. Checking or unchecking this box unchecks or checks the other three options. If this option is checked, the job is fully enabled for all execution types.
Hold triggers. All Triggers defined for the job are ignored. Note: This option holds all triggers for the job, not just Schedule Triggers.
Prevent chained execution by other jobs. Any Job Control Actions that target the job will be prevented from executing it. adTempus will log an error message in the job log for the calling job, indicating that the target job cannot be run
Prevent manual execution. Users will be prevented from executing the job on-demand using the Run command or the adtexec utility.

The Hold Status replaces the Enabled option (and corresponding Hold/Release commands) used in prior versions of adTempus. The Prevent chained execution option replaces the Allow job to be triggered by other jobs option that previously appeared on the Triggers page.

History Retention

Specify how long adTempus should retain the history for this job. The default setting is specified in the Server Options window.