Click the Plug-ins ta In the Deployed Plus-ins table, click the changelog plug-in, then click Edit in Click OK. Tuning Oracle Virtual Directory Backing Up the Oracle Virtual Directory Configuration

Extending the Domain with Oracle Virtual Directory 9-19 7. To edit the change adapter follow these steps. a. Select the OIM Changelog Adapter. b. Click the Plug-ins tab.

c. In the Deployed Plus-ins table, click the changelog plug-in, then click Edit in

the plug-ins table. The plug-in editing window appears. d. In the Parameters table, update the parameter values. Edit the Changelog Adapter to either add or modify the properties so that they match the values shown in the following table. You must add the mapObjectclass, modifierDNFilter, sizeLimit, and targetDNFilter properties to the adapter.

e. Click OK.

f. Click Apply.

Server Proxy Bind DN The bind DN of a user who has access to Sun Java System Directory Server. Proxy Password Password for oimLDAP user. Connection Test Validate that the test succeeds. Namespace Remote Base cn= Mapped Namespace cn=changelog Summary Verify that the summary is correct, then click Finish. Parameter Value Comments directoryType sunone Default mapAttribute targetGUID=targetUniqueID Default mapObjectclass changelog=changelogentry Create modifierDNFilter The bind DN of a user who has access to Sun Java System Directory Server. Create sizeLimit 1000 Create targetDNFilter dc=mycompany,dc=com Search base from which reconciliation must happen. This value must be the same as the LDAP SearchDN that is specified during Oracle Identity Manager installation. Create mapUserState true oamEnabled true 1 1 Set oamEnabled to true only if you are using Oracle Access Manager. Screen Field ValueStep 9-20 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management

9.8.4 Validating the Oracle Virtual Directory Adapters

Perform the following tasks by using ODSM: 1. Connect to Oracle Virtual Directory. 2. Go the Data Browser tab. 3. Expand Client View so that you can see each of your user adapter root DNs listed. 4. Expand the user adapter root DN, if there are objects already in the back end LDAP server, you should see those objects here. 5. ODSM doesnt support changelog query, so you cannot expand the cn=changelog subtree. Perform the following tasks by using the command-line: ■ Validate the user adapters by typing: ldapsearch -h directory_host -p ldap_port -D cn=orcladmin -q -b user_ search_base -s sub objectclass=inetorgperson dn For example: ldapsearch -h ovdhost1.mycompany.com -p 6501 -D cn=orcladmin -q -b cn=Users,dc=mycompany,dc=com -s sub objectclass=inetorgperson dn Supply the password when prompted. You should see the user entries that already exist in the back end LDAP server. ■ Validate changelog adapters by typing: ldapsearch -h directory_host -p ldap_port -D cn=orcladmin -q -b cn=changelog -s one changenumber=0 For example: ldapsearch -h ovdhost1 -p 6501 -D cn=orcladmin -q -b cn=changelog -s one changenumber=0 The command returns no data at this stage, as Oracle Identity Manager is not generating changes. However, the command returns without error if changelog adapters are valid.

9.9 Tuning Oracle Virtual Directory

For information about tuning Oracle Virtual Directory, see Oracle Fusion Middleware Administrators Guide for Oracle Virtual Directory.

9.10 Backing Up the Oracle Virtual Directory Configuration

It is an Oracle best practices recommendation to create a backup file after successfully completing the installation and configuration of each tier or a logical point. Create a backup of the installation after verifying that the install so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps. The backup destination is the local disk. This backup can be discarded once the enterprise deployment setup is complete. After the enterprise deployment setup is complete, the regular deployment-specific Backup and Recovery process can be initiated. More details are described in the Oracle Fusion Middleware Administrators Guide. Extending the Domain with Oracle Virtual Directory 9-21 For information on database backups, refer to Oracle Database Backup and Recovery Users Guide. To back up the installation to this point, follow these steps: 1. Back up the directory tier: a. Shut down the instance using opmnctl located under the ORACLE_ INSTANCE bin directory: ORACLE_INSTANCE binopmnctl stopall b. Create a backup of the Middleware home on the directory tier. On Linux, as the root user, type: tar -cvpf BACKUP_LOCATIONdirtier.tar MW_HOME c. Create a backup of the Instance home on the directory tier as the root user: tar -cvpf BACKUP_LOCATIONinstance_backup.tar ORACLE_INSTANCE d. Start up the instance using opmnctl located under the ORACLE_ INSTANCE bin directory: ORACLE_INSTANCE binopmnctl startall 2. Perform a full database backup either a hot or cold backup. Oracle recommends that you use Oracle Recovery Manager. 3. Back up the Administration Server domain directory. This saves your domain configuration. The configuration files all exist under the ORACLE_ BASE admindomainNameaserver directory. On Linux, type: IDMHOST1 tar cvf edgdomainback.tar ORACLE_BASEadmindomainNameaserver Note: Create backups on all machines in the directory tier by following the steps shown in this section. For more information about backing up the directory tier configuration, see Section 20.4, Performing Backups and Recoveries. 9-22 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 10 Preparing Identity and Policy Stores 10-1 10 Preparing Identity and Policy Stores This chapter describes how to prepare the Identity and Policy Stores. It contains the following sections: ■ Section 10.1, Backing up the LDAP Directories