Scheduling the RaiseECEvent job
Procedure
Results
What to do next
- Sends analytics events to an external analytics system and updates the value of the CHECKED column to -20.
- Updates the value of the CHECKED column to -20 for non-analytics events.
false
,
or if no stores are enabled, the analytics component is not used. <component compClassName="com.ibm.commerce.bi.events.AnalyticsComponentConfiguration"
enable="true"
name="Analytics Event Configuration"
>
<property display="false">
<supportedEvents inProcessState="-15"
mapper="mapCommonEvents.xml"
maxBatchSize="200"
maxProcessTime="86400"
processState="-10"
purgeState="-20">
...
<stores>
<store enabled="false" storeId="-1">
<configuration cmClientID=""
password=""
serviceURL="https://wscreceiver.coremetrics.com/Receiver/sendEventData"
sslKeyPassphrase="WebAS"
sslKeyStore="/usr/WebSphere/AppServer/profiles/demo/etc/DummyServerKeyFile.jks"
sslTrustPassphrase="WebAS"
sslTrustStore="/usr/WebSphere/AppServer/profiles/demo/etc/DummyServerTrustFile.jks"
transmitClassName="com.ibm.commerce.bi.events.transmit.CMWebServiceTransmitter"
transmitEnabled="false"
username="" />
</store>
</stores>
</property>
</component>
The CleanECEvent scheduled job deletes business events with a value of -20 in the CHECKED column from the BUSEVENT database table.
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.