Configuring Users and Groups portlet

When assigning a member to a group, the default behavior of the portlet is to search for all members in the group before it returns. When a group contains tens of thousands of users, not only does it take a long time, but often the search times out before completion. Solution When working with groups that have a very large number of users and using the default configuration of the Manage Users and Groups portlet, there are some operations which become prohibitively expensive from a performance viewpoint: 1. When a group is selected, the portlet's default behavior is to show all members of the group. This is time-consuming for groups with thousands of members. You can modify this behavior to show a blank page by specifying "no" for the showAllGroupMembers configuration parameter in the portlet. This will force the administrator to do a search for the desired member(s). You can re-establish the portlets behavior by specifying "yes" for showAllGroupMembers. 2. When the administrator clicks the "Add Member" button to add a member to a group, the default behavior of the portlet is to show all users and groups that are not already members of the current group. This can be time consuming when the portal has thousands of users. You can modify this behavior to show a blank page when adding members to a group by specifying "no" for the showAllAddMembers configuration parameter in the portlet. This will force the administrator to do a search to show the desired members to add to the group. You can re-establish the portlet's default behavior by specifying "yes" for showAllAddMembers. 3. Even when the showAllAddMembers configuration parameter is set to "no", the default behavior of the portlet is to filter out any members who are already a member of the currently selected group from the results. This prevents an administrator from attempting to add a member to a group that is already a member of the group. This can be time consuming since the group must be searched for each member to determine if that result is already a member of the group. You can prevent this filtering, and thereby improve performance, by specifying "no" for the filterGroupMembersInAddMembers configuration parameter in the portlet. Note that when "no" is specified and there is an attempt to add a member who is already a member of the group, an error message will be displayed by the portlet. You can re-establish the portlets behavior by specifying "yes" for filterGroupMembersInAddMembers. You can modify these configuration parameters by navigating to Administration > Portlet Management > Portlets. Find portlet "Manage Users and Groups", and then click "Configure portlet" (the wrench icon). Once you have modified the desired parameters, click the Save button. Your modifications will take immediate effect.

Cross Reference information

Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal z/OS 5.1.0.3, 5.1.0.2, 5.1.0.1, 5.1.0 Enable Organizational Productivity- Portals & Collaboration WebSphere Portal Operation AIX, HP-UX, i5/OS, Linux, Solaris, Windows 5.1.0.4, 5.1.0.3, 5.1.0.2, 5.1.0.1, 5.1.0 Enable, Extend