Resource Object Changes Connector Object Changes Supported by the Upgrade Connectors Feature

6-38 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager ■ Object authorizers can be assigned or deleted. In addition, the priority number assigned to the authorizers can be modified. ■ Process determination rules can be assigned or deleted. ■ Event-handler adapters can be assigned or deleted. ■ Resource object fields that are not present in the connector XML of the target connector are marked as obsolete. ■ Customizations performed on the resource object are not retained. After the upgrade, the new name of the resource object is the one specified in the connector XML of the target connector.

6.8.2.2 Process Definition Changes

The Upgrade Connectors feature can run on a process definition 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 a process definition. ■ The existing process definition can be replaced by a new process definition. ■ The existing provisioning definition can be renamed. ■ Existing reconciliation field mappings can be retained without change or modified. ■ New process tasks can be added. ■ Custom process tasks can be retained without a change. ■ Default process tasks can be retained, but you need to confirm that there are no changes in the default process task in the new version. Refer to the connector guide for more information. ■ Any combination of the following changes can be made to an existing process task: – The name and properties of the task can be modified. – An attached event handler-adapter can be modified. – Preceding and dependent tasks can be added, modified, or deleted. – New response codes can be added. – Existing response codes can be modified or deleted. – New tasks can be generated. – Undo tasks and recovery tasks can be modified. – Task-to-object status mapping can be modified. – Assignment rules can be modified. ■ Existing process tasks can be deleted. After the upgrade, the new name of the process definition is the one specified in the connector XML of the target connector.

6.8.2.3 Connector Code Files Changes

During an upgrade operation, you need copy connector code files, which include JAR files and scripts to the specified directories. To do so: Managing Connector Lifecycle 6-39 1. Manually upload all the connector specific jars excluding common library files Common.jar, FAMILYCommon.jar, and icf-Common.jar present in the lib folder of the connector distribution bundle using UpdateJars utility available under OIM_HOMEserverbin to Oracle Identity Manager database. 2. Download common library Common.jar, FAMILYCommon.jar and icf-Common.jar from Oracle Identity Manager database using DownloadJar utility available under OIM_HOMEserverbin. 3. Extract MANIFEST.MF from the downloaded libraries. Compare this version of MANIFEST.MF with the version in MANIFEST.MF of the common libraries that is available as part of converged distribution bundle. If the distributed library version is higher than the one downloaded from Oracle Identity Manager database, then use the UploadJar utility available under OIM_HOMEserverbin to upload the common libraries to Oracle Identity Manager database.

6.8.2.4 Resource Object Changes

To update the resource bundles:

1. If there are any customization on the resource bundles such as adding new entries

to the connector resource bundles, the changes need to be applied on the resource bundles present in the resources folder of the connector distribution bundle. The existing resource bundles present in Oracle Identity Manager database can be downloaded using the DownloadResourceBundles utility available under OIM_HOMEserverbin.

2. Use DownloadResourceBundles utility available under OIM_HOMEserverbin

to delete all the resource bundles specific to the connector from Oracle Identity Manager database.

3. Use UploadResourceBundles utility available under OIM_HOMEserverbin to

upload all the resource bundles specific to the connector to Oracle Identity Manager database.

6.8.2.5 Process Form Changes

The Upgrade Connectors feature can run on a process form on which any combination of the following changes have been performed. In addition, an upgrade operation might involve any combination of the following changes to a process form. ■ Columns can be added, modified, or deleted. ■ Child forms can be added, modified, or deleted. ■ Pre-populate adapters can be added. ■ The name, mappings, order, and rule of existing pre-populate adapters can be modified. ■ The user can manually add the customizations to the active version if they wish to add certain fields to the new version that were present in the existing form. Note: ■ An upgrade operation works on only the active version of the process form. No changes are made to earlier versions. ■ The existing process form cannot be renamed.