Configuring Provisioning On the last page, click Close.

Creating and Managing Generic Technology Connectors 21-37

21.3.2 Exporting Generic Technology Connectors

You can export the XML file of a generic technology connector. This XML file contains definitions for all the objects that are part of the connector. If you want to use the same generic technology connector on a new Oracle Identity Manager installation, you must first export the XML file and import it into the new Oracle Identity Manager installation. To export the connector XML file: 1. In the Oracle Identity Manager Advanced Administration, under System Management, click Export Deployment Manager File.

2. On the first page of the Deployment Manager Wizard, select Generic Connector

from the list and click Search. 3. In the search results, select the generic technology connector whose XML file you want to export.

4. Click Select Children.

5. For the selected generic technology connector, select the child entities that you want to export and click Select Dependencies.

6. Select the dependencies that you want to export, and click Confirmation.

7. After you verify that the elements displayed on the page cover your export requirements, click Add for Export.

8. Click Exit wizard and show full selection, and click OK.

21.3.3 Importing Generic Technology Connectors

To copy a generic technology connector to a different Oracle Identity Manager installation: 1. If the connector uses custom providers, you must copy the files created during provider creation to the appropriate directories on the destination Oracle Identity Manager installation. Note: The only difference between this procedure and the procedure that you follow to create the generic technology connector procedure is that automatic metadata detection does not take place when you modify an existing generic technology connector. Caution: If you modify attributes of fields of the OIM - Account data set or its child data sets, corresponding changes are not made in the Oracle Identity Manager database entries for these data sets. At the same time, no error message is displayed. Therefore, for this release of Oracle Identity Manager, Oracle recommends that you do not modify the fields or child data sets of the OIM - Account data set. This point has also been discussed in Section 22.2.2, Step 3: Modify Connector Configuration Page . 21-38 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager 2. Export the connector XML file on the source Oracle Identity Manager installation. 3. Import the connector XML file on the destination Oracle Identity Manager installation. To import the connector XML file: 1. In the Oracle Identity Manager Advanced Administration, under System Management, click Import Deployment Management File. A dialog box for locating files is displayed. 2. Locate and open the connector XML file from the directory into which you copy it.

3. Click Add File.

4. Click Next, Next, and Skip.

5. Click View Selections.

The contents of the connector XML file are displayed on the Import page. You may see a cross-shaped icon along with some nodes. These nodes represent Oracle Identity Manager entities that are redundant. Before you import the connector XML file, you must remove these entities by right-clicking each node and selecting Remove .

6. Click Import. The connector file is imported into Oracle Identity Manager.

See Also: Chapter 20, Creating Custom Providers for Generic Technology Connectors for more information about these provider files and the directories into which you must copy them Caution: You must ensure that the names you select for a generic technology connector and its constituent objects on a staging server do not cause naming conflicts with existing connectors and objects on the production server. The following scenario explains why you must follow this guideline: Suppose you create a generic technology connector on a staging server, and want to import the connector to a production server. While creating the generic technology connector on the staging server, you would have ensured that the names of the generic technology connector and the connector objects are unique on that server. At the same time, you must also ensure that the names are not the same as the names of connectors and connector objects on the production server. If any of the names happen to be the same, the old objects would be overwritten by the new objects when you import the connector XML file from the staging server to the production server. No message is displayed during the overwrite process, and the process would lead to eventual failure of the affected connectors. This is also mentioned in Section 22.2.1, Names of Generic Technology Connectors and Connector Objects To ensure that you are able to revert to a working state in the event that an object is overwritten, you must create a backup of the destination Oracle Identity Manager database before you import a connector XML file. Creating and Managing Generic Technology Connectors 21-39 After you import the connector XML file, you must update the run-time parameters of the generic technology connector. To update the values of the run-time parameters, follow the procedure described in Section 21.5.7, Modifying Generic Technology Connectors .

21.4 Using the Generic Connection Pool Framework in Custom Connectors

Custom connectors can choose to use the Generic Connection Pool framework sometimes referred to as the GCP for any connection pooling needs. Internally, the Generic Connection Pool framework uses Oracle Universal Connection Pool UCP as the default connection pooling mechanism. Basic steps to use the Generic Connection Pool in a custom connector include: 1. Provide a concrete implementation for the ResourceConnection interface. The implementation should also have a default constructor with no parameters. 2. Define the additional fields in the ITResource definition. 3. Invoke the Generic Connection Pool to obtain and release connections from the pool. Topics in this section include: ■ Providing concrete implementation for ResourceConnection interface ■ Defining Additional ITResource Parameters ■ Getting and Releasing Connections from the Pool ■ Using a Third-party Pool ■ Example: Implementation of ResourceConnection

21.4.1 Providing concrete implementation for ResourceConnection interface

The connection pool makes use of the concrete implementation of ResourceConnection to create and close connections, and to validate connections to the target. Thus, you should ensure that this concrete implementation class is available as a jar file under the JavaTasks folder. Table 21–5 describes key methods of ResourceConnection: Note: These values are not copied in the connector XML file when you export it.