ATG C om mer ce P ro g ramm in g Gui d e
25 - P repari n g t o Us e C o mm erce R eport i n g
category information for a given product. You can do this in the
property of the
component. This property is
by default. If the property is
and a product has only a single parent category, that category is
used. If it is null and there is more than one potential parent category, the first category is used, and a
warning is logged.
Logging Data for Commerce Reporting
Data logging takes place in two environments in an ATG Commerce context. Some data comes from your
production environment, including site visits, orders, customer/visitor changes and segment definition
changes. Other data comes from the merchandising environment, including changes to categories,
products, SKUs and promotions.
Data logging components for users, segments, and site visits are located in
. The logging components for orders and the
product catalog are located in
. All loggers have the
following common characteristics:
A listener monitors for one or more event types that signify log-worthy activity in the
listener’s domain. The event is placed on a queue, which notifies its associated logging
component of the event. The type of event that triggers logging differs among the
various types of logged data.
Depending on the log type, filtering may be performed to ensure that only changes of
interest for reporting are logged.
The data logger writes information about the events to a tab-delimited text file. Each
log file has a unique name in the format
The unique ID is generated by the
component. Including the ID in the filename means that even if you configure your
system to send all log files generated by any number of Dynamo instances to a central
location, there is no risk that they will overwrite one another.
All log files consist of one tab-delimited line per entry.
Log files are rotated by the
components, either at a scheduled time or
when a configured limit on the number of log entries is reached. During rotation, the
currently open log file is closed and a new one opened. The logging component fires a
JMS message, which is received by the
, which adds the closed log
file and its type to the queue in the
Note: Rotation occurs only if the current log file contains data.
The sections that follow provide specific information on each logger. Since all loggers are configured in
similar ways, for logger configuration, see the Data Logging Configuration section.