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 six 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 Monitoring Driver Health
in the Identity Manager 4.0.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.
Telemetry: Identity Manager Telemetry is a new job introduced with Identity Manager 4.0.1. The job functions as a usage counting tool or a license monitoring tool that provides value to the Identity Manager customers. You can add more licenses or retire unused licenses and leverage benefits such as inactive user pricing.
The Telemetry job collects details about the installed Identity Manager software and hardware, and usage of Identity Manager drivers in the customer environment. After the customer registers with the Novell Customer Center, the information is sent to Novell. This information allows Novell to support the customer better, develop and test Identity Manager more efficiently and effectively, and make important decisions in the future. Registering Identity Manager with Novell has many benefits to the customers. You can receive notifications about available updates and patches and find information about upgrades and special offers for other Novell products, and so on.
The Telemetry feature is invoked by using a telemetry agent, which is triggered through an Identity Manager DirXML job configured on the driver set. Similar to any other Identity Manager jobs, the Telemetry job is configured by using iManager. The Telemetry job can be run one or more times either manually or at scheduled times.
The Telemetry agent collects information into an XML file, which is sent to Novell over a secure HTTP connection. A telemetry file contains the following elements of information:
Information: Contains the customer ID, E-mail address, and the GUID. The GUID is the GUID of the eDirectory server object.
Hardware: Contains information about the memory, number of CPUs, and the hardware architecture of the server where Identity Manager is running.
Software: Contains the following product information:
ProductInfo: The Identity Manager version and the patch level.
UsageInfo: Contains the total count of the Active and Inactive User accounts of the drivers under the diver set that is being queried. Inactive user accounts are the user accounts which are disabled and who have not logged in for more than 120 days.
InstallationInfo: Contains activation information of each driver set .
Host: Contains host information such as the name of the host operating system, version, host type (physical or virtual), host name, and host IP.
Other Items: Contains usage information of each driver under a driver set. Other details such as driver name, driver ID, active and inactive usage count, and the driver set activation state are also added. For the User Application driver, information about the Workflow (Provisioning Request Definitions) objects created on the driver is also included.
Information about using the predefined jobs is provided in Section 2.0, Adding a Predefined Job and Section 3.0, Configuring the Properties of Predefined Jobs.
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.