From the Connector List list, select the connector that you want to install.

Managing Connector Lifecycle 6-9 The following information is displayed: ■ Connector installation history The connector installation history is information about previously installed releases of the same connector. ■ Connector dependency details There are some connectors that require the installation of some other connectors before you can start using them. For example, before you use the Novell GroupWise connector, you must install the Novell eDirectory connector. Novell eDirectory is called the dependency connector for Novell GroupWise. The connector dependency details include the list of connectors that must be installed before you can install and use the selected connector. These details also include information about any dependency connectors that are already installed, and whether or not any of the installed dependency connectors must be upgraded. However, after showing the dependency information, the Install Connector wizard allows you to install the connector. You must ensure that the correct versions of dependency connectors are installed after you complete the current installation. Figure 6–4 shows the page with connector history details and connector dependency details: Figure 6–4 Connector History and Dependency

6. To start the installation process, click Continue.

The following tasks are performed in sequence: a. Configuration of connector libraries b. Import of the connector XML files by using the Deployment Manager c. Compilation of adapters Figure 6–5 shows the Connector Installation page of the Install Connector wizard: 6-10 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager Figure 6–5 The Connector Installation Page On successful completion of a task, a check mark is displayed for the task. If a task fails, then an X mark and a message stating the reason for failure are displayed. Depending on the reason for the failure, make the required correction and then perform one of the following steps: ■ Fix the cause of the error, and then retry installation by clicking Retry. ■ Cancel the installation and begin again from step 1 of the installation procedure. One of the reasons for installation failure could be a mismatch between information about files and directory paths in the configuration XML file and the actual files and directory paths. If this happens, then an error message is displayed. For example, suppose the actual name of the JAR file for reconciliation is recon.jar. If the name is provided as recon1.jar in the configuration XML file, then an error message is displayed. If such an error message is displayed, then perform one of the following steps: ■ Make the change in the configuration XML file, and then retry installation from the Step 1: Select Connector to Install page onward. In the example described earlier, change the name of the JAR file to recon.jar in the configuration XML file, and then retry installation from the Step 1: Select Connector to Install page onward. ■ Make the change in the actual name or path of the file or directory, and then use the Retry option. In the example described earlier, change the name of the JAR file to recon1.jar and then click the Retry button.

7. If all three tasks of the connector installation process are successful, then a

message indicating successful installation is displayed. In addition, a list of the steps that you must perform after the installation is displayed. These steps are as follows:

a. Ensuring that the prerequisites for using the connector are addressed

Managing Connector Lifecycle 6-11 b. Creating an IT resource for the connector The IT resource type is displayed. You must create an IT resource of the specified type. To do this, go to Advanced Administration, Configuration, Resource Management, Create IT Resource . See the Creating IT Resources section in the connector guide for more information. c. Configuring the scheduled tasks that are created when you installed the connector. The names of the scheduled tasks that are created during the XML file import process are displayed. You must configure these scheduled tasks. To do this, go to Advanced Administration, System Management, Scheduler. Alternatively, in the System Management page, you can search Scheduled Jobs. See the Managing Scheduled Tasks section in the connector guide for more information.

6.5 Defining Connectors

Connector LCM operations such as Upgrade, Clone, and Uninstall needs a source for each connector where all the connector objects reside. The Connector Install stores the Deployment Manager DM XML in Oracle Identity Manager database. Typically, you will install the shipped connector and then perform one or both of the following operations: ■ Customize the connector by, for example, add modify existing object definitions, add additional adapters ■ Re Configure the connector by, for example, changing attribute names and key fields The DM XML in Oracle Identity Manager database, which will be the reference for all Connector LCM operations need to be updated for customization changes. Oracle Identity Manager provides Define feature to update the DM XML stored in Oracle Identity Manager database with customization changes. Define feature is similar to Export where user need to add all the connector objects related to a specific connector. The end result of defining a connector is an XML file, which will be updated in Oracle Identity Manager database. At this point, the customized or re-configured connector is not the same as the Oracle-released connector. The connector XML file for the Oracle-released connector might not be valid for the customized or re-configured connector. In the Advanced Administration page of the Oracle Identity Manager Administrative and User Console, you can define a customized or re-configured connector. Defining a connector is equivalent to registering the connector with Oracle Identity Manager. Note: There are no prerequisites for some connectors.