14.2 Editing a Job

After you create a job, you need to add the necessary information to make the job useful. To edit a job, double-click a newly created job in the Outline view to bring up the job in the IDM Job Editor view.

Figure 14-2 The IDM Job Editor View

The IDM Job Editor has four tabs at the bottom of its view:

14.2.1 Job Editor Selections on the General Settings Page

The title of the General Settings Page shows the Java class name of the job. This is followed by the job type, which shows the type of job you selected. Under the Job Type heading, you can enable or disable the job, or to delete the job after it runs.

Figure 14-3 Items Under the General Tab

  1. To delete the job after it runs, select Delete job after running once.

  2. To disable the job from running, deselect Enable job.

  3. In the Servers column, select the server or servers where this job should run.

    A filtered list of servers is available to help you assign this job. A custom job can be installed on one server but not on another. In this case, the server without this custom job is filtered out of the Server List.

    A job can be assigned to multiple servers as long as it has been installed on each server. Designer only allows this association if the jobs are properly installed and packaged so that the Metadirectory engine can see them.

  4. To add a scope to the Scopes column, click New Scope.

    Specifying the job scope criteria

  5. To select a scope object, type the Distinguished name of the object or use the Browse icon to browse to the object. Click OK to add the scope object.

    Scopes allow you to define the objects that this job applies to. An object in eDirectory can be a container, a dynamic group, a group, or a leaf object. If you select a group object, you can apply the job to the group's members, or only to the group. If you select a container object, you can apply the job to all descendants in that container, to all of the children in the container, or to the container only.

  6. If the object is a container, select Scope is a Container. Then select how you want to apply the job:

    • Apply job to this container only

    • Apply job to children of this container

    • Apply job to all descendants of this container

  7. (Optional) If you select Apply job to children of this container or Apply job to all descendants of this container, you can specify the classes and attributes you want to scope. Click the plus icon to bring up the Schema Browser window to select the classes you want to scope. Select the class schema, then click OK.

    Select the Plus icon to bring up the Schema Browser window

    The classes are added to the Classes box. To remove a class, select it and click the minus icon.

  8. If the object is a group or a dynamic group, select Scope is a Group/Dynamic Group. You can then select the Scope is the group itself and not its members option if the scope is for the group.

  9. If the object is a non-container, select Scope is a Non-Container.

  10. After the scope criteria are selected, click OK to return to the General Settings page.

  11. If you need to edit a scope, select the scope name, then click Edit.

  12. To remove a scope, select the scope name, then click Remove.

Deploying a Job with Scope Objects

Jobs might need access to eDirectory data and certain Identity Manager actions, such as starting and stopping drivers. Such access is subject to eDirectory rights assignments and is controlled by the rights that are granted to the DirXMLJob object. Although Identity Manager actions are controlled by special attributes, normal eDirectory rights are needed for data reads and writes.

When you deploy a job object that has scope objects, there might be eDirectory rights assignments that Designer cannot properly set up. The rights needed to complete the task depend on the scope objects that are assigned to the job object.

Figure 14-4 Warning Messages When Deploying a Job with Scope Objects

If you see this warning when deploying job objects, use the iManager utility to assign eDirectory rights to the job object so it can properly access the job scope objects and complete its task.

14.2.2 Job Editor Selections on the Job Parameters Page

The Job Parameters page allows you to add additional parameters to the job and to view the parameters as they are presently set up. What you can do depends on the type of job you selected.

NOTE:The parameters for a custom job vary based on the job’s design. For more information about creating a custom job, see Section 14.1, Creating a Job.

Parameters for the Schedule Driver Job

Figure 14-5 The Job Parameter Page for a Schedule Driver Job

  1. If you want the job to start the driver, select Start the driver.

  2. If you want the job to stop the driver, select Stop the driver.

  3. If you want the job to switch from one to the other, select Toggle the driver.

Parameters for the Generate Random Passwords Job

