Populating Data in the RECON_EXCEPTIONS Table

Managing Reconciliation Events 1-17 date is displayed, then continue to the next step. Otherwise, do not collect the exception data. b. While provisioning the resource object to the user, check if the resource object has already been deprovisioned in Oracle Identity Manager: If the resource object is already deprovisioned, then insert into RECON_EXCEPTIONS table the value RESOURCE_DEPROVISIONED in the REX_EXCEPTION column for the user who is to be provisioned. If the resource object is not deprovisioned, then insert into RECON_EXCEPTIONS table the value RESOURCE_NEVER_PROVISIONED in the REX_EXCEPTION column for the user who is to be provisioned. 1-18 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager 2 Managing Scheduled Tasks 2-1 2 Managing Scheduled Tasks In Oracle Identity Manager, it is often required to run jobs at specified times on a regular basis to manage various activities. Scheduler enables you to schedule jobs that automatically run predefined scheduled tasks at the specified time. This is illustrated by the following example: To meet the security policies of an organization, employees may be required to change their product application password every 60 days. For this purpose, the system administrator has to ensure that an email is sent to all employees whose passwords for the respective product applications have expired. One approach would be to identify the set of users whose passwords have expired and send email to each employee manually. Alternatively, the system administrator can use a service, such as scheduler. In Oracle Identity Manager, there is a predefined scheduled task called Password Warning Task. The system administrator can use this scheduled task to create a scheduled job with the intended schedule. Scheduler also enables you to create your own scheduled tasks that can be run by a job at a set time. A scheduled task configure the metadata for a job, which is to be run, and the parameters required for execution of that task. This metadata is predefined for the predefined tasks. A new task can be added by the user, which will have the new metadata or the existing tasks can be updated to addupdate the parameters for other configuration details. A job can be scheduled to run at the specified interval. You can create multiple jobs scheduled to run at different time intervals. A job run is a specific execution of a job. Each job run includes information such as the start time, stop time, exceptions and status of the execution. This chapter discusses the following topics: ■ Configuring the oim-config.xml File ■ Starting and Stopping the Scheduler ■ Scheduled Tasks ■ Jobs

2.1 Configuring the oim-config.xml File

After you install Oracle Identity Manager, you can configure the scheduler settings by editing the child elements of the Scheduler element in the oim-config.xml file located in the following location in Meta Data Store MDS: See Also: Table 2–2, Predefined Scheduled Tasks for information about the Password Warning Task scheduled task 2-2 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager dboim-config.xml Table 2–1 lists the default elements that you can configure within the Scheduler element in the oim-config.xml file. See Also: MDS Utilities and User Modifiable Metadata Files in the Oracle Fusion Middleware Developers Guide for Oracle Identity Manager for information about importing and exporting data to and from MDS Note: You can add new configurable child elements. For the information about new child elements, refer to the following URL: http:www.quartz-scheduler.org Table 2–1 Child Elements of the Scheduler Element Element Within Scheduler Element Description DSJndiURL This element is used for configuring transactional data source in the application server, which is used by Quartz to establish the connection. Default value: jdbcoperationsDB nonTxnDSJndiURL This element is used for configuring non-transactional data source in the application server, which is used by Quartz to establish the connection. Default value: jdbcoimJMSStoreDS Clustered Enter true if Oracle Identity Manager has been installed in a clustered environment. Otherwise, enter false. Default value: true NOTE: In a clustered environment, the clocks on all nodes of the cluster must be synchronized. implementationClass Enter the name of the Java class that implements scheduler. Default value: oracle.iam.scheduler.impl.quartz.QuartzSchedulerImpl instanceID Enter a unique string value in this element. This value represents a string that uniquely identifies an Oracle Identity Manager scheduler instance. NOTE: In a clustered environment, each node of the cluster must have a unique InstanceId. This can be achieved by entering a value of AUTO in the instanceId element. startOnDeploy Enter false if you do not want scheduler service to start automatically when Oracle Identity Manager is started. Otherwise, enter true. Default value: true threadPoolSize Enter an integer value in this element. This value represents the number of threads that must be used for running jobs. Default Value: 10