8.2 Bootstrapping by Using a Parameter File

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 the dipassistant section of the Oracle Directory Integration and Provisioning tools chapter in the Oracle Identity Management User Reference.

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:

Bootstrapping Without Using an LDIF File
Bootstrapping by Using an LDIF File

8.2.1 Bootstrapping Without Using an LDIF File

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
```

8.2.2 Bootstrapping by Using an LDIF File

This section describes two ways to bootstrap a directory by using an LDIF file.

8.2.2.1 Bootstrapping from an LDIF File by Using Directory-Dependent Tools to Read the Source Directory

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
```

8.2.2.2 Bootstrapping from an LDIF File by Using the Directory Integration and Provisioning Assistant to Load Data to Oracle Internet Directory

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
```