Cisco Cisco Unified MeetingPlace Directory Services Manuale Di Manutenzione
Chapter 5 Managing MeetingPlace Directory Services 51
Latitude Communications MeetingPlace Directory Services System Manager’s Guide
When you create the initial MetaLink agreement between the
MeetingPlace master server and the MeetingPlace Directory
Services master server, you use the meetingplace.cfg file, which
has most of the parameters needed to enable this agreement
already mapped for you. Since this agreement requires little
modification, you should use the MeetingPlace Directory
Services Admin Tool to configure the agreement. This agreement
should be configured and run before creating any additional
agreements.
MeetingPlace master server and the MeetingPlace Directory
Services master server, you use the meetingplace.cfg file, which
has most of the parameters needed to enable this agreement
already mapped for you. Since this agreement requires little
modification, you should use the MeetingPlace Directory
Services Admin Tool to configure the agreement. This agreement
should be configured and run before creating any additional
agreements.
Once this MetaLink agreement runs and the profiles are imported
into the MeetingPlace Directory Services master server, you must
create an agreement between the MeetingPlace Directory
Services slave server and the MeetingPlace slave server.
into the MeetingPlace Directory Services master server, you must
create an agreement between the MeetingPlace Directory
Services slave server and the MeetingPlace slave server.
Next, an export (one-way) MetaLink is run from the
MeetingPlace Directory Services master to slave server(s), and
then deleted when the synchronization process has completed.
MeetingPlace Directory Services master to slave server(s), and
then deleted when the synchronization process has completed.
Once the export (one-way) Metalink is deleted, a Changelog
agreement is added to the MeetingPlace Directory Services slave
server. This enables the master server to pick up any updates that
take place on the slave server.
agreement is added to the MeetingPlace Directory Services slave
server. This enables the master server to pick up any updates that
take place on the slave server.
Finally, a two-way MetaLink synchronization agreement is added
to the MeetingPlace Directory Services master server so the slave
server(s) can be replicated with the master.
to the MeetingPlace Directory Services master server so the slave
server(s) can be replicated with the master.
Once these MetaLink agreements have run and the profiles are
imported into the appropriate MeetingPlace Directory Services
server, you must create an agreement between the MeetingPlace
Directory Services master server and your corporate directory
server.
imported into the appropriate MeetingPlace Directory Services
server, you must create an agreement between the MeetingPlace
Directory Services master server and your corporate directory
server.
If your corporate directory server has less than 50,000 entries,
you should use the MeetingPlace Directory Services Admin Tool.
If your corporate directory server has more than 50,000 entries,
you should modify the configuration file manually to configure
the MetaLink agreement.
you should use the MeetingPlace Directory Services Admin Tool.
If your corporate directory server has more than 50,000 entries,
you should modify the configuration file manually to configure
the MetaLink agreement.
Currently, MeetingPlace Directory Services provides default
configuration files for both Netscape LDAP and Microsoft Active
Directory servers. These default configuration files provide some
configuration files for both Netscape LDAP and Microsoft Active
Directory servers. These default configuration files provide some