Uninstalling a Connector Uninstalling Connectors and Removing Connector Objects

Managing Connector Lifecycle 6-69 See Running the Script to Uninstall Connectors and Connector Objects on page 6-69 for the procedure.

6.9.4.2 Removing Adapters, Lookup Definitions, Resource Objects, and Scheduled Tasks

You can use the ConnectorUninstall script to remove an adapter, lookup definition, resource object, or scheduled task. Only the object that you specify is removed from Oracle Identity Manager.

6.9.4.3 Running the Script to Uninstall Connectors and Connector Objects

Running the script to uninstall connectors and connector objects includes the following procedures: ■ Preuninstall ■ Uninstall ■ Postuninstall

6.9.4.3.1 Preuninstall

Before Uninstalling the connector, you must: 1. Take Oracle Identity Manager Database backup so that if something goes wrong during uninstalling, then the data can be restored. See Oracle Identity Manager Database documentation for details about taking backup. Warning: ■ Connector uninstall collects all the objects information from the connector XML, which is created while installing or defining a connector. If an additional object, which is not related to this connector is added while defining the connector, uninstall would delete that too. For example, while defining AD connector, if user adds a system lookup or lookup related to other connector, uninstall would delete that lookup. ■ Ensure that only the connector specific objects are added while defining a connector. Caution: It is strongly recommended that Oracle Identity Manager is idle and it is not available for any operations. You must ensure that: ■ there are no operations on Oracle Identity Manager while using uninstalling connector or connector objects ■ all scheduled tasks are disabled and there are no asynchronous messages pending for processing such as audit messages, offline provisioning messages, offline task messages, requests scheduled for future and so on. Note: Before executing the uninstall, you must ensure that all scheduled tasks are disabled. 6-70 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager 2. Create Oracle Identity Manager metadata MDS backup. See MDS Utilities and User Modifiable Metadata Files in the Oracle Fusion Middleware Developers Guide for Oracle Identity Manager for information about the utilities that you can use to modify Oracle Identity Manager metadata. 3. Ensure that there are no operations on Oracle Identity Manager until the Uninstall utility is completed. Oracle Identity Manager and SOA servers should be up and running. 4. Ensure that all the JMS messages are processed.

6.9.4.3.2 Uninstall To run the ConnectorUninstall script for uninstalling the

connector: 1. Set values in the properties file used by the script. The ConnectorUninstall.properties file is a viable in OIM_HOMEserverbin. This file contains information that is used by the script for deleting connector objects. Open the properties file in a text editor, and then set values for the following properties: ■ DatabaseURL: Enter the JDBC URL for the Oracle Identity Manager database in the following format: jdbc:oracle:thin:HOST_NAME:DATABASE_PORT:DATABASE_NAMEORACLE_SID For example: jdbc:oracle:thin:localhost:1521:orcl ■ DBUserName: Enter the user name of an Oracle Identity Manager database. ■ DBType: Specifies the type of database. ■ LogLevel: Enter one of the following as the log level: DEBUG, WARN, INFO, or ERROR. ■ Location: Enter the directory location where you want to have all the log files generated by the Uninstall utility. If the Uninstall utility completes successfully, then the ConnectorUninstall.log file, along with ResourceObject.log files are generated. If the Uninstall utility fails, then the ConnectorUninstall.log file along with the ConnectorUninstall_Error.log file are generated. For example, if the Uninstall utility of ActiveDirectory Connector succeeds, then the following logs will be generated: – ConnectorUninstall.log – AD User.log Note: If you provide ConnectorName and Release along with ObjectType and ObjectValues, then deletion of ObjectValues will be performed by the utility and the Connector information will be skipped. Note: If the uninstall utility fails with errors, then check the ConnectorUninstall.log and ConnectorUninstall_Error.log and take suitable action. Then, run the uninstall utility again.