Siebel Loyalty.Realtime And Batch Engines. Transaction Processing.
Last updated on APRIL 30, 2018
Applies to:Siebel Loyalty Engine - Version 220.127.116.11 SIA and later
Information in this document applies to any platform.
Client has a web service that calls a business service which for a member increments a counter for each transactions processed, the counter (promotion attribute that counts flights) increases correctly and the promotion rule is used to compare current number of flights with some value.
It seems there some time lag between transaction processing and bucket (promotion rule) processing. One possibility is to separate Transactions processes to the Realtime engine and Buckets processes to the Batch engine.
The current setting for the 'eLoyalty Processing Engine - Batch' component parameter 'LOY - Engine Queue Objects' is 'Transaction:500,Bucket:200,Tier:10'.
So, the questions are:
1. Can the performance be improved?
2. If the same parameter 'LOY - Engine Queue Objects' was set to the same value for the eLoyalty Processing Engine - Realtime would it help?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms