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-26 shows a sample of a native ALL-IN-1 format LDIF directory file; this is the form of file extracted from ALL-IN-1 using a
PMDF DIRSYNC/CONVERT A1 LDIF=ldif-file-spec/OPTION=option-file-speccommand, or ready to be imported into ALL-IN-1 using a
PMDF DIRSYNC/CONVERT LDIF=ldif-file-spec A1/OPTION= option-file-speccommand. It is the form of file which
cook_a1.rcp would
work upon, to cook the native format ALL-IN-1 directory information
into canonical LDIF form. It is also the form of file which
serve_a1.rcp would create, working upon a canonical LDIF
file and producing a file of this form as output.
Example 36-26 Sample native format ALL-IN-1 directory file
user: JEFF template: USER direct: BRESTLA:[ALLIN1_USERS.JEFF.A1] vmsusr: JEFF surname1: Allison forename1: Jeff initials1: W fulnam: Jeff Allison company: Acme, Inc. depart: Support and Services location: Galactic HQ int_location: Over in the corner phone: 1 626 555 1212 internal_phone: 2 addr1: 1 Acme Drive addr2: Acme City addr3: CA country_name: NZ zipcod: 99999 maides: ALL-IN-1 mail_menu: EMC start: MAIN language: ENGLISH rfc822addr: JEFF@a1.acme.com
Example 36-27 shows an LDIF representation of MS Exchange directory
entries, in native MS Exchange attribute form. It is the form of file
which cook_exchange.rcp would work upon, to cook the
native format MS Exchange directory file into canonical LDIF form. It
is also the form of file which serve_exchange.rcp would
create, working upon a canonical LDIF file and producing a file of this
form as output.
Example 36-27 Sample native MS Exchange directory file
DN: cn=PortiaS,cn=Recipients,ou=ACME-HQ,o=Acme objectClass: organizationalPerson objectClass: person objectClass: Top cn: Portia Shao mail: PortiaS@hosta.acme.com otherMailbox: MS$ACMEIN/ACMEHQ/PORTIAS uid: PortiaS MAPI-Recipient: TRUE sn: Shao DN: cn=Mike,cn=Recipients,ou=ACME-HQ,o=Acme objectClass: organizationalPerson objectClass: person objectClass: Top cn: Mike de Laine mail: Mike@acme.com uid: Mike MAPI-Recipient: TRUE sn: de Laine
Example 36-28 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-28 Sample IDDS LDAP directory LDIF file
DN: ou=development, o=Acme, c=NZ objectClass: top objectClass: organizationalUnit objectClass: pilotObject objectClass: quipuObject objectClass: quipuNonLeafObject ou: Development description: The Acme development team userPassword: xxxxxx lastModifiedTime: 980601080604Z lastModifiedBy: cn=Manager, o=Acme, c=NZ 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 telephoneNumber: +1 626 555 1212 facsimileTelephoneNumber: +1 626.555.1212 seeAlso: cn=Mrochek, ou=Pets, o=Acme, c=NZ seeAlso: cn=Beckett, ou=Pets, o=Acme, c=NZ userPassword: yyyyyy uid: ned mail: Ned.Freed@acme.com otherMailbox: internet $ ned@acme.com lastModifiedTime: 980316144818Z lastModifiedBy: cn=Manager, o=Acme, c=NZ 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@a1.innosoft.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@msx.acme.com