Setting Null Values in Synchronization Profiles

8-2 Oracle Fusion Middleware Administrators Guide for Oracle Directory Integration Platform This topic includes the following sections: ■ Syntax for syncProfileBootstrap ■ Arguments for syncProfileBootstrap ■ Tasks and Examples for syncProfileBootstrap ■ Recommended Bootstrapping Methodology ■ Bootstrapping Using a Parameter File ■ Bootstrapping Directly Using the Default Integration Profile

8.1.1 Syntax for syncProfileBootstrap

syncProfileBootstrap syncProfileBootstrap -h HOST -p PORT -D wlsuser {-file FILENAME |-profile -PROFILE_NAME} [-ssl -keystorePath PATH_TO_KEYSTORE -keystoreType TYPE] [-loadParallelism INTEGER] [-loadRetry INTEGER][-help]

8.1.2 Arguments for syncProfileBootstrap

-h | -host Oracle WebLogic Server host where Oracle Directory Integration Platform is deployed. -p | -port Listening port of the Oracle WebLogic Managed Server where Oracle Directory Integration Platform is deployed. -D | wlsuser Oracle WebLogic Server login ID -f | -file Bootstrap properties file. -pf | -profile The name of the synchronization profile to use when performing the operation. -ssl Executes the command in SSL mode. Note: You will be prompted for the Oracle WebLogic Server login password. You cannot provide the password as a command-line argument. Best security practice is to provide a password only in response to a prompt from the command. If you must execute syncProfileBootstrap from a script, you can redirect input from a file containing the Oracle WebLogic Server login password. Use file permissions to protect the file and delete it when it is no longer necessary. Bootstrapping a Directory in Oracle Directory Integration Platform 8-3 -keystorePath The full path to the keystore. -keystoreType The type of the keystore identified by -keystorePath. For example: -keystorePath jks or -keystorePath PKCS12 -lp | -loadParallelism Indicator that loading to Oracle Internet Directory is to take place in parallel by using multiple threads. For example, -loadparallelism 5 means that 5 threads are to be created, each of which tries to load the entries in parallel to Oracle Internet Directory. -lr | -loadRetry The number of times the retry should be made when the load to the destination fails before marking the entry as bad entry. -help Provides command usage help.

8.1.3 Tasks and Examples for syncProfileBootstrap

manageSyncProfileBootstrap -h myhost.mycompany.com -p 7005 -D login_ID \ -pf myProfile -lp 5 manageSyncProfileBootstrap -h myhost.mycompany.com -p 7005 -D login_ID \ -f optldapodipbootstrap.properties -lr 3

8.1.4 Recommended Bootstrapping Methodology

If the source directory from which you are loading data contains a large number of entries, the quickest and easiest method to bootstrap the target directory is by using an LDIF file. Bootstrapping with an integration profile is not recommended in this case because connection errors may occur when reading and writing between the source and target directories. Using an LDIF file is also recommended if the DNs contain special characters, which may not be escaped properly when bootstrapping with an integration profile.

8.1.5 Bootstrapping Using a Parameter File

The parameters in this file specify: ■ Source and destination interface types LDIF and LDAP ■ Connection details and credentials valid only for LDAP ■ Mapping rules Note: The Oracle WebLogic Managed Server where Oracle Directory Integration Platform is deployed must be configured for SSL to execute this command in SSL mode. Refer to the Configuring SSL chapter in Oracle Fusion Middleware Securing Oracle WebLogic Server for more information. 8-4 Oracle Fusion Middleware Administrators Guide for Oracle Directory Integration Platform You can bootstrap using an LDIF file by using directory-dependent tools to read from the source directory. During installation, the following sample parameter files are copied to the ORACLE_ HOMEldapodiconf directory: ■ Ldp2ldp.properties ■ Ldp2ldf.properties ■ Ldf2ldp.properties ■ Ldf2ldf.properties The preceding files describe 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.

8.1.5.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:

1. Create 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.

2. 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_HOMEldapodisamples. Make sure that binary attributes are specified as binary in the SrcAttrType field. 3. Execute the syncProfileBootstrap command with a configuration file that contains: ■ The source is specified as an LDAP directory. ■ The destination type is specified as an LDIF. 4. 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 5. Use bulkload.sh or the ldapadd command to upload the data to Oracle Internet Directory. 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