To log order data, the CommerceOrderSubmitPipeline emits a SubmitOrder event. The event is received by the /atg/reporting/datacollection/commerce/OrderLogEntryQueueSink and forwarded on to the /atg/reporting/datacollection/commerce/OrderFileLogger component.
There is one log entry per order. The logging file is named order_timestamp_unique ID.data, and it includes the following:
Timestamp
Profile ID of the user who placed the order
Order ID
Set of segments the user was in when the
OrderSubmitmessage was firedThis means those segments for which both of the following apply:
The user is a member of the segment
The segment is part of the
CommerceReportingsegment list
If the logger encounters a null value, it writes the empty string to the log file. If you prefer the logger to write the string null instead, set the skipNullOjbect property of the OrderFileLogger component to false.
The following is an example of the order log:
12/04/2006 16:39:42o100041100025E47ED51379664EBA2077AEFCDC0F90D
UserProfiles:ValueShoppers
