The following steps provide instructions for using Identity Console to add all of the predefined jobs (Driver Health, Password Expiration Notification, Random Password Generator, Schedule Driver, Subscriber Channel Trigger). For information about using Designer to add jobs, see Scheduling Jobs
in the NetIQ Designer for Identity Manager Administration Guide.
Click IDM Administration tab from the Identity Console home screen.
(Conditional) If you want to add the job to a driverset:
Click the Action menu icon on the appropriate driver set and select Driver Set Properties.
Click Advanced > Jobs.
Click the + Create a new job icon.
(Conditional) If you are adding the job to a driver:
Click the driver to display the driver properties page.
Click Advanced > Jobs.
Click the + Create a new job icon.
In the Job Name field, specify a descriptive name for the job.
Under Job Type, make sure that Installed is selected, then choose one of the following job types:
Driver Health (Driver Set): Evaluates the health conditions for a driver, assigns the health state, and carries out any actions associated with the health state.
Password Expiration Notification (Driver Set): Sends e-mail notifications to users whose passwords are about to expire.
Random Password Generator (Driver Only): Generates a random password for each object in the job’s scope. The password is generated by NMAS to match the Password Policy object that the job references. These Password Policy objects are not usually the same as those used for eDirectory user password policies.
The job submits the generated passwords one at a time to the driver’s Subscriber channel. The Subscriber channel policies must take action on the passwords.
Schedule Driver (Driver Only): Starts or stops the associated driver. You can also toggle a driver to start the driver if it is stopped or to stop the driver if it is running.
Subscriber Channel Trigger (Driver Only): Submits zero or more trigger documents to the Subscriber channel. The submission can either be a document per object if a scope is defined, or it can be a single trigger event if no scope is defined.
Trigger event documents identify the job and the scope object. A trigger event can bypass the cache and be processed immediately if desired. Trigger jobs allow you to use driver policies that you can customize for your personal requirements.
In the Server(s) to run this job field, select the servers where you want to run the job.
Click Create.
Under Advanced > Jobs, select the newly created job name to display its configuration properties.
To configure the job’s properties, continue with the instructions in the appropriate section: