From the task selection bar, select Advanced.

Migrating Data from Other Data Repositories 36-3 When using an LDIF file and bulkload to migrate data to Oracle Internet Directory, you must perform the following tasks. Task 1: Export Data from the Non-Oracle Internet Directory Server into LDIF File Format See the vendor-supplied documentation for instructions. If flags or options exist for exporting data from the foreign directory, be sure to select the method that: ■ Produces LDIF output with the least amount of proprietary information included ■ Provides maximum conformance to the IETF Request for Comments 2849 of the IETF, available for download at: http:www.ietf.org Task 2: Analyze the LDIF User Data for Any Required Schema Additions Referenced in the LDIF Data Any attributes not found in the Oracle Internet Directory base schema require extension of the Oracle Internet Directory base schema before the importation of the LDIF file. Some directories may support the use of configuration files for defining extensions to their base schema Oracle Internet Directory does not. If you have a configuration file you can use it as a guideline for extending the base schema in Oracle Internet Directory in Task 3: Extend the Schema in Oracle Internet Directory . Task 3: Extend the Schema in Oracle Internet Directory See Chapter 20, Managing Directory Schema for tips on how to extend the directory schema in Oracle Internet Directory. You can do this by using either Oracle Directory Services Manager or the SchemaSynch tool, which is documented in Oracle Fusion Middleware Reference for Oracle Identity Management. If you have users who are using other Oracle products, you must create users with object class orclUserV2 and its required attributes. If you are integrating with Active Directory, you must create users with object class orclADUser and its required attributes. These object classes and their attributes are documented inOracle Fusion Middleware Reference for Oracle Identity Management. Task 4: Remove Any Proprietary Directory Data from the LDIF File Certain elements of the LDAP v3 standard have not yet been formalized, such as ACI attributes. As a result, various directory vendors implement ACI policy objects in ways that do not translate well across vendor installations. After the basic entry data has been imported from the cleaned up LDIF file to Oracle Internet Directory, you must explicitly reapply security policies in the Oracle Internet Directory environment. You can do this by using either Oracle Directory Services Manager, or command-line tools and LDIF files containing the desired ACP information. There may be other proprietary metadata unrelated to access control. You should remove this as well. Understanding the various IETF RFCs can help you determine which directory metadata is proprietary to a given vendor and which complies with the LDAP standards, and is thus portable by way of an LDIF file. Task 5: Remove Operational Attributes from the LDIF File Four of the standard LDAP v3 operational attributes, namely, creatorsName, createTimestamp, modifiersName, and modifyTimestamp are automatically See Also: RFC 2849 of the IETF, available for download at: http:www.ietf.org