Question

1
Replies
182
Views
Close popover
Nikhil Agarwal (Nikhil_Agarwal)

CA
Nikhil_Agarwal Member since 2015 37 posts
Posted: November 3, 2016
Last activity: November 7, 2016
Closed

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 ..?

Low-Code App Development Decision Management
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.