Overview of AsyncService Features of Offline Processing

16-4 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager

16.4.2 Viewing Failed Async Tasks

The System Administrator can view the details of each failed task, for instance the cause for the task to fail and the remedial action to be undertaken. The user can view the details of the failed tasks by either providing the filter criteria or by clicking the Search button.

16.4.2.1 To view failed async tasks

1. Log in to the Diagnostic Dashboard main page. See Starting the Diagnostic Dashboard UI on page 16-3 for more information. 2. Perform one of the following to view a list of failed tasks. ■ Click Search to view a list of all the failed tasks. ■ Search for the failed task based on the following filter criteria. – Task Name: Type the name of the failed task. – Category: Type the category of the failed task. – Between: Specify the date range. – Select the Exclude if retries are remaining option if you do not want to view the tasks for which automated retries are still pending. Click Search after providing the filter criteria. The list of failed async tasks are displayed, as shown in Figure 16–1 : Figure 16–1 Failed Async Tasks 3. Click the Identifier link to view detailed information about the failed task. In this scenario, click 222. The following information is displayed: ■ Task Name ■ Instance ID ■ Category ■ Last Execution Time ■ Cause ■ Action ■ Stack Trace Managing Asynchronous Execution 16-5

16.4.3 Retrying Failed Async Tasks

The System Administrator can retry a specific failed task directly from the Diagnostic Dashboard UI and then view the results of the retry.

16.4.3.1 To retry failed Async task

1. Search for the failed task that you want to retry. See To view failed async tasks on page 16-4 for more information.

2. Click the Retry link. The retry status for the task is displayed. The following

details are provided. ■ Retry Status ■ Task Summary ■ Stack Trace ■ Cause ■ Resolution

16.4.4 Resubmitting Failed Async Tasks

All the failed tasks are resubmitted to the Async queue. These are later executed asynchronously. To resubmit failed tasks, click ResubmitAll.

16.4.5 Purging Failed Async Tasks

There are situations when there are numerous failed Async tasks. The System Administrator might feel that there is no use retrying these tasks. In such a scenario, the failed tasks can be purged. The action purge removes all the failed Async tasks from the database. In other words, there no more tasks to retry.

16.4.5.1 To purge failed Async tasks

1. Search for the failed task that you want to retry. See

To view failed async tasks on page 16-4 for more information.

2. Click PurgeAll.

16-6 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager 17 Enabling Offline Provisioning 17-1 17 Enabling Offline Provisioning In online provisioning, multiple provisioning operations are performed in sequence. For example, if you create a request to allocate provision five resources to five OIM User, then the system: ■ Treats the provisioning of one resource to one user as a provisioning operation ■ Processes provisioning operations in sequence, one after the other This chapter contains the following sections: ■ Features of Offline Processing ■ Enabling and Disabling Offline Provisioning ■ Reports Related to Offline Provisioning ■ Configuring the Remove Failed Off-line Messages Scheduled Task

17.1 Features of Offline Processing

The following are features of offline provisioning: ■ The offline provisioning approach is applied only during Provision Create Target System Account Resource, Enable Resource, Disable Resource, and Revoke Resource operations. The offline provisioning approach is not applied in a provisioning operation that involves modification of an allocated provisioned resource. ■ Offline provisioning is not applied during organization provisioning. ■ You enable offline provisioning at the resource object level. The procedure is described later in this chapter. ■ JMS messages generated during offline provisioning are processed in parallel. Processing of each JMS message is treated as a single transaction, and it is asynchronous and independent of other JMS messages. This approach provides better performance over the online provisioning approach in which provisioning operations are processed in sequence. ■ When you view the resource details for a resource instance of an OIM User, you can view the Provisioning in Queue, Enable in Queue, Disable in Queue and Revoke in Queue statuses for Provision, Enable, Disable, and Revoke operations respectively if provisioning for a particular resource has not yet been processed. Note: You might not need to enable offlining in Oracle Identity Manager 11g architecture, depending on your work flow. This feature may be obsolete in future. 17-2 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager ■ The final status of the resource instance is the same as the status for online provisioning. For example, if a message for a resource is processed successfully, then the Provisioned status is displayed. The same status is displayed for online provisioning. ■ In offline provisioning, details of failed messages are stored in the Off-line Persistent Store OPS table. You can view these details by running the Off-line Resource Provisioning Messages report. See Reports Related to Offline Provisioning for information about this report.

17.2 Enabling and Disabling Offline Provisioning

As mentioned earlier, you enable offline provisioning at the resource object level. Off-line provisioning is applicable only when the Auto Save Form option is already selected in the Process Definition form. To enable offline provisioning: 1. Log in to Oracle Identity Manager Design Console.

2. Expand Resource Management, and double-click Resource Objects.

3. Search for and open the resource object for which you want to enable offline provisioning.

4. On the Resource Object form, select Off-line Provisioning. This enables off-line

provisioning for enable, disable, and revoke resource operations. When the Off-line Provisioning option is not selected, the specific resource provisioning, enable, disable, and revoke operations occur online. 5. Click the Save icon. To disable offline provisioning: 1. Log in to Oracle Identity Manager Design Console.

