Note:The predefined connectors are distributed in the Oracle Identity Manager Connector Pack, independent from the Oracle Identity Manager core server release.
See the Oracle Identity Manager Connector Pack documentation to determine whether or not you can install the required release of the connector by using the Install Connector feature of Oracle Identity Manager Administration.
This chapter is divided into the following sections:
Verify the installation requirements.
Configure the target system.
Copy the external code files to a directory on the Oracle Identity Manager server.
Configure the Oracle Identity Manager server.
Import the connector XML files.
Configure Secure Sockets Layer (SSL).
Of these tasks, the Oracle Identity Manager Administration can be used to perform the following:
Copying the connector files and external code files to directories on the Oracle Identity Manager server
Importing the connector XML files
Compiling adapters (which is part of the procedure to configure provisioning)
Note:You must manually perform the remaining tasks. For instructions on performing these tasks, see the connector-specific documentation in the Oracle Identity Manager Connector Pack documentation library.
Log in to the Administrative and User Console.
Go to Advanced Administration.
In the Welcome page, under Deployment Manager, click Install Connector.
From the Connector List list, select the connector that you want to install. This list displays the names and release numbers of connectors whose installation files you copy into the default connector installation directory:
If you have copied the installation files into a different directory, then:
In the Alternative Directory field, enter the full path and name of that directory.
To repopulate the list of connectors in the Connector List list, click Refresh.
From the Connector List list, select the connector that you want to install.
Information about the following 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 install 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.
You must ensure that the correct versions of dependency connectors are installed before you proceed with the connector installation.
To start the installation process, click Continue.
The following tasks are performed in sequence:
Configuration of connector libraries
Import of the connector XML files (by using the Deployment Manager)
Compilation of adapters
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:
Retry the installation by clicking Retry.
Cancel the installation and begin again from Step 1.
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 any 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.
Some connectors have user-defined fields (UDF) that need additional configuration so that they can be searched on. The Active Directory connector field USR_UDF_OBGUID is an example of this type of field. To make a UDF searchable
Go to the User Attributes page, select the UDF attribute, and set the Searchable property to true. See "Modifying Entity Attributes" for information about editing the attributes specific to user entity.
Create an authorization policy to allow searching on the UDF. The policy should set Search User and View User Details permissions. See "Creating Custom Authorization Policies" in the Oracle Fusion Middleware User's Guide for Oracle Identity Manager for information about creating authorization policies.
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:
Ensuring that the prerequisites for using the connector are addressed
Note:At this stage, run the PurgeCache utility to load the server cache with content from the connector resource bundle in order to view the list of prerequisites. See "Purging the Cache" for information about running the
There are no prerequisites for some predefined connectors.
Creating an IT resource for the connector
The IT resource type is displayed. You must create an IT resource of the specified type.
See Also:"Creating IT Resources" for information about how to create IT resources in the Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager
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.
See Also:Chapter 2, "Managing Scheduled Tasks" for information about configuring scheduled tasks
Note:You can also access links to the Oracle Identity Manager Administrative and User Console pages for creating the IT resource and configuring the scheduled tasks by expanding the Resource Management menu on the left navigation pane of the console.
You can create a custom connector to link Oracle Identity Manager and a target system that has no predefined connector by using Generic Technology Connector (GTC). For detailed information about GTC, see Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager.