Deleting a Third-Party Directory External Authentication Plug-in

A-2 Oracle Fusion Middleware Administrators Guide for Oracle Directory Integration Platform ■ Oracle Directory Integration Platform server is deployed and undeployed using WLST commands or the Oracle WebLogic Server Administrative Admin console. ■ The Quartz Scheduler is used for scheduling processing. ■ One instance of Oracle Directory Integration Platform schedules all synchronization and provisioning profiles. ■ No concept of configset and profile groups. All enabled profiles are scheduled. A.2 Configuration Files In 10g Releases 10.1.4.x: ■ The ORACLE_HOMEldapodiconfodi.properties file contained the Oracle Directory Integration Platform server password used to connect to Oracle Internet Directory. It also contained the Oracle Wallet location and password. ■ The connection details for the Oracle Internet Directory associated with Oracle Directory Integration Platform were specified as part of command to start Oracle Directory Integration Platform. ■ Oracle Wallet was used for storing certificates. In 11g Release 1 11.1.1: ■ The associated Oracle Internet Directory host and port details are stored in the dip-config.xml file in dipapps.ear. ■ Java Keystore is used for storing the SSL certificates. ■ The password Oracle Directory Integration Platform uses to connect to Oracle Internet Directory is stored in the Credential Store Framework. The JKS passwords are also stored in the Credential Store Framework. ■ All parameters required for Oracle Directory Integration Platform to start are specified in the dip-config.xml file. A.3 Templates for Mapping, Configuration, and Properties Files In 10g Releases 10.1.4.x: ■ Templates for mapping and configuration files for all connected directories were located in the ORACLE_HOMEldapodiconf directory. ■ Templates for mapping, configuration, and properties files for LDIF, Tagged directories were located in the ORACLE_HOMEldapodisamples directory. ■ Templates for bootstrapping files were located in the ORACLE_ HOMEldapodisamples directory. In 11g Release 1 11.1.1: ■ Templates for mapping and configuration files for all connected directories are located in the ORACLE_HOMEldapodiconf directory. ■ Templates for mapping, configuration, and properties files for LDIF, Tagged directories are located in the ORACLE_HOMEldapodisamples directory. Refer to Appendix B, Example Properties File for Synchronization Profiles for more information. Comparing Oracle Directory Integration Platform 11g Release 1 11.1.1 and 10g Releases 10.1.4.x A-3 ■ Templates for bootstrapping files are located in the ORACLE_ HOMEldapodisamples directory. Refer to Bootstrapping Using a Parameter File on page 8-3 for more information. A.4 Log Files In 10g Releases 10.1.4.x: ■ Oracle Directory Integration Platform server log file was located in the ORACLE_ HOMEldaplog directory. ■ Individual logs for each profile were located in the ORACLE_ HOMEldapodilog directory. Logs used a file naming convention of PROFILE_NAME.log. In 11g Release 1 11.1.1: ■ Log files are located at: MW_HOMEuser_projectsdomainsDOMAIN _NAMEserversNAME_OF_ MANAGED_SERVERlogsNAME_OF_MANAGED_SERVER.log A.5 Graphical User Interfaces In 10g Releases 10.1.4.x: ■ DIPAssistant -gui was the Graphical User Interface GUI tool for managing synchronization profiles. In 11g Release 1 11.1.1: ■ Use Oracle Enterprise Manager Fusion Middleware Control to manage synchronization and provisioning profiles. Refer to Using Fusion Middleware Control on page 3-1 for more information. A.6 Command-Line Tools In 10g Releases 10.1.4.x: ■ dipassistant: Was used to manage synchronization profiles. ■ oidprovtool: Was used to manage provisioning profiles. In 11g Release 1 11.1.1: ■ dipStatus: Allows you to check the status of Oracle Directory Integration Platform and whether or not it is registered. Refer to Viewing the Status of Oracle Directory Integration Platform Using the dipStatus Utility on page 4-3 for more information. ■ manageDIPServerConfig: Manages Oracle Directory Integration Platform configuration settings including refresh interval, Oracle Internet Directory port number, keystore location and password, and the number of scheduler threads. Note: This log file contains the logs for the Oracle Directory Integration Platform server and all profiles.