Excluding Attributes Attribute-Level Mapping

Configuring Directory Synchronization 6-11 This is required when you need search on the value of objectguid. ■ tolower: Converts the String attribute value to lowercase. firstname: : : :givenname: :inetorgperson: tolowerfirstname ■ toupper : Converts the String attribute value to uppercase. firstname: : : :givenname: :inetorgperson: toupperfirstname ■ truncstr,char: Truncates the string beginning from the first occurrence of the specified char. mail : : : : uid : : inetorgperson : truncmail,’’ For example, if mail is John.Doeacme.com in the source, then this rule results in the uid attribute in the destination with the value John.Doe. ■ trunclstr, char: Truncates the string up to and including the first occurrence of the specified char. For example: mail : : : : uid : : inetorgperson : trunclmail, ■ truncrstr, char: Truncates everything in the string that appears on the right side of the specified char. For example: mail : : : : uid : : inetorgperson : truncrmail, ■ dnconvert str: Converts DN type attributes if domain mapping is used. This example assumes the following domain mapping rule: DomainRules cn=srcdomain:cn=dstdomain: For example: uniquemember : : : groupofuniquenames : uniquemember : :groupofuniquenames : dnconvertuniquemember In this example, if uniquemember in the source is cn=testuser1,cn=srcdomain, then uniquemember in the destination becomes cn=test user1,cn=dstdomain. ■ Literals: Userpassword: : :person: userpassword: :person: ’welcome1’

6.4.5 Example: Mapping File for a Tagged-File Interface

Based on the preceding discussions, here is a sample mapping file for importing user entries from the Oracle Human Resources database tables by using the tagged-file interface. Note that the source is a non-LDAP directory. This sample file is supplied during installation, at ORACLE_HOMEldapodiconforaclehragent.map.master. DomainRules NONLDAP:dc=myCompany,dc=com:uid=dc=myCompany,dc=com AttributeRules firstname: : : :cn: :person email : : : :cn: :person: truncemail, email : 1 : :uid: :person:truncemail, firstname,lastname: : : :cn: :person: firstname+,+lastname lastname,firstname: : : :cn: :person: lastname+,+firstname firstname,lastname: : : :sn: :person: lastname | firstname 6-12 Oracle Fusion Middleware Administrators Guide for Oracle Directory Integration Platform EmployeeNumber: : : :employeenumber: :inetOrgperson EMail: : : :mail: :inetOrgperson TelephoneNumber1: : : :telephonenumber: :person TelephoneNumber2: : : :telephonenumber: :person TelephoneNumber3: : : :telephonenumber: :person Address1: : : :postaladdress: :person state: : : :st: :locality street1: : : :street: :locality zip: : : :postalcode: :locality town_or_city: : : :l: :locality Title: : : :title: :organizationalperson Sex: : : :sex: :person As described earlier, the mapping file consists of keywords and a set of domain and attribute mapping rule entries. The mapping file in this example contains the domain rule NONLDAP:dc=myCompany,dc=com:cn=,dc=myCompany,dc=com. ■ This rule implies that the source domain is NONLDAP—that is, there is no source domain. ■ The destination domain :dc=myCompany,dc=com implies that all the directory entries this profile deals with are in the domain dc=myCompany,dc=com. Be sure that the domain exists before you start synchronization. ■ The domain mapping rule :uid=,dc=myCompany,dc=com implies that the data from the source refers to the entry in the directory with the DN that is constructed using this domain mapping rule. In this case, uid must be one of the destination attributes that should always have a non null value. If any data corresponding to an entry to be synchronized has a null value, then the mapping engine assumes that the entry is not valid and proceeds to the next entry. To identify the entry correctly in the directory, it is also necessary that uid is a single value. ■ In the case of the tagged file, the source entry does not have an object class to indicate the type of object to which it is synchronizing. Note that the SrcObjectClass field is empty. ■ Every object whose destination is Oracle Internet Directory must have an object class. ■ Note that email is specified as a required attribute in the sample mapping file. This is because the uid attribute is derived from the email attribute. Successful synchronization requires the email attribute to be specified in all changes specified in the tagged file as follows: Email : 1 : : :uid : : person : truncemail,’’ ■ In some cases, the RDN of the DN needs to be constructed by using the name of a multivalued attribute. For example, to construct an entry with the DN of cn=,l=,dc=myCompany,dc=com, where cn is a multivalued attribute, the DomainMappingRule can be in this form: rdn,l=,dc=myCompany,dc=com where rdn is one of the destination attributes having a non null value. A typical mapping file supporting this could have the following form: DomainRules NONLDAP:dc=us,dc=myCompany,dc=com:rdn,l=,dc=us,dc=myCompany,dc=com AttributeRules firstname: : :cn: :person email : : : :cn: :person: truncemail, email : 1: : :rdn: :person: cn=+truncemail,