Figure 14-6 The Job Parameter Page for the Generate Random Password Job

  1. Type the Password policy object’s Distinguished name, or use the Browse icon to select the Password policy you want to use for password generation.

  2. If you want to generate passwords for scoped objects without a driver association, select True. Otherwise, select False.

Parameters for the Subscriber Channel Trigger Job

Figure 14-7 The Job Parameter Page for the Subscriber Channel Trigger Job

  1. If you want to submit a trigger document for scoped objects that do not have a driver association, select True. Otherwise, keep the default of False.

  2. If you want to use the job’s Common Name (CN) as a document identifier trigger, keep the default of True. Otherwise, select False.

  3. (Optional) If you select False, enter the string that the job can use as the value for the trigger element’s Source attribute.

  4. Select a method for submitting the trigger documents. If you want to queue the job the trigger is from, keep the default of Queue (use cache). Otherwise, select Direct (bypass cache).

  5. (Optional) If you select Direct (bypass cache), you are presented with the Start driver if not running option. If you want to start the driver if it is not running, keep the default of True. Otherwise, select False.

  6. (Optional) If you select True on the Start driver if not running option, you are presented with the Stop driver when finished processing triggers option with the default of True. Use the default to stop the driver once it finishes processing the trigger job, or select False to keep the driver running.

A customized job definition has its own parameter set.

14.2.3 Job Editor Selections on the Scheduler Page

The Scheduler page allows you to set up when you want to run the job.

Figure 14-8 The Job Options for the Scheduler Page

  1. Select the Use schedule option to set the date and time, and whether to run the job daily, weekly, monthly, yearly.

    or

    Select the Run job manually option to run the job when you choose to.

  2. With Use schedule selected, set the time when you want the job to start running. Use the drop-down menus to select the hours, minutes, and AM or PM. The default is 1:00 AM.

  3. If you want to run the job repeatedly, use the Daily, Weekly, Monthly, Yearly, or Custom fields to select when you want it to run.

    For example, if you want the job to run weekly, select Weekly, then the day you want it to run on. If you want the job to run once a month, select Monthly, then click the Plus icon to select the day of the month.

    Selecting the days of the month

  4. (Optional) Select Custom, to choose minutes, hours, days, months and days of the week from the Choose Advanced Crontab Criteria page.

    The Advanced Crontab Criteria page

  5. The Choose Advanced Crontab Criteria page default has everything selected. Click Unselect All, choose the time and days you want to run the job, then click OK to return to the Scheduler page.

    The information displayed in the Crontab Text field displays any settings you make on the Scheduler page. For example, if you click Monthly and select two days, those two days are displayed in the Crontab Text field.

14.2.4 Job Editor Selections on the Notification Settings Page

The Notification Settings page allows you to define what you want to do with the job results. It is divided into two parts, Intermediate and Final, with the Success, Warning, Error, and Aborted results for each part.

The Notification Settings page allows you to set how you want to be notified for each result. Actions include sending an audit result or sending an e-mail when the result completes.

Figure 14-9 The Job Options Under the Notification Tab

  1. If you select Send email for this event, Designer allows you to search in the Default Notification Collection directory for an appropriate template to use in the Notification Template field. Click the Model Browser icon to select an appropriate template.

  2. Under Notification Recipients, select who you want to send the results to by typing the user’s or group’s fully distinguished name. You can use the Plus icon to create a mail profile or click the Model Browser icon to choose a mail profile.

    Creating a mail recipient profile

    The To and Reply fields are required for a profile.

  3. When you have filled in the information, click OK.

  4. If you want the results to go to Novell Audit, select Use Novell Audit for this event.

  5. Use Step 1 through Step 4 for each of the options:

    • Intermediate Success

    • Intermediate Warning

    • Intermediate Error

    • Intermediate Abort

    • Final Success

    • Final Warning

    • Final Error

    • Final Abort

    If you do not select an option, no action is taken for the result.