Procedure to Upgrade a Non-Converged Connector to a Converged Connector

Managing Connector Lifecycle 6-65 4. Explode the connector bundle with naming convention org.identityconnectors. in some temporary folder. Make a folder named lib in the same temporary folder and copy all the third party libraries to that folder. 5. Retain MANIFEST.MF from the above exploded bundle. 6. Repackage the connector with the same name and with the same MANIFEST.MF that was being retained. Now, the repackaged connector bundle will also be having third party libraries. 7. Upload the repackaged connector in Oracle Identity Manager database with jar type as ICFBundle. 8. Delete the temporary folder created in Step 4. 9. Upgrade the connector by following the upgrade process 10. Purge cache or restart the server.

6.9 Uninstalling Connectors

Connector uninstall utility deletes the data related to the connector chosen for uninstall from Oracle Identity Manager Database. It deletes all the account related data associated with resource objects of the connector. This utility does not delete: ■ The actual user account from the target system ■ Identities from Oracle Identity Manager although the users are brought from trusted source to Oracle Identity Manager through trusted reconciliation ■ Audit data ■ Archival data Connector uninstall utility does not validate and notify the user if there is any object dependency present. For example, while uninstalling a Microsoft Active Directory AD connector, it does not validate if a dependent connector, such as Microsoft Exchange connector, already exists or not. Before uninstalling a connector, you must check if there are any other connectors dependent on the connector. If there are any, then the connector must not be uninstalled because this will affect the functionality of the dependent connectors. You must uninstall all the dependent connectors before uninstalling the base connector. This section discusses the following topics: ■ Use Cases Supported by the Uninstall Connectors Utility ■ Overview of the Connector Uninstall Process ■ Setting Up the Uninstall Connector Utility ■ Uninstalling Connectors and Removing Connector Objects WARNING: Do not use this utility in production. This utility deletes data from the Oracle Identity Manager database directly and is meant to be used in developmentstaging environments. 6-66 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager

6.9.1 Use Cases Supported by the Uninstall Connectors Utility

The following use cases are supported by the Uninstall Connectors utility: ■ A target system that has been decommissioned, and you want to uninstall the connector that was used to link that target system with Oracle Identity Manager. ■ Instead of directly upgrading to the latest release of a connector, you want to uninstall the earlier release and then perform a fresh installation of the latest release. ■ You want to remove an individual connector object from the Oracle Identity Manager database. For example, you had created a resource object in Oracle Identity Manager to represent the Intern user type defined in your target system. This user type has been removed from the target system, and you now want to remove the resource object from Oracle Identity Manager. The Uninstall Connectors utility supports independent deletion of following connector artifacts: – Adapters – Lookup definitions – Resource objects – Scheduled tasks

6.9.2 Overview of the Connector Uninstall Process

When you run the Uninstall Connectors utility, the utility performs the following steps before deleting the resource objects of the connector: 1. Checks if there are any access policies associated with the resource objects of the connector. If there are any access policies present, then the utility displays the list of access policies associated with the resource object and prompts you to modify the access policy and terminates with no data deletion. The access policy should be modified to remove the resource object from it. If the access policy is associated with only one resource object, then you need to create a dummy resource object, assign it to the access policy and then proceed with the removal of resource object from the access policy. 2. Closes all requests associated with the resource objects. 3. Displays list of request templates that are used while creating requests that are associated with the resource objects. The request templates are generic in nature, therefore the utility does not delete request templates. It prompts a message recommending you to deletemodify these templates as the resource objects would be deleted from Oracle Identity Manager. If the request template is associated with the resource object, then the request template needs to be modified to remove the resource name. If the request template is created for this resource object only, then you can delete the request template. 4. Displays the list of attestation processes which are associated with the resource objects. Attestation processes are generic in nature, therefore the utility does not delete attestation processes from Oracle Identity Manager. It prompts you to modify these processes as the resource objects would be deleted from Oracle Identity Manager. 5. Deletes only the operational level approval policies, which are associated with the resource object. The utility does not delete or modify request level approval