3 Deploying Connectors

This chapter provides generic information about the procedure to deploy a connector. For detailed information about the procedure to deploy a target-specific connector, refer to the deployment guide for that connector. The "Related Documents" section of the preface contains a list of all the deployment guides.

Note:

It is recommended that you customize and test connectors before you move them to your production environment.

This chapter discusses the following sections:

• Overview of Connector Deployment

• General Considerations

Overview of Connector Deployment

The following are the high-level steps involved in deploying a connector:

1. Import the relevant XML file into the Oracle Identity Manager environment. There may be more than one XML file associated with the connector for your target application.

   When you import the connector XML file, create at least one IT resource definition. This definition is used by Oracle Identity Manager to connect to the actual computer on which the target application is hosted. This definition is required for the provisioning process and the associated adapters to run successfully.

2. Determine whether you want to deploy Oracle Identity Manager as a provisioning, reconciliation, or provisioning and reconciliation solution. The procedure that you must follow depends on the type of solution you select.

   See Also:

   "Deployment Configurations of Oracle Identity Manager" for information about the various configurations in which Oracle Identity Manager can be deployed

3. Compile the adapters that are predefined with the connector XML file.

General Considerations

The following are general considerations that you must address:

• Some connectors require external libraries in the form of JAR files for normal functioning. You may need to purchase these JAR files from the respective vendors.

  After you obtain these JAR files, you must configure Oracle Identity Manager as required. For example, you may need to update the CLASSPATH environment variable.

• Some connectors require external software to be installed on the target system. For example, if you are using the Bourne (sh) shell on Solaris, then you must install and start WBEM Services on the target Solaris computer. Otherwise, you cannot use Oracle Identity Manager to provision users on Solaris.

• To make most prepackaged connectors function as required, you must configure the target systems separately. Where required, this step is explained in the connector deployment guides.

• While installing Oracle Identity Manager in a clustered environment, you copy the contents of the installation directory to each node of the cluster. Similarly, all the JAR files that you copy to the Oracle Identity Manager server during the connector deployment process must be copied to the corresponding directories on each node of the cluster. You must also copy the adapters, which you recompile while deploying the connector, to the corresponding directory on each node.