8-54 Application Administrators Guide for Content Server
2. Click the Services tab.
3.
Select the desired service entry from the Service Name list.
4. Click Edit.
The Extended Service Tracking screen is displayed and the fields are populated with the selected service entrys values. In this case, the Service Name field is
deactivated. If necessary, you can also edit the other field values for this service entry in addition to editing the field map ResultSet.
5.
To edit the Field Map ResultSet, you can either:
■
Add one or more data field, location, and table column sets. Refer to the procedure for
Adding Field Map ResultSets and Linking Them to Service Entries
on page 8-52.
■
Delete one or more data field, location, and table column sets as follows:
■
Select the field, location, and table column set to be deleted.
■
Click Delete
1. Click OK.
A confirmation dialog box is displayed.
2. Click OK.
The Extended Service Tracking screen closes and the Services tab on the Data Engine Control Center is displayed. The services state and Content Trackers
SctServiceFilter.hda file are updated.
Content Tracker does not perform error checking such as field type or spelling verification for the extended services tracking function in the Data Engine Control
Center. Errors are not generated until you perform a reduction. These fields are case-sensitive. Therefore, if you are editing field map ResultSets by adding one or
more data field, location, and table column sets, be careful to enter the proper data field names, location names, and SctAccessLog table column names. Ensure that
all field values are spelled and capitalized correctly.
To verify the modified values of the data field, location, and table column sets in field map ResultSets, you can access the Content Trackers SctServiceFilter.hda file
in the following directory:
cs_rootdatacontenttrackerconfigSctServiceFilter.hda Optionally, you can manually modify the values of the data field, location, and
table column sets in field map ResultSets. For more detailed information about field map ResultSets in the SctServiceFilter.hda file and how to manually edit
them, see About the Service Call Configuration File
on page 8-75 and Manually
Editing the SctServiceFilter.hda File on page 8-82, respectively.
8.4.5.16 Deleting Service Entries
To delete a service:
1. Open the Data Engine Control Center, see
Accessing the Data Engine Control Center
on page 8-43.
2. Click the Services tab.
3.
In the Services list, select the service entry that you want to delete.
4. Click Delete.
Managing Content Tracker 8-55
You are asked to verify your request to delete service logging for this service entry.
5. Click Yes.
The selected service entry is deleted from the Services list and removed from the SctServiceFilter.hda file.
To verify that the service entry has been deleted, you can access the Content Trackers SctServiceFilter.hda file in the following directory:
cs_rootdatacontenttrackerconfigSctServiceFilter.hda Optionally, you can manually delete specific service entries. For more information,
see Manually Editing the SctServiceFilter.hda File
on page 8-82.
8.4.5.17 Deleting Field Map ResultSets
To delete a field map ResultSet:
1. Open the Data Engine Control Center, see
Accessing the Data Engine Control Center
on page 8-43.
2. Click the Services tab.
3. In the Services list, select the service entry that is linked to the field map ResultSet
that you want to delete.
4. Click Edit.
The Extended Service Tracking screen is displayed and the fields are populated with the selected service entrys values.
5. Remove the field map ResultSet name from the Field Map field.
6. Select a data field, location, and table column set and click Delete.
The data field, location, and table column set is removed from the list. Repeat this step for each data field, location, and table column set as necessary.
7. Click OK.
The field map ResultSet is removed from the SctServiceFilter.hda file. It is no longer linked to the service entry.
To verify that the field map ResultSet has been deleted, you can access the Content Trackers SctServiceFilter.hda file in the following directory:
cs_rootdatacontenttrackerconfigSctServiceFilter.hda Optionally, you can manually delete field map ResultSets. For more information,
see Manually Editing the SctServiceFilter.hda File
on page 8-82.
8.4.5.18 AddingEditing Web Beacon Object Names to the Web Beacon ID List
To set or edit the preference setting for the list of web beacon objects:
1.
Log in to Content Server as an administrator.
2. Select Admin Server from the Administration menu.
The Content Admin Server page is displayed.
3.
Click the name of the Content Server instance whose web beacon preference setting will be changed.
The Content Admin Server instance_name page is displayed.
8-56 Application Administrators Guide for Content Server
4. Click Component Manager.
The Component Manager page is displayed.
5. In the Update Component configuration field, select Content Tracker from the list.
6. Click Update.
The Update Component Configuration page is displayed.
7.
In the SctWebBeaconIDList preference field, enter the applicable web beacon object dDocNames separated by commas.
8. Click Update.
9.
Restart Content Server to apply the changes.
8.5 Report Generation
Content Tracker Reports uses the captured and reduced data to generate reports that outline the usage history of particular pieces of content. You can use the pre-defined
reports that are provided or create custom queries for the information to be tracked. Optionally, you can use any external commercial reporting tool. See
External Report Generator
on page 8-61.
Reports can be derived from a variety of criteria, including specific users, groups of users, and any set of content that can be defined by a query or group of metadata
values. Based on the variables in the system such as number of users, amount of content, metadata count, etc., Content Tracker Reports enables hundreds of key
metrics to be included in reports. Specialized reports enable you to understand and disclose which content is most relevant to users.
This section covers the following topics:
■
Oracle and DB2 Case Sensitivity on page 8-57
■
Access Control Lists and Content Tracker Reports Secure Mode on page 8-57
■
Pre-Defined Reports on page 8-58
Note: By default, Content Tracker is configured for maximum
performance using several optimization functions see Performance
Optimization Functions on page 8-1. As such, Content Tracker
collects and records only content access event data. This excludes information gathering on non-content access events like searches as
well as the collection and synthesis of user profile summaries.
Because non-content event data is not gathered, various pre-defined report options are not displayed on the Content Tracker Report
Generator main page. However, all of the pre-defined report options can be available if you reconfigure Content Tracker. This is done by
changing the settings of the optimization functions see
Changing the Variable Settings for the Performance Optimization Functions
on page 8-42.
Note: The user reports are only visible if the Content Access Only
operating mode is disabled. See Performance Optimization
Functions on page 8-1.
