Bootstrapping Directly by Using the Default Integration Profile

Bootstrapping relies on an existing integration profile configured for synchronization. The configuration details are used to connect to the third-party directory.

While using this method, put the source directory in read-only mode.

If the profile is an IMPORT profile, then footprints of the required objects in the connected directory are created in Oracle Internet Directory. If the profile is an EXPORT profile, then footprints of the required objects from Oracle Internet Directory are created in the connected directory.

While creating these entries, the domain-level and object-level mappings as specified in the integration profile are used. If there is a failure in uploading the entries, then the information is logged in $ORACLE_HOME/ldap/odi/log/bootstrap.log. The trace information is written to the file $ORACLE_HOME/ldap/odi/log/bootstrap.trc.

For example, for bootstrapping from SunONE Directory Server to Oracle Internet Directory, you would do the following:

1. Customize the default integration profile IplanetImport, which is created as part of installation by following the instructions in "Task 1: Configure the Integration Profile for the SunONE Connector".

2. Enter the following command:

   dipassistant bootstrap -profile IplanetImport -dn  'cn=orcladmin' -passwd 
   'welcome' 
   

3. Check the bootstrap.log and bootstrap.trc files to be sure that the bootstrapping is successfully completed.

If you are bootstrapping by using the Directory Integration and Provisioning Assistant, then, at the end of the bootstrapping process, the assistant initializes the lastchangenumber attribute for further synchronization.

See Also: "Limitations of the Directory Integration and Provisioning Assistant in Oracle Internet Directory 10g (9.0.4)"