2. Expand Resource Management, and double-click Resource Objects.

3. Search for and open the resource object for which you want to enable offline provisioning.

4. On the Resource Object form, deselect the Off-line Provisioning check box.

5. Click the Save icon.

17.3 Reports Related to Offline Provisioning

When an online provision, enable, disable, or revoke operation fails, the error messages and other information about the operation are displayed on the UI. The Offline Resource Provisioning Messages report in Oracle BI Publisher stores all the error messages.

17.4 Configuring the Remove Failed Off-line Messages Scheduled Task

Configure the Remove Failed Off-line Messages scheduled task to schedule deletion of failed provisioning operations from the OPS table. While configuring this scheduled task, set a value for the Remove Failed Messages Older Than days attribute. See Chapter 2, Managing Scheduled Tasks for information about working with scheduled tasks. 18 Using Enterprise Manager for Managing Oracle Identity Manager Configuration 18-1 18 Using Enterprise Manager for Managing Oracle Identity Manager Configuration Oracle Identity Manager stores the configuration files in MDS. Most of the configurations are exposed as MBeans. Therefore, you can control the configuration values by using Enterprise Manager. In some instances, might have to export the complete files to file system, make the necessary changes, and then import the files back into the repository, as described in the following sections: ■ Using MBeans for Configuration Changes ■ Exporting and Importing Configuration Files

18.1 Using MBeans for Configuration Changes

To change configuration settings by using Mbeans: 1. When the administrative server and at least one Oracle Identity Manager managed server is running, login to Oracle Enterprise Manager Fusion Middleware Control by using the URL in the following format: http:ADMINSTRATION_SERVER:PORTem

2. Navigate to Identity and Access, oim. Right-click and navigate to System MBean

Browser .

3. Under Application Defined MBeans, navigate to oracle.iam, Application:oim,

XMLConfig , Config. All the configuration files are in this location.

18.2 Exporting and Importing Configuration Files

To export or import configuration files: 1. When the administrative server and at least one Oracle Identity Manager managed server is running, login to Oracle Enterprise Manager Fusion Middleware Control by using the URL in the following format: http:ADMINSTRATION_SERVER:PORTem See Also: MDS Utilities and User Modifiable Metadata Files in the Oracle Fusion Middleware Developers Guide for Oracle Identity Manager for information about the list of configuration files that can be exported and imported 18-2 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager

2. Navigate to Identity and Access, oim. Right-click and navigate to System MBean

Browser .

3. Under Application Defined MBeans, navigate to oracle.mds.lcm,

Server:oim_server1 , Application:oim, MDSAppRuntime. 4. To export the configuration files: a. Click the Operations tab, and then click exportMetaData. b. In the toLocation field, enter tmp or the name of another directory.

c. Select createSubDir as false.

d. In the docs field, enter the complete file location as the Element.

e. Also select false for excludeAllCust, excludeBaseDocs, and

excludeExtendedMetadata. Then, click Invoke. This exports the file specified in the docs field to the directory specified in the toLocation field. 5. To import the configuration files: a. Click importMetaData. b. In the fromLocation field, enter tmp or the name of the directory in which you have the configuration files.

c. Select createSubDir as false.

d. In the docs field, enter the complete file location as the Element. For example, dboim-config.xml.

e. Also select false for excludeAllCust, excludeBaseDocs, and

excludeExtendedMetadata. Then, click Invoke. This imports the file specified in the docs field to MDS in the toLocation field. 19 Setting the Language for Users 19-1 19 Setting the Language for Users In Oracle Identity Manager 11g Release 1 11.1.1, the language preference of the user for the UI is not set according to the locale specified by the user in the Preferences section of the Self Service. However, this locale preference is used to determine the language of notification messages. The logic to determine the UI locale gives precedence to other ways a locale can be specified, such as through Fusion Apps or Oracle Access Manager OAM login page, before using the browser locale. The oracle.fusion.appsMode system property is used internally and is automatically set when the environment is with fusion Apps. Based on this propertys value, the appropriate attribute within a cookie called ORA_FUSION_PREFS set and used internally, is used to determine the locale. To determine the UI locale for a user, the following logic is used internally: 1. Check if the oracle.fusion.appsMode system property is available. 2. If the oracle.fusion.appsMode system property is not available or the value is set to false, then preferredLanguage attribute is checked. The value of this attribute is the UI locale for the user. The preferredLanguage attribute is checked inside the ORA_FUSION_PREFS cookie. 3. If the oracle.fusion.appsMode system property is available and the value is set to true, then the locale attribute is checked inside the ORA_FUSION_PREFS cookie. The value of this attribute is the UI locale for the user. 4. If the ORA_FUSION_PREFS cookie is not present, then check the browser language setting. The UI locale for the user is same as the browser language setting. Note: The ORA_FUSION_PREFS cookie is internal to Oracle Identity Manager. Note: If none of the above can provide a locale value, then check the server setting.