What will be happened before and after passivation expiration?
I have a question about Passivation's life cycle. By default, Passivation occurs when the operator has not operated for 30 minutes. The passivated data is used to restore the operator’s clipboard data when the operator resumes operation. You can check the passivated data using SMA, but these data is set with 24-hour expiration time. The question is what happens before and after this passivation expires.
I attempted a simple experiment, but when I resumed the screen operation after the expiration date of passivation(after 24hours passed when passivation occurred), I could do the operation without problems.
And the passivation record was removed on SMA just after the resume. I guess passivation data still existed on server’s disk at that time so that my access could find passivation data and could resume it without any problems.
When and by what will the passivated data removed after its expiration?
What will happen operator resume after passivated data removed?
Note: in this situation there is no authentication timeout for the operator.
***Updated by moderator: Lochan to update platform capability***
Passivation is a process to maintain the user state as it even he is away for sometime. This sometime is 24 hr by default. However, this 24 hr is not exact 24 hr. It depends on the cleaner agent schedule to run on that node.
Let say if the user leaves the session and go for a break. There is a requestor timeout of 30 mins. So, after 30 mins, the passivation will happen. This will create a folder for that requestor in the pega temp directory for that node.
Now, if the user comes back after 5 hr (say) , as the requestor hash is same, it will search for that operator in the passivation folder and reload all its clipboard.
There is a system cleaner agent (node cleaner) scheduled to run everyday at 00.00 hrs. This will check if the passivated folder created is 24 hr old or not. If yes, then it will delete that folder.
Posted: 4 years ago
Posted: 9 Jul 2018 8:43 EDT
RajeshKumar Yadav (RajeshKumarY6297)
Thank you for your helpful comments!
Now I can understand. I was a little confused because i could restart my session after a passivated data expires on SMA.
As my understanding, Schedule of "Node Cleaner" or "ClusterAndDBCleaner"(in HA mode) decides the "Activation" available or not.
And if there is no passivated data on the server while browser's cookie is remaining,
an operator's resume triggers login request(because there is no Requestor ID both in Passivation Management and Requestor Management).