The Create a Job dialog box allows you to select the type of Job object that you want to create and then provide the Job name. If the server in which you are creating a job is version 3.5 or later, Designer provides a list of default job definitions to choose. The job definitions are guaranteed to exist on the server
Additionally, a Live Update button next to the server selection box queries the selected server and retrieves any or all custom job definitions. Job definitions are filtered from this dialog box, based on containment rules. All shipping 3.5 jobs support only Driver containment and will, therefore, not be selectable when creating a job under a driver set. Under these circumstances, the list of job definitions for the selected server is empty, and a job can not be created. The list of job definitions refreshes upon each server selection.
If any Server object contained in a driver set is set to a version earlier than 3.5, Designer prevents creating Job Scheduler objects and displays the following dialog box:
The general page displays the job definition. Additionally, you can specify a job to be removed after Job Scheduler runs once. A job can also be disabled or turned off from this page. Server and Scope assignments are managed from this page.
A Job Scope repository in Designer enables you to reuse scopes from within the same Identity Vault. For all jobs, the scope selector shows both available and selected scopes, if they exist.
The Create Scope dialog box enables you to create a scope. The UI of this dialog guides you through advanced scope options if you want to filter beyond the eDirectory object that you have specified.
For example, you can choose a container and then target specific classes within this container by browsing the schema.
The Job Parameter page enables you to edit values contained within the job definition. These parameters are displayed in a similar fashion as Engine Controls and GCVs.
The Schedule page enables you to specify simple or advanced scheduling criteria for a job. This UI takes advantage of the power of a crontab. The different options guide you from simple to advanced schedule needs. A simple schedule might be running a job daily at 12:00 am or running every Monday and Wednesday at 6:00 pm.
If you want to leverage the power of crontab and perform advanced scheduling, you can choose the custom option, where you can enter you own crontab data or use the advanced crontab builder dialog. The advanced crontab builder allows multiple times and days to be chosen and enforces proper syntax.
By clicking the Plus button next to the Advanced field, you launch the advanced crontab builder. If crontab data exists in this field and is valid, it is loaded and displayed in the controls. However, if the data exists and is not valid, it is ignored and no settings are displayed. If you click OK on a schedule selection, the previous contents of this custom field are overwritten.
The Notification page enables you to configure notification events for eight different categories. For the Intermediate and Final categories, there are Success, Warning, Error and Abort options. You can enable email or Novell Audit for each notification option. If email is enabled, the default Novell job template is automatically selected.
You can optionally create and browse to a custom email template or modify the default shipping template from the Email Notification Editor. Part of the email notification setup requires the setup of email recipients. For flexibility, a job allows you to choose different recipient lists for each category. Designer has therefore provided an eMail Profile object that can be reused across the entire project so that you do not have to redundantly enter contact information. Currently, this email profile is only accessible by jobs but will be used later with other features that require email recipient input.
For further information on how Job objects function and how to use them refer to the Identity Manager Engine Documentation for version 3.5.