If you have existing order data in a repository and you want to load into the Data Warehouse for reporting, you can use the OrderRepositoryLoader
to do so. This component treats the data in your order repository as if it were a log file and loads it accordingly.
This component uses the same SubmitOrder
pipeline chain as the OrderSubmitLoader
, but is managed by the OrderRepositoryPipelineDriver
component.
To use the OrderRepositoryLoader
, first start the OrderRepositoryPipelineDriver
component. You can either start this component in the ACC, or enter the following browser path to start it in the Dynamo Server Admin:
http://host:port/dyn/admin/nucleus/atg/reporting/datawarehouse/
loaders/OrderRepositoryPipelineDriver
In the Admin UI, go to /atg/reporting/datawarehouse/loaders/OrderRepositoryPipelineDriver
. In the text field, enter an RQL statement corresponding to a query against the order repository. Check the Preview box if you want to see how many records will be retrieved before actually processing the orders.
The OrderRepositoryPipelineDriver
includes the following configurable properties:
skipRecordOnError
—If set totrue
, the component skips any records for which processing results in an error. The default is false.errorDataListener
—Set this property to a component that implements theatg.service.datacollection.DataListener
interface. IfskipRecordOnError
istrue
, the driver notifies this component when an error occurs. The record that produced the error is added to theDataListener
.
When you click Submit, the query is issued against the repository. For each result, the component creates a new pipeline parameter object and sends that object down the pipeline, just as if it were a line item in a log file.
The Dynamo Server Admin keeps a count of how many records have been processed out of the total retrieved.
Note: The following data is not included for orders in the repository, and has the values indicated:
Session ID
—NullSite visit
—UnspecifiedSegmentclusterID
—Unspecified
These fields are not populated in the Data Warehouse when loading existing orders. This may affect the conversion rate as it appears in reports, because that calculation relies on the session ID.