Upgrade Use Cases Supported by the Connector Upgrade Feature

6-36 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager Use Case 1: Custom-Developed Source Connector A custom-developed source connector must meet the following requirements so that it is compatible with the Upgrade Connectors feature: ■ The connector must be defined in Oracle Identity Manager. See Defining Connectors on page 6-11 if you want to manually define the connector. ■ The connector must have a configuration XML file. See the connector guide for information about configuration XML files. The following are sample events that can take place before you upgrade a custom-developed source connector: ■ You develop the connector and its configuration XML file. ■ Create a deployment package that is compatible with the Connector Installation feature. When you use this feature to deploy the connector on the production server, the connector is automatically defined at the end of the installation process. ■ You use the connector for reconciliation and provisioning. Target system resources are allocated through reconciliation and provisioning for OIM Users. ■ You modify the connector on the staging server, redefine it, and then regenerate the connector XML file. Use Case 2: Oracle-released connector that is not supported by the Install Connectors feature A connector that is not supported by the Install Connectors feature connector must meet the following requirements so that it is compatible with the Upgrade Connectors feature: ■ The connector must be defined in Oracle Identity Manager. See Defining Connectors on page 6-11 if you want to manually define the connector. ■ The connector must have a configuration XML file. See the connector guide for information about configuration XML files. Sample events and the upgrade procedure for this use case are the same as those for Use Case 1. Use Case 3: Oracle-released connector that is installed using the Install Connectors feature A connector that is installed using the Install Connectors feature meets the requirements specified for Use Cases 1 and 2. Note: ■ Connector lifecycle management does not support the upgrade of a trusted connector if the source connector uses the Xellerate User resource object for trusted source configuration. Therefore, you must manually upgrade the connector. Contact Oracle Support for more information. ■ Connector lifecycle management does not support the upgrade of a connector from the target mode source version to the trusted mode target version. Similarly, upgrading from trusted mode to the target mode is also not supported. Managing Connector Lifecycle 6-37 Use Case 4: Oracle-released connector that has been installed and then customized A connector that is supported by the Install Connectors feature meets the requirements specified for Use Cases 1 and 2. However, customizations are overwritten during the upgrade process. For example, if you have added an attribute in a scheduled task and also modified the JAR file for reconciliation, then this customization would be lost after the upgrade. To work around this issue: 1. Keep a record of customizations that you implement on a connector. 2. After you upgrade the connector, reapply the customizations. Use Case 5: Cloned connector A connector that is installed using the Clone Connectors feature meets the requirements specified for Use Cases 1 and 2. After the upgrade operation, you can use each clone to manage resource data that was collected through the clone before the upgrade.

6.8.2 Connector Object Changes Supported by the Upgrade Connectors Feature

Before you upgrade a connector, you might have reconfigured or customized the connector by making changes in individual connector objects. The upgrade process itself changes individual connector objects. The following sections list connector object changes supported by the Upgrade Connectors feature. These changes may have been performed manually that is, at any time before the Upgrade Connectors feature is used or may be performed by the Upgrade Connectors feature itself. ■ Resource Object Changes ■ Process Definition Changes ■ Connector Code Files Changes ■ Process Form Changes ■ Lookup Definition Changes ■ Adapter Changes ■ Rule Changes ■ IT Resource Type Changes ■ IT Resource Changes ■ Scheduled Task Changes

6.8.2.1 Resource Object Changes

The Upgrade Connectors feature can run on a resource object 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 resource object. ■ Status definitions can be added or deleted. ■ Administrators can be assigned or deleted. ■ Password policies can be added or deleted. ■ User-defined fields UDFs can be added or deleted. ■ Dependencies with other resource objects can be assigned or deleted. 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: