Identity Manager provides the ability to launch jobs that perform specific tasks. The jobs can be run one or more times either manually or at scheduled times.
Identity Manager provides five predefined jobs:
Random Password Generator: Generates a random password for each object defined in the job’s scope. The password is generated by NMAS™ to match a Password Policy object that the job references. The job submits the generated passwords one at a time to a driver’s Subscriber channel. The Subscriber channel policies must take action on the passwords.
Schedule Driver: Starts or stops a driver.
Subscriber Channel Trigger: Sends event documents to be processed by a driver’s Subscriber channel. For example, a job could generate an event document to trigger policies associated with a user. Submitted event documents can be queued to the driver cache, or they can bypass the cache and be processed immediately.
Driver Health: Evaluates the health conditions for a driver, assigns the health state, and carries out any actions associated with the health state. This job is used in conjunction with driver health monitoring. For complete instructions about setting up driver health monitoring, including using the Driver Health job, see Identity Manager 3.6.1 Common Driver Administration Guide.
Password Expiration Notification: Searches an LDAP directory for objects whose passwords expire in a specified number of days. When an object that meets the criteria is discovered, the job sends an e-mail to the address contained in the object’s mail LDAP attribute.
Information about using the predefined jobs is provided in Section 2.0, Adding a Predefined Job and Section 3.0, Configuring a Predefined Job’s Properties.
You can also develop custom jobs to perform tasks. A custom job requires you to create a Job Definition and a Job Implementation. The Job Definition is XML code that defines the parameters for the job. The Job Implementation is a JAR file that contains the Java* classes that perform the task. The job can perform any task that you can implement through Java classes. Because the job is initiated through the Metadirectory engine, the job also has access to the Identity Vault data. For more information, see Section 4.0, Creating a Custom Job.