|
Oracle® Identity Management Integration Guide
10g Release 2 (10.1.2) Part No. B14085-01 |
|
 Previous |
 Next |
|
Oracle® Identity Management Integration Guide
10g Release 2 (10.1.2) Part No. B14085-01 |
|
|
Previous |
Next |
This chapter discusses directory bootstrapping, which refers to the initial migration of data between a connected directory and Oracle Internet Directory. Because the synchronization process can handle the migration of data between a connected directory and Oracle Internet Directory, you are not required to perform directory bootstrapping. However, relying on the synchronization process to perform the initial migration can be a time consuming process, especially for large amounts of data. For this reason, you should perform directory bootstrapping when you first deploy Oracle Directory Integration and Provisioning.
This chapter contains these topics:
About Directory Bootstrapping in Oracle Directory Integration and Provisioning
Bootstrapping Directly by Using the Default Integration Profile
In Directory Integration and Provisioning, bootstrapping is handled by using the Directory Integration and Provisioning Assistant with the bootstrap option. The command is:
dipassistant bootstrap
For information about usage of the Directory Integration and Provisioning Assistant, enter:
dipassistant bootstrap -help
The Directory Integration and Provisioning Assistant enables you to bootstrap by using either a parameter file or a completely configured integration profile. This chapter discusses both approaches.
The parameters in this file specify:
The source and destination data types
Credentials
The way the entries need to be mapped between Oracle Internet Directory and the connected directory
The various parameters and the default values that the Directory Integration and Provisioning Assistant assumes for them while reading the file are given in Table A-30.
You can bootstrap by using an LDIF file in one of these ways:
By using the Directory Integration and Provisioning Assistant to read from the source directory
By using directory-dependent tools to read from the source directory
By using the Directory Integration and Provisioning Assistant to load data to Oracle Internet Directory
During installation, sample parameter files are copied to the $ORACLE_HOME/ldap/odi/samples/ directory. Each file describes the significance of each of the parameters in bootstrapping.
When you run the tools for bootstrapping, be sure that the ORACLE_HOME and NLS_LANG settings are correct.
Bootstrapping can be performed between services with or without one or more intermediate files. However, for large directories, an intermediate LDIF file is required.
This section contains these topics:
Oracle recommends this method for smaller directories where the entries are:
Relatively few in number
In a flat structure
Not interdependent—that is, the creation of one entry does not depend on the existence of another as, for example, when the creation of a group entry depends on the existence of user member entries
To use this method:
Prepare the mapping file with appropriate mapping rules. The mapping file is one of the properties in the bootstrap file. Be sure that it is compatible with the mapping rules defined for synchronization.
Create the parameter file with the required details specifying the source as LDAP and the destination type as LDIF. A sample parameter file, ldp2ldf.properties, is available in $ORACLE_HOME/ldap/odi/samples. Make sure that binary attributes are specified as binary in the SrcAttrType field.
Use the Directory Integration and Provisioning Assistant bootstrap command using a configuration file in which:
The source is specified as an LDAP directory
The destination type is specified as LDIF. Dump the data to an LDIF file.
Execute the Directory Integration and Provisioning Assistant as follows:
Dipassistant bootstrap –cfg parameter_file
Check the bootstrap.log and bootstrap.trc files for any errors.
Use bulkload to upload the data to Oracle Internet Directory.
For continued synchronization, update the last change number:
dipassistant mp –profile profile_name -updcln
This section describes two ways to bootstrap a directory by using an LDIF file.
Oracle Corporation recommends that you use this method for large directories. To use this method:
Download the data from the directory to an LDIF file. The tool you use depends on the directory from which you are loading the data. If you are bootstrapping from a Microsoft Active Directory, then use "ldifde" to load the data. Be sure to load all the required attributes for each entry.
Prepare the mapping file with appropriate mapping rules. When you want to do further synchronization, be sure that the mapping file is the same as the one used for synchronization.
Create the parameter file with source and destination as LDIF and other details. A sample parameter file is available in $ORACLE_HOME/ldap/odi/samples/ldf2ldf.properties.
Use the Directory Integration and Provisioning Assistant bootstrap command with a parameter file in which the source is specified as LDIF and the destination type is specified as LDIF. This converts the source data and creates a new LDIF as required by Oracle Internet Directory. Execute the Directory Integration and Provisioning Assistant as follows:
dipassistant bootstrap –cfg parameter_file
Check the bootstrap.log and bootstrap.trc files for any errors.
Use The Oracle Internet Directory bulkload tool (bulkload.sh) to upload the data to Oracle Internet Directory.
If a corresponding synchronization profile is created for further synchronization, then update the last change number:
dipassistant mp –profile profile_name -updcln
To use this method:
Download the data from the directory to an LDIF file. The tool you use depends on the directory from which you are loading the data. If you are bootstrapping from a Microsoft Active Directory, then use "ldifde" to load the data. Be sure to load all the required attributes for each entry.
Prepare the mapping file with appropriate mapping rules. When you want to do further synchronization, be sure that the mapping file is the same as the one used for synchronization.
Create the properties file with the source specified as LDIF and the destination specified as LDAP.
Use the Directory Integration and Provisioning Assistant bootstrap command with a parameter file in which the source is specified as the LDIF file, the destination type is specified as LDAP, and the destination specified as Oracle Internet Directory. This converts the source data and creates entries in Oracle Internet Directory as required. A sample properties file, ldf2ldp.properties, is available in $ORACLE_HOME/ldap/odi/samples.
Check the bootstrap.log and bootstrap.trc files for any errors.
If a corresponding synchronization profile is created for further synchronization, then update the last change number:
dipassistant mp –profile profile_name -updcln
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 distinguished name 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:
Customize the default integration profile IplanetImport, which is created as part of installation by following the instructions in "Task 1: Configure the Synchronization Profiles for the SunONE Connector".
Enter the following command:
dipassistant bootstrap -profile IplanetImport -D 'cn=orcladmin' -w 'welcome'
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.
