Arguments for syncProfileBootstrap Directory Bootstrapping Using syncProfileBootstrap

Bootstrapping a Directory in Oracle Directory Integration Platform 8-5

8.1.5.2 Bootstrapping Using an LDIF File

This section describes the following two ways to bootstrap a directory by using an LDIF file: ■ Bootstrapping from an LDIF File Using Directory-Dependent Tools to Read the Source Directory ■ Bootstrapping from an LDIF File Using the syncProfileBootstrap Command to Load Data into Oracle Internet Directory Bootstrapping from an LDIF File Using Directory-Dependent Tools to Read the Source Directory Oracle recommends that you use this method for large directories. To use this method: 1. 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 the ldifde command to load the data. Be sure to load all the required attributes for each entry. 2. Create 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. 3. Create the parameter file with source and destination as LDIF and other details. A sample parameter file is available in: ORACLE_HOMEldapodiconfldf2ldf.properties. 4. Use the syncProfileBootstrap 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. Run the syncProfileBootstrap command as follows: syncProfileBootstrap -profile profile_name -loadParallelism threads -loadRetry retries 5. Check the NAME_OF_MANAGED_SERVER-diagnostic.log file for any errors. This file can be found in the following location: MW_HOMEuser_projectsdomainsDOMAIN_NAMEserversNAME_ OF_MANAGED_SERVERlogsNAME_OF_MANAGED_ SERVER-diagnostic.log 6. Use bulkload.sh or the ldapadd command to upload the data to Oracle Internet Directory. 7. To continue synchronization, use the updatechgnum operation of the manageSyncProfiles command to update the last change number, as follows: manageSyncProfiles updatechgnum -h HOST -p PORT -D wlsuser \ -profile my_Import_Profile Bootstrapping from an LDIF File Using the syncProfileBootstrap Command to Load Data into Oracle Internet Directory To use this method: 1. 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 the ldifde command to load the data. Be sure to load all the required attributes for each entry. 8-6 Oracle Fusion Middleware Administrators Guide for Oracle Directory Integration Platform 2. 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. 3. Create the properties file with the source specified as LDIF and the destination specified as LDAP. 4. Use the syncProfileBootstrap 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_HOMEldapodisamples. 5. Check the NAME_OF_MANAGED_SERVER-diagnostic.log file for any errors. This file can be found in the following location: MW_HOMEuser_projectsdomainsDOMAIN_NAMEserversNAME_ OF_MANAGED_SERVERlogsNAME_OF_MANAGED_ SERVER-diagnostic.log 6. To continue synchronization, use the updatechgnum operation of the manageSyncProfiles command to update the last change number, as follows: manageSyncProfiles updatechgnum -h HOST -p PORT -D wlsuser \ -profile my_Import_Profile

8.1.6 Bootstrapping Directly Using the Default Integration Profile

Bootstrapping relies on an existing integration profile configured for synchronization. The configuration information 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 uploading the entries, then the information is logged in the NAME_OF_MANAGED_ SERVER-diagnostic.log file located in the MW_HOMEuser_ projectsdomainsDOMAIN_NAMEserversNAME_OF_MANAGED_ SERVERlogs directory. For example, for bootstrapping from Oracle Directory Server Enterprise Edition previously Sun Java System Directory Server to Oracle Internet Directory, you would do the following: 1. Customize the default integration profile iPlanetImport, which is created as part of the installation by following the instructions in Configuring Advanced Integration with Oracle Directory Server Enterprise Edition on page 20-2. 2. Enter the following command: syncProfileBootstrap -h HOST -p PORT -D wlsuser -profile iPlanetImport -loadParallelism 5 -loadRetry 3 3. Check the NAME_OF_MANAGED_SERVER-diagnostic.log file for any errors. This file can be found in the following location: MW_HOMEuser_projectsdomainsDOMAIN_NAMEserversNAME_