People Finder
The People Finder portlet provides both quick search and advanced search options for locating people and information about people. Once found, a person is visible to other users as a person link that indicates online presence and displays a menu of instant messaging and other options.
Clicking a person link in People Finder displays the Person Record, including the person's business card information followed by administrator-defined fields organized in sections, for example, Contact Information, Current Job, and Background. The portlet also provides a view of the person's place in the organizational context. In the Organization View, users can display the person's reporting structure: that is, the employees the person manages, if any, and the person's management chain.
The People Finder portlet appears in the People palette, so that users can find people in any context.
Sametime Contact List portlet in the portal site, consider adding it to the People palette, making it a central location for awareness and collaboration. People Finder is supported as a remote WSRP service.
What's new
In this release, People Finder supports the Java Portlet Specification. For more information on this specification, see Standard portlet API.
Use the People Finder portlet
Users interact with the People Finder portlet through the following features, which appear in one or more views of the portlet:
- Quick Search and Quick Search Results, including Business Card fields
- Advanced Search and Advanced Search Results
- Person record, including Business Card fields
- Organization view, including Business Card fields
Test assumptions
The People Finder portlet has been tested on and is compatible with all supported WebSphere Portal platforms, as listed in Supported hardware and software.
Set up People Finder
Using the portlet's configuration mode, administrators can specify the fields that they want to appear in the People Finder portlet. The fields that are available for selection when configuring the portlet are based on the Member Manager schema. The defined People Finder fields then become available for selection in the remaining portlet configuration tasks, by which the administrator or designer specifies the content and format of the People Finder views.
For People Finder, make sure the portal environment meets the following client and server requirements.
Client requirements
This portlet supports browsers capable of rendering HTML markup. The following table provides detailed information.
Minimum requirements for HTML Markup level HTML 4.01 Transitional Java applet n/a JavaScript n/a <iframe> No Style sheets Portal styles only Software The People Finder portlet is compatible with the specific Web browser software releases listed in the Supported Web browsers (required) table under Software requirements in Supported hardware and software. Accessibility Yes
Server requirements
There are no special server requirements for the People Finder portlet.
Deployment/Installation
This portlet is installed automatically as part of WebSphere Portal installation.
National language support for People Finder fields
All fields of the People Finder portlet must have associated language strings defined in each language property file, PeopleFinderUI_language_code.properties. The field names are the names of the corresponding attributes in Member Manager.
For each People Finder field, three strings are required:
- One string for the field's name, which is the attribute name
- One string for the field's long name
- One string for the field's description as it appears in the tasks of People Finder configuration mode
Example:
displayName = Name displayName_Long = Preferred Name displayName_Desc = Display nameThe resource key for each field refers to the appropriate language property file, /nls/PeopleFinderUI_language_code.properties. Foreign language translations of People Finder fields must be stored in the appropriate language property file.
Language properties files are in the following location on the portal server (nnnnnnn represents a random number generated by the installation process when the lwppeoplefinder.jar file is installed):
portal_server_root /installedApps/peoplefinder/nnnnnnn.ear/lwppeoplefinder.war/web-inf/lib/lwp.peoplefinder.jarFor more information, see Language support.
Configuration parameters
The following configuration parameters are available in this portlet.
Do not modify any configuration parameter values for the People Finder portlet using...
Administration | Portlets | Portlet ManagementUse the portlet's Configure command to configure the People Finder.
Parameter Value ConfigHelpURI The location and name of the JSP containing topics launched from the Help command when configuring People Finder. Default: /help/pfind_config.jsp
SearchHelpURI The location and name of the JSP containing topics launched from the Help command in the Person Record view of the People Finder. Topics in this JSP include Help for person links, Quick Search, Quick Search Results, Advanced Search, and Advanced Search Results. Default: /help/pfind_view_search_for_people.jsp
PersonRecordHelpURI The location and name of the JSP containing topics launched from the Help command in the Person Record and Organization view of the People Finder. Default: /help/pfind_view_display_person_info.jsp
Config_ResultSetLimit Number of search results to be returned by Quick Search and Advanced Search. The value specified for this parameter appears in People Finder configuration mode, Configuration Basics, the Search Results field. Default: 40
Config_RecursionSetLimit Specifies the maximum number of recursions performed by search and retrieval on the manager attribute for a given person. The limit of recursions performed on the manager attribute determines the number of managers above the found person that appear in the Organization View. Config_ActiveFields
Config_Active_Queries
Config_VisualSets
Config_Views
Config_QuerySets
Config_QueryViews
Config_UpdateInfo
Config_CompleteThese parameters appear in the portlet after fields are specified in configuration mode. Do not modify these parameters.
Parent topic:
Planning awareness
Related reference:
Collaborative Services API
Related information
Member Manager