Cisco Cisco Unified MeetingPlace Directory Services Manuale Di Manutenzione

Pagina di 144
Chapter 5  Managing MeetingPlace Directory Services 49
Latitude Communications  MeetingPlace Directory Services System Manager’s Guide
last 4 digits of a user’s phone number and assign its value to the 
MeetingPlace extension attribute. The attribute mapping for this 
task might appear as:
ExtensionNumber = &StringRight(Phone Number, "-") 
This example states that the extension number attribute of the 
MeetingPlace profile will be synchronized with the value of the 
characters after the first occurrence of the "-", from the right, of 
the phone number attribute. So, if an entry on your corporate 
directory has a ’770-649-1865’ phone number value, ’1865’ will 
become the MeetingPlace profile extension number value. Of 
course, the MetaLink agreement, which should include other 
meaningful attribute mappings to ensure the correct entries are 
synchronized, must be run before synchronization will occur.
To use a plug-in function, it must be registered in the 
configuration file. The standard syntax for registering a plug-in 
function is Plug-InFunction = Library, EntryPoint, [OptPar]
where
Plug-InFunction is the name of the plug-in function
Library is the name of the shared library that contains the 
function
EntryPoint is the name of the entry point to the function in 
the shared library
OptPar is the optional parameter, a literal string, that will be 
passed to the function each time it is called
Chapter 6 details the process of registering and using plug-in 
functions. For a list of plug-in functions and their optional and 
required parameters, entry points, and libraries, see Appendix B.