Configuring the oim-config.xml File

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 Managing Scheduled Tasks 2-3

2.2 Starting and Stopping the Scheduler

The Scheduler Status page is an authenticated UI page that displays the current status of the scheduler. At any given instance, the scheduler can be in one of the following statuses: ■ Started If the scheduler is in the started status, then jobs can be scheduled and jobs that have already been scheduled will continue to run at the scheduled time. ■ Stopped If the scheduler is in the stopped status, then all jobs are stopped. When the scheduler gets the stopped status while jobs are running, the currently running jobs are stopped. In addition, the jobs that are scheduled to run does not run, but are submitted for run according to the schedule. When the Scheduler Service is up in the future, all submitted jobs are run. The Scheduler Status page also displays a detailed error message in the Last Error field, if any. You can use the Scheduler Status page to either start, stop, or reinitialize the scheduler. By default, the scheduler is in the started status after you install Oracle Identity Manager. However, if you want to stop scheduler for any reason and then restart it, then you must follow the procedure discussed in this section. To start or stop the scheduler: 1. Browse to the following URL by using a Web browser: http:OIM_HOST:OIM_PORTSchedulerService-webstatus In this URL, OIM_HOST represents the name of the computer hosting the Oracle WebLogic Application Server and OIM_PORT refers to the port on which the server is listening. The default port number for Oracle WebLogic Application Server is 7001.

2. Enter the User ID and password, and then click OK.

The Scheduler Status page is displayed. 3. Depending on the type of action that you want to perform, click one of the following: ■ START: Click this button to start the scheduler. ■ STOP: Click this button to stop the scheduler. This stops the scheduler and further execution of triggers, but it does not stop or abort any jobs that are Note: ■ You need to have Scheduler Admin role to start or stop the scheduler. ■ In a clustered environment, you must perform this procedure on each node of the cluster. Note: You may be automatically logged in to the scheduler service if you are working in a single sign-on environment. 2-4 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager already executing. When the Scheduler Service is started again, jobs will then be executed at their appropriate times based on when they are scheduled. ■ REINIT : Click this button to reinitialize the scheduler. Reinitializing the scheduler will restart the scheduler.

2.3 Scheduled Tasks

In Oracle Identity Manager, metadata is predefined for the default scheduled tasks. New tasks can be added by the user with new metadata, or the existing tasks can be updated to add or update the parameters or other configuration details. For example, you can configure a reconciliation run using a scheduled task that checks for new information on target systems periodically and replicates the same in Oracle Identity Manager. Each scheduled task contains the following metadata information: ■ Name of the scheduled task ■ Name of the Java class that runs the scheduled task ■ Description ■ Retry ■ Optional Parameters that the scheduled task accepts. Each parameter contains the following additional information: – Name – Data Type – Required Optional – Help Text – Encryption This section discusses the following topics: ■ Predefined Scheduled Tasks ■ LDAP Scheduled Tasks ■ Creating Custom Scheduled Tasks

2.3.1 Predefined Scheduled Tasks

This release of Oracle Identity Manager provides a set of predefined scheduled tasks that you can use while creating or working with jobs. Table 2–2 lists the predefined scheduled tasks.