Question
CA
Last activity: 7 Nov 2016 15:21 EST
Sticky session for event strategy tumbling window
Hi
We have developed an application which processes events from various sources like google analytics, MQ etc. These events are mostly transactional data e.g. purchase, debit, credit, account transfer etc. We have a event strategy which listens for duplicate transaction within 10 secs of tumbling window. The source of events are not on Pega server. How do I ensure the sticki-ness of the event based on a custom key e.g. visitorid or account num.
E.g.
Transactions from same customer (visitorID : C1)
T1 : Swipe card at sales terminal.
T2 : Swipe card at sales terminal again.
Current Behaviour :
T1 : LoadBalancer redirects to appserver 1.
T2 : LoadBalancer redirects to appserver 2.
Expected Behaviour :
T1 : LoadBalancer redirects to appserver 1.
T2 : LoadBalancer redirects to appserver 1 (based on visitorID : C1).
How this scenario can be implemented ..?
Pegasystems Inc.
US
Do the options listed in this article help you solve this? https://community.pega.com/sites/default/files/help_v719/procomhelpmain.htm More details are found here as well: https://collaborate.pega.com/question/high-availability-administration-guide