# Administrator Guide

# Using Analytics Administration

This chapter provides information on accessing and working with the Analytics Administration console. It includes the following topics:

- Accessing Analytics Administration
- Using Analytics Administration

## Accessing Analytics Administration

To access Analytics Administration:

1. Navigate to WebLogic Portal Administration.
2. Under Configuration & Monitoring, choose Analytics.
   The Analytics application appears.
3. Click the Administration Console tab.

## Using Analytics Administration

This section contains the following topics:

- Configuring Runtime Settings
- Configuring Partition Settings

### Configuring Runtime Settings

The Runtime Settings page lets you configure timeout periods, and choose the format of exported reports. The timeout settings that you specify on the Runtime Settings page are only for Analytics reporting purposes; there is no relationship between these timeout settings and other portal timeout settings.

The following table describes the timeout settings that you can configure.

Table 4-1 Timeout Settings
Setting | Description
--- | ---
Visit Timeout (seconds) | Type the maximum number of seconds that a user must remain inactive during a portal visit in order for Analytics to report subsequent activity as a new portal visit. Analytics reports this data on the Duration console page. The default is 120 seconds.

In the Preferred Locale area of the Runtime Settings page, use the drop-down list to select the locale (language) in which you want Analytics to display report data. The locale that you select determines the object names that Analytics requests from your portal. For example: if you select France - France [fr_FR], Analytics requests the French names—localized for France—of objects from your portal.

The Preferred Locale setting only determines the language of the data in Analytics reports. Individual users must configure their own browser's locale setting to specify their language preference for non-data strings that appear on Analytics console pages. Examples of non-data strings are text in dialog boxes, drop-down lists, buttons, and tabs.

Note: | You must ensure that strings in the preferred locale that you select exist in your portal. If your portal does not return object names in your preferred locale, Analytics performs one of the following:

- If your preferred locale is not country-specific (for example, if your preferred locale is French - [fr]), Analytics requests objects names from your portal using the locale setting of the machine on which Analytics is installed. If your portal does not return object names in this locale, Analytics displays object IDs in reports instead of localized strings.
- If your preferred locale is country-specific—and your portal does not return object names in this locale—Analytics attempts to find strings in the most appropriate locale that is not country-specific. If your preferred locale is not country-specific (for example, if your preferred locale is France - France [fr_FR]) and your portal does not return object names in this locale—Analytics requests object names from French - [fr]. If your portal does not return strings in this locale, Analytics requests object names using the locale setting of the machine on which Analytics is installed. If your portal does not return object names in this locale, Analytics displays object IDs in reports instead of localized strings.

The following table describes the export report settings that you can configure.

Table 4-2 Export Report Settings
Setting | Description
--- | ---
Export Report | Select to export reports in one of the following formats: Excel (10,000 row limit): Exporting to Excel is limited to 10,000 rows. If you choose this option, reports that contain more than 10,000 rows in Analytics will contain only the first 10,000 rows when exported to Excel. TSV: Tab Separated Values is a text-based file format in which exported columns are separated by tabs. TSV files are typically opened by Excel.
Note: | Although TSV reports have no limitation on numbers of rows, exported reports in excess of 10,000 rows will likely take an extended period of time to generate.

### Configuring Partition Settings

This section discusses the configuration of Analytics Administration's Partition Settings page. For guidelines on archiving and restoring partitions in your Analytics database, see Archiving and Restoring Partitions.

Analytics data is segregated into month-by-month partitions in the database. The Partition Settings page lets Portal Administrators specify the number of data partitions that are accessible to Analytics reports. The Analytics Engine regularly scans each data partition that is accessible. For this reason, you can have more control over system performance by limiting the number of accessible partitions to only those that are needed.

At the beginning of each month, the system creates a new partition and stores all new Analytics data in that partition until the month ends.

Note: | You also use the Partition Settings page to refresh database views after archiving or restoring partitions. To do so, click Finish. If you do not refresh the database views, Analytics reports will fail.

#### Working with the Scrolling View Window

The Scrolling View Window, which you configure on the Partition Settings page, is a rolling database view that changes month-to-month. For example, suppose that on August 5, you enable the Scrolling View Window and set its size to 4 months. The following occurs:

The Scrolling View Window makes data from 4 months available: May, June, July, and August. (Note that even though the month of August has not completed, the Scrolling View Window makes data from the August partition available so that the most current data appears in Analytics reports).

On September 1, the Scrolling View Window scrolls one month forward and makes data from the June, July, August, and September partitions accessible. Though the Scrolling View Window removes the May partition from view, the partition and its data is still stored in the database. In this example, if in December of the same year the Portal Administrator wanted to make the data from the May partition available to reports, he or she would increase the Scrolling View Window size to 8 months so that it includes the May to December time frame.

To set the number of months, that are accessible to Analytics reports, first enable the Scrolling View Window, then specify the number of months: between 3 and 60. Data from monthly partitions that do not fall within the Scrolling View Window size is made unavailable to Analytics reports.

Note: | If you do not enable the Scrolling View Window, all data from all partitions is accessible to Analytics reports.

#### Previewing Partitions

At any time, you can click Preview on the Partition Settings page to view a chart that displays a representation of all partitions and indicates whether they are available or unavailable to Analytics reports:

- Green squares indicate partitions whose data is available to Analytics reports.
- Red squares with an X indicate partitions whose data is unavailable to Analytics reports; these partitions do not exist in the database.
- Grey squares indicate partitions for months that do not currently fall within the Scrolling View Window's date range. These partitions may or may not exist in the database.

###