Download IBM Tealeaf CX: Configuration Manual

Examining the Search Server logs generally identifies the problem. When Search
Server restarts with authorization enabled, the list of defined users accessible to it
are inserted into the log.
v Search Server is typically restarted at 1AM. At restart time, the Search Server log
also lists OperatingParams, which indicate the authorization mode and other
operating parameters.
v If you know the time that saving events failed, you can examine the slave server
log at that time for the /NTYP command from Search Server to identify the user
name it's using and then compare that ID to the user list from the last restart.
Data Segmentation
Data segmentation restricts the search data returned for a given user based on
authentication group using Tealeaf events that you create.
Events that are configured for data segmentation are used to filter live sessions so
that active sessions appearing in the Portal are visible only to users who have
access to them. In addition, you can specify which events are visible to members of
specified groups; users cannot see sessions from other groups, and active events
appearing in the Portal pertaining to the other groups' sessions are hidden, too.
Note: To use data segmentation, your Tealeaf system must be configured to use
Portal or NT authentication and authentication groups.
For every submitted search, the term is ANDed with a restricting term defined for
the user's authentication group. The second search term that is appended to the
user's search term is an event configured to fire on a specific type of session.
Data segmentation example 1: For example, suppose your enterprise supports
two web sites, www.example1.com and www.example2.com. There are separate
customer service groups to monitor each website, and neither group is supposed to
see the session data from the other site.
To enable data segmentation, two separate events must be defined. One event fires
when the request or response pertains to www.example1.com, while the other
responds to www.example2.com data. The first event is assigned unique identifier 17,
and the second received unique ID 18.
To enable data segmentation of these two websites:
v Through Search Server configuration, authentication is enabled.
v Two user groups are created: Example1group and Example2group.
v The appropriate users are added to each group.
v Through the Search Server configuration:
1. Example1group is configured to use the following filter string:
(canisterappevent/uniqueid contains 17)
2. Example2group is configured to use the following filter string:
(canisterappevent/uniqueid contains 18)
v When members of the Example1group do searches, they cannot see sessions from
www.example2.com sessions. When Example2group members execute searches, they
cannot www.example1.com sessions.
Each group added in Search Config can have multiple events associated with it.
These events can be combined using the Boolean operators AND or OR.
128
IBM Tealeaf CX: Configuration Manual