The loading of data for reports occurs on a set schedule, which is determined through each /atg/reporting/datacollection/campaign/*loader component on the data loading server. These components have a scheduler property that points to an instance of /atg/dynamo/service/Scheduler. They also have a runSchedule property that specifies when the loading should start. If you want to change the default schedule, edit the appropriate settings in the loader component.
The following example shows the relevant properties for the CampaignLoader component:
scheduler=/atg/dynamo/service/Scheduler
runSchedule=calendar * * * 21 0
stopSchedule=calendar * * * 6 0
In this case, the runSchedule setting indicates that loading should start at 9 PM every night. The loader checks repeatedly for new work to process until the stopSchedule time is reached (here, 6 AM). For more information on the values in the runSchedule and stopSchedule properties, refer to Configuring a Schedulable Component in the ATG Programming Guide.
Be aware that the loading of campaign data needs to happen before any order- or e-mail-related data is loaded so that the order and e-mail data can be attributed to the correct campaign. By default, the loader components other than CampaignLoader are scheduled to start loading data at 10 PM (one hour after the campaign data is loaded). If you change the schedule on which these activities occur, make sure you maintain this distinction.
Note also that the production database is referenced during the data loading process. For this reason, you should avoid scheduling loading activities to occur during your Web site’s busiest time of day.
