Configuring restriction filters

You can use restriction filters to control the rows in ObjectServer tables that users are allowed to view and modify. Restriction filters apply to Tivoli Netcool/OMNIbus client applications and INSERT, UPDATE, and DELETE statements. You can assign restrictions filters to individual users or to a collection of users in a group.

You can assign only one restriction filter per table to a user or a group. However, multiple restriction filters can apply to a user. For example, a user can be assigned a single restriction filter and can also be a member of one or more groups, to which restriction filters are applied. So, if a user is a member of three groups to which restriction filters are assigned, and the user is also assigned a restriction filter, four restriction filters apply to that user. If multiple restriction filters apply to a user, the resulting data is a combination of all applicable restriction filters for the user or group

If you are using multiple restriction filters, make sure that you set the ObjectServer RestrictionFiltersAND property appropriately.

You create a restriction filter against the alerts.status table that has the following condition:

Tally > 100 AND Severity > 4

After this restriction filter is applied to a user, the user can see only events that occurred more than 100 times and that have a severity that is greater than 4.

Another example usage of restriction filters is to limit the geographical coverage for events that users can view. You can create a restriction filter against the alerts.status table that permits London-based users to view only events from operations centers in London.