This section shows simplified samples of the sort of data that PMDF-DIRSYNC might encounter at the sample ACME.COM site, in the LDIF file format that PMDF-DIRSYNC uses for transporting directory information. Such files are not themselves part of the PMDF-DIRSYNC configuration, but rather are samples of the data that PMDF-DIRSYNC would receive, operate upon, and use to convey directory updates. In particular, these concrete examples may be helpful when thinking about recipe files.
Example 36-44 shows a sample of a native cc:Mail directory file; this
is the form of file extracted from cc:Mail or ready to be imported into
cc:Mail. It is the form of file which cook_cc.rcp would
work upon, to cook the native cc:Mail directory file into canonical
LDIF form. It is also the form of file which serve_cc.rcp
would create, working upon a canonical LDIF file and producing a file
of this form as output.
Example 36-44 Sample native cc:Mail directory file
cn: Dickens, Charles sn: Dickens mail: "Charles Dickens%cc"@acme.com description: DWM cn: Coates, Peter sn: Coates mail: "Peter Coates%pmdf"@acme.com description: a Notes user cn: Freed, Ned sn: Freed mail: "Ned Freed%pmdf"@acme.com description: an SMTP user
Example 36-45 shows a native Lotus Notes directory file. It is the
form of file which cook_notes.rcp would work upon, to cook
the native Lotus Notes directory file into canonical LDIF form. It is
also the form of file which serve_notes.rcp would create,
working upon a canonical LDIF file and producing a file of this form as
output.
Example 36-45 Sample native Lotus Notes directory file
FullName: CN=Ned Freed/O=Development LastName: Freed Form: Person Type: Person description: an SMTP user MailAddress: ned@acme.com MailDomain: PMDF $UpdatedBy: CN=korova/O=acme FullName: CN=peter coates/O=acme FullName: peter coates ShortName: pcoates Owner: CN=peter coates/O=acme Form: Person Type: Person MailSystem: 1 ClientType: 0 EncryptIncomingMail: 0 CheckPassword: 0 AvailableForDirSync: 1 PasswordChangeInterval: 0.000000e+000 PasswordGracePeriod: 0.000000e+000 DocumentAccess: [UserModifier] FirstName: peter MailDomain: acme description: a notes user LastName: coates MailServer: CN=korova/O=acme MailFile: mail\pcoates $UpdatedBy: CN=korova/O=acme FullName: CN=Charles Dickens/O=cc LastName: Dickens Form: Person Type: Person description: a cc user MailAddress: charles.dickens@acme.com MailDomain: PMDF $UpdatedBy: CN=korova/O=acme
Example 36-46 shows an LDIF representation of IDDS LDAP data. It is
the form of file which cook_idds.rcp would work upon, to
cook the LDAP directory information into canonical LDIF form (which is
the same as LDAP LDIF form). It is also the form of file which
serve_idds.rcp would create, working upon a canonical LDIF
file and producing a file of this form as output.
Example 36-46 Sample IDDS LDAP directory LDIF file
DN: ou=development, o=Acme, c=NZ objectClass: top objectClass: organizationalUnit objectClass: pilotObject objectClass: quipuObject objectClass: quipuNonLeafObject description: The Acme development team DN: cn=Ned Freed, ou=Development, o=Acme, c=NZ objectClass: top objectClass: person objectClass: organizationalPerson objectClass: pilotObject objectClass: newPilotPerson objectClass: pmdfPerson objectClass: quipuObject cn: Ned Freed cn: Freed, Ned cn: Edwin E Freed sn: Freed uid: ned mail: Ned.Freed@acme.com DN: cn=Peter Coates, ou=Notes, o=Acme, c=NZ objectClass: top objectClass: person objectClass: organizationalPerson objectClass: pilotObject objectClass: newPilotPerson objectClass: pmdfPerson objectClass: quipuObject cn: Peter Coates sn: Coates uid: pcoates mail: peter.coates@notes.acme.com DN: cn=Charles Dickens, ou=cc, o=Acme, c=NZ objectClass: top objectClass: person objectClass: organizationalPerson objectClass: pilotObject objectClass: newPilotPerson objectClass: pmdfPerson objectClass: quipuObject cn: Charles Dickins sn: Dickins mail: Charles.Dickens@cc.acme.com