IT Resource Type Changes

Managing Connector Lifecycle 6-41 operation might involve any combination of the following changes to an IT resource type. ■ The existing IT resource type can be replaced by a new IT resource type. ■ In an existing IT resource type, new parameters can be added and existing parameters can have their default values and types modified or deleted. ■ All custom parameters are displayed while mapping IT Resource Type definitions. You can retain the custom parameters.

6.8.2.10 IT Resource Changes

The Upgrade Connectors feature can run on an IT resource on which any combination of the following changes have been made. In addition, an upgrade operation might involve any combination of the following changes to an IT resource. ■ The parameter retained for IT Resource Type definition will be available for all the IT Resource instances of this type. If an existing parameter in IT Resource Type definition is not retained, then this parameter will not available in all the IT Resource instances of this type. ■ In an existing IT resource, new parameters can be added and existing parameters can have their default values and types modified or deleted. After the upgrade, the new name of the IT Resource Type definition is the one specified in the connector XML of the target connector.

6.8.2.11 Scheduled Task Changes

The Upgrade Connectors feature can run on a scheduled task that has been retained or existing scheduled tasks have been replaced by new scheduled tasks.

6.8.3 What Happens When You Upgrade a Connector

See Upgrade Use Cases Supported by the Connector Upgrade Feature for information about the changes that can be put into effect when you upgrade a connector. In addition, the following events are part of the outcome of an upgrade operation: ■ While performing the upgrade procedure, you are prompted to map new connector objects with existing objects. For example, you are prompted to map each resource object in the target connector with a resource object in the source connector. If the object names are same in both source and target, then for the new object, the corresponding old object need to be mapped. If there are changes in the object names in source and target, then you need to map the object properly by referring the source and target connector release documents. It is your responsibility map the source and target objects properly. If the objects are not mapped properly, then the source object will be corrupted by the upgrade process. Therefore, it is mandatory that you must know about all the source and the target connector objects.

6.8.4 Summary of the Upgrade Procedure

The following is a summary of the procedure to upgrade a connector: 6-42 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager 1. Read through the upgrade procedure. This will let you make an estimate of the time for which the connector and, therefore, the target system might be unavailable to Oracle Identity Manager users. You can also determine if you have the Oracle Identity Manager expertise required to complete all the upgrade and post-upgrade steps. 2. Make a note of associations between objects of the source connector and other Oracle Identity Manager objects. For example, make a note of associations between resource objects and access policies. 3. If required, create the connector XML file for a clone of the source connector. If the object names in the target connector are different from object names in the source connector, then it is recommended that you first create the connector XML file for the clone connector. Step 1: Create the connector XML file for the cloned connector on page 6-22 describes the procedure. While performing the procedure, specify object names that are the same as object names in the target connector. This will help avoid the need for renaming connector objects after you upgrade the connector. 4. Upgrading the source connector to target connector on staging server. The XML file contains details of changes to be made to the connector objects of the source connector so that they are converted into the connector objects of the target connector. These changes are applied automatically during the upgrade process. To upgrade the source connector: a. Back up the Oracle Identity Manager database on the production server. b. Perform the steps described in Preupgrade Procedure on page 6-43 c. Perform the steps described in Silent Mode Upgrade in Staging and Production Environment on page 6-55 The resulting transformed XML can be generated and used in production server. 5. Use the silent delta XML for connector upgrade. To use the delta XML file: a. Restore the production database on the staging server. b. Perform the steps described in Preupgrade Procedure on page 6-43 c. Perform the steps described in Silent Mode Upgrade in Staging and Production Environment on page 6-55 d. Perform the steps described in Postupgrade Procedure on page 6-58 6. Verify that the source connector on the production server is the same as the source connector on the staging server. If there are differences in the source connector on the staging server and the production server, then the delta XML file is not correctly imported on the production server. 7. Import the delta XML file on the production server. Note: The procedure explained in this chapter is based on the best practice in which you first perform the upgrade in a test development environment. All functional use cases need to be tested before applying the upgrade in production server. Wizard mode upgrade should not be used in production, only silent mode need to be used in production server.