The Directory Search or "People Picker" portlet is a common embedded component that allows users to search for and select names of people (individual users) and groups for which the portal is configured. Using a search string that contains a space may result in multiple wild card characters being used for the query to the federated repository. In some cases, you may receive an error being unable to find any valid user or group.
The SystemOut and trace logs reveal the following error:
[datetime] 000000d0 exception W com.ibm.ws.wim.adapter.file.was.FileXPathHelper countWildcardAndValidatePattern
com.ibm.websphere.wim.exception.InvalidArgumentException: CWWIM4534E The 'My*Group*Search*' search pattern is not valid.
Where 'My Group Search' is the search string used with Directory Search. You may encounter a pop-up in Directory Search stating:
Too many names were found. Type more characters of the name, then search again.
The Virtual Member Manager (VMM) file-based repository does not support search queries with multiple wild card characters. After adding another repository and choosing the administrative users from that repository, it is recommended to remove the file repository. For more information, refer to the section User registry considerations in the WebSphere Portal knowledge center.
Diagnosing the problem
Enable the following VMM traces, recreate the problem and check the resulting trace logs for the above message.
Resolving the problem
In this case, Portal was configured using a federated repository that included an LDAP and the built-in file repository. Search queries with multiple wild card characters are directed to both the LDAP and the file repository where the above exception occurs.
Remove the built-in file repository - defaultWIMFileBasedRealm. Using LDAP only should resolve the issue.
APAR PM94677 was introduced in CF08 for Portal 220.127.116.11 and is already included in the base Portal 8.5 code. This APAR introduces the option to disable the wild card character (*) from automatically being appended to the search string. Setting pickerWildCardSearchEnable to false in WP PeopleService will disable the function. An administrator could still manually append the wild card character to the search string. For more information, refer to the section Configuring the wildcard support in directory search queries in the WebSphere Portal knowledge center.
|Organizational Productivity- Portals & Collaboration||WebSphere Portal End of Support Products||AIX, HP-UX, Linux, Solaris, Windows, z/OS, IBM i||6.1|