The EventProcessor job further processes events in the -10 state.
Analytics events are sent to an external analytics system and then
updated to the -20 state and non-analytics events
are simply updated to the -20 state. By default,
this scheduled job runs every hour.
About this task
If the Analytics Event Configuration component is enabled, 200 events are fetched and
updated from the process state (by default -10) to the inProcess state (by
default -15). Any qualifying analytics events in this batch (events for store
that are enabled with the correct type, transport, and channel IDs) are transformed. These events
are then sent to the analytics system and then updated to the purge state. Any analytics events in
the batch that do not qualify are updated to the purge state (by default
-20).This process of fetching and processing groups of 200 events repeats
until the maxBatchSize analytics events are processed. If the value of the
maxBatchSize parameter is set to -1, all business events
in the BUSEVENT database table are fetched and processed.
If
the Analytics Event Configuration component is disabled or the stores are disabled, up to 500, 000
business events in the process state (-10) are deleted from the BUSEVENT table
in batches of 5000 events.
1The
scheduler jobs that are used for the ECEvent framework process ECEvents more efficiently. These
scheduler jobs can update and delete rows in the BUSEVENT database table by using multiple
transactions. By using multiple transactions, these commands can update and delete millions of
records over time without encountering transaction timeouts or database locks. Previously, the
default configuration for the Business Event framework causes the rows in the BUSEVENT table to grow
unbounded. Eventually, the site encountered high memory utilization or database locking problems
when the framework commands attempted to operate on many rows.
Procedure
- Open the Administration Console,
and select Site on the Administration Console
Site/Store Selection page.
- From the Configuration menu, click Scheduler.
A list of jobs that are scheduled to run on your store is displayed.
- From the list of jobs, select EventProcessor.
- Update the Schedule interval field
to reflect your preferred interval.
By default, this value
is set to 3600 seconds so that the job runs every hour.
- Click OK.
Results
Your job is listed on the Scheduler Status Display page
and run at the specified start time.
1 The improved functionality is included in the
interim fix for APAR
JR42537. This interim fix allows for the processing of
more than 5000 rows at a time. If the Analytics Event Configuration component is disabled, or the
stores are disabled, up to 500, 000 business events in the process state (
-10)
are deleted from the BUSEVENT table. These events are deleted in batches of 5000 events.
2 When you apply the interim fix for APAR
JR42537 or upgrade to Fix Pack 6 or
later, you can encounter a null pointer exception during an Event Processor scheduled job when an
Event Component is disabled. The interim fix for APAR
JR48930 resolves this
exception.