Create the mapping file with appropriate mapping rules. The mapping file is one

Bootstrapping a Directory in Oracle Directory Integration Platform 8-7 OF_MANAGED_SERVERlogsNAME_OF_MANAGED_ SERVER-diagnostic.log If you use the syncProfileBootstrap command, following the bootstrapping process the lastchangenumber attribute is initialized for further synchronization.

8.2 Bootstrapping in SSL Mode

You can use either a parameter file or an integration profile to bootstrap in SSL mode. When you bootstrap in SSL mode, either Oracle Internet Directory, the connected directory, or both Oracle Internet Directory and the connected directory can be running SSL mode. To bootstrap in SSL mode from a parameter file, you must assign values of either true or false to the odip.bootstrap.srcsslmode and odip.bootstrap.destsslmode arguments in the parameter file. When you bootstrap from an integration profile, the value assigned to the default integration profiles odip.profile.condirurl is used to establish an SSL connection to the connected directory.

8.2.1 Adding a Trusted Certificate to the DIP Keystore

When bootstrapping in SSL mode, Directory Integration Platform needs to have the trusted certificate of the third party directory in its keystore. DIP will connect to the third party directory using SSL Server-Auth mode.

8.2.1.1 To Add a Trusted Certificate to the DIP Keystore

Complete the following before starting the bootstrap in SSL mode. 1. Create a new Java Key Store using the keytool command in some physical location and add the third party directory trusted certificate into this keystore. keytool -importcert -noprompt -trustcacerts -alias ALIAS_ NAME -file PATH_TO_CERTIFICATE_FILE -keystore PHYSICAL_ LOCATION_OF_KEYSTORE -storepass KEYSTORE_PASSWORD 2. Configure the Java Key Store JKS location created in the previous step in the Directory Integration Platform application. In the following command, WLS stands for WebLogic Server. OHbinmanageDIPServerConfig set -attr keystorelocation -val FULL_PATH_TO_KEYSTORE -h WLS_HOST -p WLS_MANAGED_ SERVER_PORT -wlsuser WLS_USER 3. Create a CSF Credential Store Framework password credential so that DIP can read the password from CSF and open the keystore for validating the certificates. a. Run the following command: MW_HOMEoracle_commoncommonbinwlst.sh b. Run the following command: connectWLSUSER,WLSPWD, t3:HOST:ADMINSERVER_PORT c. Run the following WLST command to create a credential: createCredmap=dip, key=jksKey, user=cn=odisrv,cn=Registered Instances,cn=Directory