Configuring settings for nested groups in policy assignments

You can configure whether or not IBM® Sametime® considers nested groups when it applies policies and how many levels deep that Sametime searches for the highest weighted group.

About this task

For authenticated users, Sametime searches for an exact ID match, and then applies the highest weighted policy. If there is no match for the user ID in any policy, then Sametime applies the highest weighted group match to which the user belongs. By default, Sametime searches through four levels of nested groups when determining the highest weighted policy. If a policy is assigned to a group nested more than the current nesting depth limit, then the default policy is assigned. If a group inherits a higher-level policy and is also assigned a policy directly, the directly assigned policy takes precedence over the inherited policy regardless of either policy's weight.

Note: Maximum Nested Group Depth applies only on System Console and Meeting Server policy searches. To change the maximum nested group depth of the Community Server, edit the DIR_SEARCH_LEVEL_LIMIT parameter of the Sametime Community Server sametime.ini file.

Procedure

  1. On the Sametime System Console, log in to the WebSphere® Integrated Solutions Console as the WebSphere administrator.
  2. In the navigation tree, click Sametime System Console > Manage Policies.
  3. In the Manage Policies pane, click the Edit Policy Settings button.
  4. In the Policy Assignment Settings section, enter a numerical value between -1 and 10 in the Maximum Nested Group Depth field. The default value is 4 levels.
    Note that entering a large number as the maximum nested group depth can have an impact on performance.
    Note: To change the maximum nested group depth of the Community Server, edit the DIR_SEARCH_LEVEL_LIMIT parameter of the Sametime Community Server sametime.ini file.
  5. Enter a number in minutes in the Group Membership Cache Timeout field. The default value is 30 minutes.
  6. In the Policy Settings section, enter a number in minutes in the Policy Cache Timeout field. The default value is 30 minutes.
  7. Click Apply.
  8. Restart the Meeting and Community Servers for changes to take effect.