Table of Contents

Search

  1. Preface
  2. Understanding PowerExchange for LDAP
  3. PowerExchange for LDAP Configuration
  4. LDAP Sources and Targets
  5. LDAP Mappings
  6. LDAP Sessions
  7. Appendix A: LDAP Datatype Reference
  8. Appendix B: Error Messages
  9. Appendix C: Glossary

PowerExchange for LDAP User Guide for PowerCenter

PowerExchange for LDAP User Guide for PowerCenter

Generating Key Values

Generating Key Values

When you import a multi-group LDAP source definition, the Designer creates a key relationship between each child group in the source definition and the parent group. Each key uses the following naming convention:
GPK__<group_name>
GFK__<parentgroup_name>__<group_name>
The following table describes the key naming conventions:
Key Name Component
Description
GPK|GFK
Type of key. A group primary key name begins with GPK. A group foreign key name begins with GFK.
group_name
Name of the group to which the key belongs.
parentgroup_name
Name of the parent group with which you have established a primary key relationship.
In the multi-valued group, the Designer generates a primary key GPK__Parent_Group for the parent group. The Designer generates GFK__Parent_Group__objectClass and GFK__Parent_Group__mail foreign keys for the child groups. The PowerCenter Integration Service generates the values for the update strategy.
The following table shows the sample rows in the Parent_Group parent group from the source:
GPK__Parent_Group
displayName
employeeNumber
1
Sam Carter
4576
2
Ted Morris
6712
The following table shows the sample rows in the objectClass child group:
GFK__ Parent_Group__objectClass
objectClass
1
top
1
person
1
organizationalPerson
1
inetOrgPerson
2
top
2
person
2
organizationalPerson
2
inetOrgPerson
The following table shows the sample rows in the mail child group from the source:
GFK__Parent_Group__mail
mail
1
scarter@airius.com
1
samcarter@gmail.com
2
tmorris@airius.com
2
ted@gmail.com
2
tedmorris@rediffmail.com
To maintain key relationships when you connect mapping objects, connect source columns to the corresponding groups into the target definitions.
When you create mappings with the primary key-foreign key relationship, the Designer might not create the relationship for the tables. You need to manually set the primary key relationship in the foreign key table.
The following table lists the column relationships between the groups in the multi-valued source definition and the target definitions:
Source Group Name
Source Column Name
Target Name
Target Column Name
Parent_Group
GPK__Parent_Group
single3
GPK_Parent_Group
Parent_Group
dn
single3
dn
Parent_Group
employeeNumber
single3
employeeNumber
Parent_Group
displayName
single3
displayName
objectClass
GFK__Parent_Group__objectClass
single11
GFK_Parent_objectClass
objectClass
objectClass
single11
objectClass
mail
GFK__Parent_Group__mail
single21
GFK_Parent_mail
mail
mail
single21
mail
The PowerCenter Integration Service extracts the following rows from the source definition:
[Parent (“Sam Carter”, “4576”), objectClass (top, person, organizationalPerson, inetOrgPerson), mail (scarter@airius.com, samcarter@gmail.com)] [Parent (“Ted Morris”, “6712”), objectClass (top, person, organizationalPerson, inetOrgPerson), mail (tmorris@airius.com, ted@gmail.com, tedmorris@rediffmail.com)]
The PowerCenter Integration Service fails the session if you change the order of the groups or columns in the source definition.

0 COMMENTS

We’d like to hear from you!