This section presents a sample configuration of PMDF-DIRSYNC on an OpenVMS system. The sample site is assumed to be named ACME.COM, with PMDF-DIRSYNC system COYOTE. The directory synchronization will be between an IDDS (Innosoft LDAP) directory, a Microsoft Exchange LDAP directory, and an ALL-IN-1 directory (ALL-IN-1 PROFILE and NETWORK databases). In this example, the IDDS directory and the ALL-IN-1 are assumed to also be running on the COYOTE system.
Example 36-14 Sampledirsync.rulesfile
for COYOTE system
idds.dirsync.coyote.acme.com $U@$idds.dirsync.coyote.acme.com exchange.dirsync.coyote.acme.com $U@$exchange.dirsync.coyote.acme.com a1.dirsync.coyote.acme.com $U@$a1.dirsync.coyote.acme.com master.dirsync.coyote.acme.com $U@$master.dirsync.coyote.acme.com
Example 36-15 Sampledirsync.chansfile
for COYOTE system
sync_ldap_idds defragment idds.dirsync.coyote.acme.com sync_ldap_exchange defragment exchange.dirsync.coyote.acme.com sync_ldif_a1 defragment a1.dirsync.coyote.acme.com sync_dirbot_local defragment master.dirsync.coyote.acme.com
Example 36-14 and Example 36-15 show rewrite rules and channel definitions that must be included into the PMDF configuration file; (usually this is performed simply by uncommenting the references in the PMDF configuration file to these generated files).
Example 36-16 shows the SYNC_DIRBOT channel option file---effectively the DIRBOT work order, that informs the DIRBOT which directories to synchronize.
Example 36-16
Samplesync_dirbot_local_optionfile
directory_master=fredd.bloggs@acme.com send_bulk_load_to=a1 secret=mindyourownbusiness required_directories=idds,exchange,a1 ! [directory=idds] cook=PMDF_TABLE:cook_idds.rcp|diff diff=serve exclude=MAPI-Recipient serve=PMDF_TABLE:serve_idds.rcp|apply|dirbot@idds.coyote.acme.com ! [directory=exchange] cook=PMDF_TABLE:cook_exchange.rcp|diff diff=serve serve=PMDF_TABLE:serve_exchange.rcp|apply|dirbot@exchange.coyote.acme.com ! [directory=a1] cook=PMDF_TABLE:cook_a1.rcp|diff bulk_load=serve serve=PMDF_TABLE:serve_a1.rcp|apply|dirbot@a1.coyote.acme.com
Each of the individual channels has its own corresponding PMDF-DIRSYNC directory agent, hence its own channel with its own channel option file. The IDDS directory is handled by the SYNC_LDAP_IDDS channel, whose option file is shown in Example 36-17 . The MS Exchange LDAP directory is handled by the SYNC_LDAP_EXCHANGE channel, whose option file is shown in Example 36-18 . The ALL-IN-1 directory is handled by the SYNC_LDIF_A1 channel, whose option file is shown in Example 36-19 .
Example 36-17
Samplesync_ldap_idds_optionfile
directory_master=fred.bloggs@acme.com directory_robot=dirbot@dirsync.coyote.acme.com secret=mindyourounbusiness cookie_file=PMDF_TABLE:idds.cookie dirname=idds ldaphost=coyote.acme.com password=qwertyuiop ldapuser=cn=Manager, o=acme, c=nz root=o=acme, c=nz ldaplimit=8
Example 36-18
Samplesync_ldap_exchange_optionfile
directory_master=fred.bloggs@acme.com directory_robot=dirbot@dirsync.coyote.acme.com secret=mindyourounbusiness cookie_file=PMDF_TABLE:exchange.cookie dirname=exchange ldaphost=gopher.acme.com password=asdfghjkl ldapuser=cn=administrator, cn=recipients, ou=acme, o=acme root=ou=acme, o=acme ldaplimit=8 ldappage=1000 msx=1
Example 36-19
Samplesync_ldif_a1_optionfile
dirname=a1
directory_master=fred.bloggs@acme.com
directory_robot=dirbot@dirbot.coyote.acme.com
secret=mindyourownbusiness
cookie_file=PMDF_DIRSYNC:A1.COOKIE
slave_file=PMDF_DIRSYNC:PROFILE.LDIF
slave_command=pmdf dirsync /convert a1 ldif=pmdf_dirsync:profile.ldif \
/option=pmdf_table:sync_ldif_a1_option
master_command=pmdf dirsync /convert ldif=pmdf_dirsync:a1.ldif \
a1 /option=pmdf_table:sync_ldif_a1_option
A batch job will also be needed, one that runs and resubmits itself at scheduled times to run the directory agents at those desired times.
Each directory will need its own cook and serve recipes, discussed in Section 36.9.1.1 .