In this example, a company called SmallCorp has very limited space in its database and wants to track only the names of the pages that customers visit and the time that the visits occur. In addition, SmallCorp wants to sample this data to save space in its database.
SmallCorp’s database administrator has already set up the database columns that will hold the recorded data. The column names and descriptions are shown below.
Table: Dynamo_Recorder
Column | Description |
|---|---|
| The dataset name that records the data. Different datasets can share the same mapper. It is this dataset identification that allows reports to show actual totals in coordination with sampling. |
| The name of the page that is visited by the customer. |
| The date and time when the page was visited. |
SmallCorp would take the following steps to create the custom recorder:
Create a new Data Collection object of
class=$atg.reporting.dataset.DatasetSQLLogger.Create a new mapper to listen for the Data Collection event.
Create a new dataset to reference the new mapper.
Create a new scenario to record data to this table using this dataset.
SmallCorp can then use the data that the recorder collected in reports. The following sections show how to perform the steps outlined above.
Note: If you plan to add new tables to your database for the data you want to log, perform this step before you create the recorder.
