Configuring Parameters of the Batch Server Component
You can configure the batch server component by changing the parameters that are used in processing, as described in the following procedure.
To configure parameters for the Loyalty Engine batch server component
Navigate to Administration - Server Configuration, Enterprises, then the Component Definitions view.
Query for the eLoyalty Processing Engine - Batch component.
In the Component Parameters view, specify values for the parameters used in batch processing, which are summarized in the following table. All of the parameters in this table apply only to the Siebel Enterprise eLoyalty Processing Engine - Batch component.
Name Display Name Default Value Description LOYEngineNumberOfRuns
LOY - Engine Number of Runs
5 The number of times to query after the queue becomes empty. This parameter must have the value -1 or greater than 0. If -1, then the eLoyalty engine keeps running indefinitely until it is shut down. Otherwise, it queries the specified number of times after the current query has run out of records. LOYEngineNumberOfTasks
LOY - Engine Number of Tasks
0 The number of processing threads that are automatically started when the Loyalty Engine server component is started. By default, it is 0, which means that there is no processing thread started, but there is one queue manager thread started. If -1, then no queue manager thread can be started either. If 4, then 4 processing threads plus one queue manager thread can be started for each MT server. LOYEngineQueueObjects
LOY - Engine Queue Objects
Transactions:90
Buckets:10
Tier:10
Accrual:10
The objects to process in the queue and the number of objects to place in the queue each time. This information is displayed in the format Object1:n,Object2:m listing each object to process and the number of objects. LOYEngineSearchSpec
LOY - Engine Search Specification
None Currently not supported. Reserved for future use. LOYEngineSleepTime
LOY - Engine Sleep Time (secs.)
10
The time (in seconds) for which the eLoyalty engine must wait after it has processed the records and there are no more records in the next query. After sleeping for that time, the eLoyalty engine can requery.