10 Exporting and Importing Adapters

This chapter describes the exporting and importing adapters.

Sometimes, when you create an adapter for one database, you may want to use it with another database. One approach is to manually reconstruct the adapter for that database. However, besides this method being unproductive in terms of time, money, and resources, the developer may inadvertently introduce an error while re-creating the adapter. As a result, once the process with which this adapter is associated is provisioned to the target user or organization, the adapter will not be able to perform its designated function, and Oracle Identity Manager will not be able to provision the corresponding resource to that user or organization.An alternate method, which is more efficient, and eliminates the chance for error, is to:

1. Create a bug-free adapter and apply it properly within one database. The Deployment Manager, internally, builds an *.xml file, which contains this adapter and all of its internal variable mappings.

   The Deployment Manager also exports this file into a designated location.

2. Retrieve the file from the location, and import it into the target database.

You can use Deployment Manager to transfer adapters from one database to another. Refer to the Oracle Identity Manager Administrative and User Console Guide for instructions about how to use Deployment Manager.

Note:

Any adapter that you import into a target database must be recompiled within that database. Also, you should copy the third-party jars files, after migrating the adapter. Otherwise, the adapter will not work.