Creating Synchronization Profiles Managing Synchronization Profiles Using Fusion Middleware Control
7-4 Oracle Fusion Middleware Administrators Guide for Oracle Directory Integration Platform
OU=myou,OU=test,DC=mycompany,DC=com, or by clicking Lookup and browsing to the domain, and then clicking OK in the Create Domain Exclusion
Container dialog box.
■
DIP-OID Container to Exclude : This parameter appears if you are configuring an
export profile. Identify the domains to be excluded during bootstrap and synchronization for by entering a value, for example,
OU=myou,OU=test,DC=mycompany,DC=com, or by clicking Lookup and browsing to the domain, and then clicking OK in the Create Domain Exclusion
Container dialog box.
The following is a list and description of the Attribute Mapping Rules parameters:
■
Source Object Class : Select the object class in the source directory. Do not select a
value when synchronizing with a non-LDAP source.
■
Source Attributes : The source directory attributes to which you want to apply the
mapping rule. When synchronizing with LDAP sources, select the Single Attributes option and enter the appropriate attributes in the Attributes field. When
synchronizing with non-LDAP sources, select the Multiple Attributes option and enter the appropriate attributes in the Multivalue Attributes field.
■
Source Attribute Required : Enable or disable the source attribute requirement.
■
DIP-OID Object Class : Select the destination object type or class. Use the
destination object class for LDAP targets.
■
DIP-OID Attribute : Select the destination attribute name to which you want to
apply the mapping rule.
■
DIP-OID Attribute Type : Enter the type of the attribute in the destination
directory.
■
Mapping Expression : Enter the transformation rule that derives the destination
attribute value from the source attribute value. The following is a list and description of the Attribute Exclusion List parameters:
■
ObjectClass : Select the objectclass that contains the attributes you want to add to
the Attribute Exclusion List. After you select an objectclass, its attributes appear in the Multiple Address field.
■
Attributes : Select the attributes you want to add to the Attribute Exclusion List.
Filtering The Filtering tab contains the following parameters that configure the filter settings for
the profile:
■
Source Matching Filter : Specify the attribute that uniquely identifies an entry in
the connected directory or specify an LDAP search filter for the connected directory in the format searchfilter=ldap_search_filter.
■
Destination Matching Rule : Specify the attribute that uniquely identifies records
in Oracle Internet Directory. This attribute is used as a key to synchronize Oracle Internet Directory with the connected directory.
■
Associated Profile : The Associated Profile filtering setting is used to avoid loop
back changes in bi-directional synchronization where changes initiated from one directory return to the same directory. For import profiles, specify the export
profile it is associated with in the Associated Profile field. For export profiles, specify the import profile used for synchronizing the data from that directory.
Managing Directory Synchronization Profiles 7-5
Advanced The Advanced tab contains the following parameters that configure the advanced
settings for the profile:
■
Scheduling Interval HH:MM:SS : Specify the number of hours, minutes, and
seconds between synchronization attempts between a connected directory and Oracle Internet Directory.
■
Maximum Number of Retries : Specify the maximum number of times the
synchronization is to be retried before synchronization stops. The default is 5. The first retry takes place one minute after the first failure. The second retry happens
two minutes after the second failure, and subsequently the retry takes place n minutes after the n failure.
■
Log Level : Specify the logging level for debugging. Selecting the All level logs all
information, including entries that are synchronized.
■
Last Change Number : Identifies the number of changes that synchronization has
been performed for. When you create a synchronization profile, the Last Change Number parameter is locked—you cannot enter a value for it.
After you create a synchronization profile and attempt to edit it, an additional option named Edit and Persist is available for the Last Change Number parameter.
You can edit the value for the Last Change Number parameter if you select enable the Edit and Persist option. Enabling the Edit and Persist option causes
the Last Change Number to be persisted in the profile. Changes to the Last Change Number will not be persisted if the Edit and Persist option is not enabled.
■
Additional Configuration Parameters : This section allows you to manage optional,
advanced configuration parameters. To create an advanced configuration parameter, click Add and identify the parameter and its value. The following is a
list and description of each advanced configuration parameter:
■
Check All Entries : Applicable only for eDirectory and OpenLDAP, it
determines how deleted entries in Novell eDirectory or OpenLDAP are synchronized with Oracle Internet Directory. If you assign a value of true to
this parameter, the Oracle Directory Integration Platform identifies deleted entries by performing a linear comparison between the entries in Oracle
Internet Directory and Novell eDirectory or OpenLDAP. If an entry does not exist in Novell eDirectory or OpenLDAP, the entry is deleted from Oracle
Internet Directory. If you assign a value of false to this parameter, deleted entries are synchronized according to the difference between the number of
entries in the connected directory and the number of entries in Oracle Internet Directory. If the number of deleted entries is 0 or less than 0, then there are no
deleted entries to synchronize. However, if the number of deleted entries is greater than 0, then the Oracle Directory Integration Platform compares each
entry in Oracle Internet Directory with Novell eDirectory or OpenLDAP to identify the deleted entries to synchronize. The Oracle Directory Integration
Note: To disassociate a profile, set the Associated Profile setting to
Select One .
WARNING: Be aware that if you edit the value for the Last Change
Number, setting an incorrect value can cause the profile to stop working or cause erroneous synchronization operations.
7-6 Oracle Fusion Middleware Administrators Guide for Oracle Directory Integration Platform
Platform continues to compare entries until it locates the same number of deleted entries as the difference between the number of entries in the
connected directory and the number of entries in Oracle Internet Directory. For better performance, you should assign a value of false to this parameter.
■
Unique Attribute : Applicable only for eDirectory and OpenLDAP, it identifies
the unique attribute in Novell eDirectory or OpenLDAP that can be used to search for an entry. You assign to this parameter a value of GUID for Novell
eDirectory or entryuuid for OpenLDAP.
■
Attribute Type : Applicable only for eDirectory and OpenLDAP, it indicates
the type of the UniqueAttribute parameter. You assign to this parameter a value of Binary for Novell eDirectory or nonBinary for OpenLDAP. This
parameter is used to obtain the corresponding Oracle Internet Directory attribute for the attribute that is defined in the mapping file.
■
Search Time Delta Size in seconds: This parameter is applicable only for
eDirectory and OpenLDAP, which handle synchronization based on timestamps and do not support changelog. Search Time Delta Size in seconds
determines the time interval for processing changes during each synchronization cycle iteration. The default value is 3600. The number of
iterations performed during each synchronization cycle depend on the number of pending changes. For example, if the Search Time Delta In Seconds
parameter is set to 60 and there are changes pending for about one minute, synchronization will require a single iteration. If changes are pending for three
minutes, synchronization will require three iterations.
■
Search Delta Size: This parameter is applicable when importing changes from
directories that support changelog. Search Delta Size determines how many incremental changes are processed during each iteration in a synchronization
cycle. The default value is a value of 500. The number of iterations performed during each synchronization cycle depend on the number of pending changes.
For example, if the Search Delta Size parameter is assigned a value of 500 and there are 498 pending changes, synchronization will require a single iteration.
However, if there are 501 pending changes, synchronization will require two iterations. In some cases, you will experience better synchronization efficiency
if you assign a higher value to this parameter. However, be sure that the value you specify does not exceed the LDAP search limit of the connected directory
server. Otherwise, you may receive an error during synchronization and some changes may not be processed.
Notes:
■
When the number of changes per minute is small, you will experience better synchronization efficiency by setting Search
Time Delta Size in seconds to a higher value.
■
Be sure the value you set for the Search Time Delta In Seconds parameter does not exceed the LDAP search limit of the connected
directory server. Otherwise, you may receive an error during synchronization and some changes may not be processed.
Note: Be sure to thoroughly analyze and test your deployment when
modifying the Search Delta Size parameter, especially if you assign a value higher than 2000.
Managing Directory Synchronization Profiles 7-7
■
Skip Error To Sync Next Change: Determines how Oracle Directory
Integration Platform handles an error when processing a change during synchronization. By default, Skip Error To Sync Next Change is assigned a
value of false, which means that Oracle Directory Integration Platform will continue processing a change until the error is resolved. If you assign a value
of true to Skip Error To Sync Next Change, Oracle Directory Integration Platform will skip any changes that cause an error. All failures are recorded in
the ORACLE_HOMEldapodilogprofile_name.aud audit log. If you set Skip Error To Sync Next Change to true, be sure to periodically review the
audit log for failures.
■
Update Search Count: Specifies the maximum number of iterations to
perform on the connected directory during the synchronization process. The synchronization process stops after the specified number of search has been
performed and resumes at the next scheduled interval.
■
Reduce Filter Time In Seconds : Applicable only for eDirectory and
OpenLDAP, it specifies the time difference between a computer that is running Oracle Internet Directory and a computer that is running Novell eDirectory.
This parameter is necessary because synchronization between Oracle Internet Directory and Novell eDirectory will not function properly if the time on the
Novell eDirectory computer is earlier than the time on the Oracle Internet Directory computer. You assign to this parameter a value in seconds that is
equal to the time difference between the two computers. The default value is 0.
■
Writer : Identifies the Writer used by the profile for synchronization. This is a
read only value and is used only for information purposes.
■
Reader : Identifies the Reader used by the profile for synchronization. This is a
read only value used only for information purposes.
■
Reconciler : Do not modify this parameter. It identifies the class used by the
profile for reconciliation purposes. The parameter is applicable only for eDirectory and OpenLDAP. This is a read only value used only for
information purposes.