PMDF System Manager's Guide

This section shows simplified samples of the sort of data that PMDF-DIRSYNC might encounter at the sample EXAMPLE.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 can be helpful when thinking about recipe files.

Example 37-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 37-44 Sample Native cc:Mail Directory File

cn: Dickens, Charles sn: Dickens mail: "Charles Dickens%cc"@example.com description: DWM cn: Johnson, Peter sn: Johnson mail: "Peter Johnson%pmdf"@example.com description: a Notes user cn: Jones, Ned sn: Jones mail: "Ned Jones%pmdf"@example.com description: an SMTP user

Example 37-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 37-45 Sample Native Lotus Notes Directory File

FullName: CN=Ned Jones/O=Development LastName: Jones Form: Person Type: Person description: an SMTP user MailAddress: ned@example.com MailDomain: PMDF $UpdatedBy: CN=korova/O=example FullName: CN=peter johnson/O=example FullName: peter johnson ShortName: pjohnson Owner: CN=peter johnson/O=example 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: example description: a notes user LastName: johnson MailServer: CN=korova/O=example MailFile: mail\pjohnson $UpdatedBy: CN=korova/O=example FullName: CN=Charles Dickens/O=cc LastName: Dickens Form: Person Type: Person description: a cc user MailAddress: charles.dickens@example.com MailDomain: PMDF $UpdatedBy: CN=korova/O=example

Example 37-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 37-46 Sample IDDS LDAP Directory LDIF File

DN: ou=development, o=Example, c=NZ objectClass: top objectClass: organizationalUnit objectClass: pilotObject objectClass: quipuObject objectClass: quipuNonLeafObject description: The Example development team DN: cn=Bob Smith, ou=Development, o=Example, c=NZ objectClass: top objectClass: person objectClass: organizationalPerson objectClass: pilotObject objectClass: newPilotPerson objectClass: pmdfPerson objectClass: quipuObject cn: Bob Smith cn: Smith, Bob cn: Robert E Smith sn: smith uid: bob mail: Bob.Smith@example.com DN: cn=Peter Johnson, ou=Notes, o=Example, c=NZ objectClass: top objectClass: person objectClass: organizationalPerson objectClass: pilotObject objectClass: newPilotPerson objectClass: pmdfPerson objectClass: quipuObject cn: Peter Johnson sn: Johnson uid: pjohnson mail: peter.johnson@notes.example.com DN: cn=Charles Dickens, ou=cc, o=Example, c=NZ objectClass: top objectClass: person objectClass: organizationalPerson objectClass: pilotObject objectClass: newPilotPerson objectClass: pmdfPerson objectClass: quipuObject cn: Charles Dickens sn: Dickens mail: Charles.Dickens@cc.example.com