Cisco Cisco Unified MeetingPlace Directory Services Maintenance Manual
42
Chapter 5 Managing MeetingPlace Directory Services
MeetingPlace Directory Services System Manager’s Guide Latitude Communications
MeetingPlace Profiles
A MeetingPlace profile, which uniquely identifies each
MeetingPlace user, can be made up of several attributes.
Minimally, a MeetingPlace profile consists of a case-sensitive
user name and profile number.
MeetingPlace user, can be made up of several attributes.
Minimally, a MeetingPlace profile consists of a case-sensitive
user name and profile number.
Once you run the initial MetaLink agreement between the
MeetingPlace Directory Services server and the MeetingPlace
server, and you have linked to your corporate directory server,
any changes made to directory information that involve the
mapped attributes should be made on your corporate directory
server only. If you make a change to a profile in MeetingPlace
afterward, the change will be overwritten by the information on
your corporate directory server if there is a change to the entry in
your corporate directory.
MeetingPlace Directory Services server and the MeetingPlace
server, and you have linked to your corporate directory server,
any changes made to directory information that involve the
mapped attributes should be made on your corporate directory
server only. If you make a change to a profile in MeetingPlace
afterward, the change will be overwritten by the information on
your corporate directory server if there is a change to the entry in
your corporate directory.
Mapping an Attribute
In a MetaLink agreement, entries can be synchronized using
either BootStrap or standard attribute mapping. The type of
attribute mapping, as well as which attributes to map, is
determined by you when you create the MetaLink agreement.
Provided there are no errors, the attributes are mapped once the
MetaLink agreement is run. If an error does occur, it will be
written to the suspense file.
either BootStrap or standard attribute mapping. The type of
attribute mapping, as well as which attributes to map, is
determined by you when you create the MetaLink agreement.
Provided there are no errors, the attributes are mapped once the
MetaLink agreement is run. If an error does occur, it will be
written to the suspense file.
Note: The case-sensitive nature of the user name attribute can
have an effect on the MetaLink agreement between the
MeetingPlace Directory Services server(s) and the MeetingPlace
server(s). If profiles exist in both upper case and lower case on
the MeetingPlace server, only the first profile detected will be
propagated when the MetaLink agreement is run.
have an effect on the MetaLink agreement between the
MeetingPlace Directory Services server(s) and the MeetingPlace
server(s). If profiles exist in both upper case and lower case on
the MeetingPlace server, only the first profile detected will be
propagated when the MetaLink agreement is run.
For example, if "dsmith" and "DSmith" exist on the MeetingPlace
server, in that order, the lower case profile will be detected first
and propagated to MeetingPlace Directory Services. The user
will have to access MeetingPlace using the lower case user name.
The "DSmith" entry, when detected by MeetingPlace Directory
Services, will cause an error and be written to the suspense file.
server, in that order, the lower case profile will be detected first
and propagated to MeetingPlace Directory Services. The user
will have to access MeetingPlace using the lower case user name.
The "DSmith" entry, when detected by MeetingPlace Directory
Services, will cause an error and be written to the suspense file.