Tasks and Examples for syncProfileBootstrap

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_