Application Programming Interface Upgrade Overview

13-10 Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management 2. Run generatePendingTransactionReport.bat Located at MW_ HOME\Oracle_IDM1\server\bin for Windows or generatePendingTransactionReport.sh Located at MW_HOMEOracle_ IDM1serverbin for UNIX and provide the following details: ■ jdbc url [hostname:portname:sid] ■ Oracle Identity Manager schema username ■ Oracle Identity Manager schema password ■ Directory where you save the reports. The pending transaction report utility generates a report which includes the following details: ■ Pending Recon: This includes all events that are deferred to a later date. ■ Pending Request: This includes all requests including self registration pending approval. ■ JMS Queues: This includes all messages, which are in unprocessed state. A JMS message is submitted in case of off-line provisioning. So this report will provide details of the entire pending provisioning task including task, which are initiated in offline mode. The following are the pending transactions which can exist in your environment: ■ All pending recon events generated in OIM 9.1 must be processed. Failed events will not be upgraded, if left unaddressed. ■ All pending approval tasks generated in Oracle Identity Manager 9.1 must be processed. Pending approval tasks will not be upgraded, if left unaddressed. Ensure that these reach a final state before the Upgrade. ■ Scheduled task execution history in Oracle Identity Manager 9.1 will not be upgraded. Ensure that you finish all pending scheduled tasks and there is no scheduled task running during the upgrade period. ■ Any asynchronous audit processing must be processed in Oracle Identity Manager 9.1 before upgrading to Oracle Identity Manager 11g. ■ All JMS queues should be empty. JMS messages in regular or error queues will not be migrated in Oracle Identity Manager 11g. Wait for all JMS messages to be consumed, take proper manual actions for JMS error messages and clean all JMS tables before upgrading to Oracle Identity Manager 11g. For more information, see Emptying JMS queues . JAVA_HOME Specify the path of the Java home. The following example shows the full path: MW_HOMEjdk160_24 XEL_HOME Specify the path of the Oracle Identity Manager server home. The following example shows the full path: oracleMiddlewareOracle_IDM1server Table 13–6 Cont. Environment Variables Environment Variable Values Upgrading Oracle Identity Manager Environment 13-11

13.2.3 Running OSI Data Upgrade Utility

You must run the OSI Data Upgrade utility for Oracle Identity Manager 9.1 before you start the upgrade process. To do so, refer to the note 1303215.1 at https:support.oracle.com .

13.2.4 Running Schedule Task to Process the Audit Messages

Oracle recommends you to run the Issue Audit Messages Task schedule task to process pending audit messages for Oracle Identity Manager 9.1.

13.2.5 Emptying JMS queues

You must empty the JMS queues to ensure that the JMS messages are processed before you start the upgrade. To do so, complete the following:

1. Disable access by end-users, SPML, or API clients to Oracle Identity Manager. The

steps to do this will depend on your existing environment. For example, you can modify the firewall configuration to deny end-users access to Oracle Identity Manager or if you have fronted the Oracle Identity Manager application server with a Oracle HTTP server then you can shutdown the Oracle HTTP server but ensure that the application server is up and running. Any SPML or API clients For example, Active Directory Password Synch or any custom clients can be shutdown.

2. Disable all scheduled tasks using the Design Console. For more information, see

Oracle Identity Manager Design Console Guide.

3. Monitor the JMS queues and allow Oracle Identity Management to run for some

time, until all JMS queues except error queues e.g. xlErrorQueue, are empty.

4. Stop the Oracle Identity Manager 9.1. Depending on the application server you

use, see the Oracle Identity Management Release 9.1.0.1 documentation library for more information.

13.2.6 Circular Dependencies for Approval Workflow

Oracle Identity Manager 11g does not support circular dependencies for approval workflow where a approval task you create for example task1 response to another approval task for example task2, and task2 response is set to task1. Before you start the upgrade process, you must remove task2 from the response generated tasks in task1 using the Design Console. For more information, see Oracle Identity Manager Design Console Guide. Notes: ■ Ensure that you back up your existing Oracle Identity Manager database as described in Section 13.2.1, Backing Up the Oracle Identity Manager 9.1 Database . ■ OSI Data Upgrade utility is available with the Oracle Identity Manager 9.1.0.2 Bundle Patch 15. See: For more information, see the Oracle Identity Management Release 9.1.0.1 documentation library at: http:download.oracle.comdocscdE14049_ 01index.htm