Stages in the Subsite Template Job
Load Data and Apply Global Rules
The Read Me First note in the job flow contains information
needed for the initial setup and modification of this job. The only
value described in this note is EMAILADDRESS, which supplies the e-mail
address in the Checkpoint transformations in the template. This address
is used for failure notification.
The first
stage of the subsite template process locates the data and applies
global rules to it. For example, you can apply default rules to filter
requests for image files or requests made by spiders and robots that
identify themselves as such in their user agent data. For more information,
see Managing Non-Human Visitor Detection.
Load Data and Apply Global Rules Transformations
|
Parses the data and
applies global rules that apply to all of the subsites; filters out
graphics files, non-pages, and spiders that identify themselves in
their user agent strings. Also see Managing Non-Human Visitor Detection.
|
||
Generate Subsite Sessions
The second stage of the subsite template
process uses a Clickstream Parse transformation to limit the data
to a selected subsite. Then, a Clickstream Sessionize transformation
is used to identify the sessions in that particular subsite. You can
assign a session ID, which effectively identifies the sessions that
are present within the data.
The template
job performs this operation for three distinct subsites: PRD, SVCS,
and GEN. Of course, you do not have to process exactly this set of
subsites. The template is meant to serve only as an example. You can
filter the data for as many or as few subsites as needed. Simply add
or remove sets of transformations to match the number of subsites
that you have. Then, change the names to appropriate values.
Generate Subsite Sessions Transformations and Tables
Generate Data from Site-Wide Data
The third stage of the
subsite template processes the data from the Web log without splitting
it into subsites. This stage enables you to create an output table
that covers all the data in the Web log. Although filters are not
applied in this data, this data can be thought of as a subsite of
everything. For example, the ALL output data might be of interest
to those responsible for the entire company's site, while the PRD
data might be of interest to those in charge of the PRD department's
site.
