Posted: 6 Nov 2015 17:05 EST Last activity: 4 Oct 2018 11:08 EDT
Flush/remove the Declare Page in a multi-node environment
What are the different possible ways to flush/remove the Declare Page in a multi-node environment? We are using V6.2 and we want to flush the page instance from all the nodes in running a single activity/utility with no performance issues created in production server.
I know one way is clicking the "Flush Page" in all production nodes but we have more number of nodes to perform this exercise.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
There is an OOTB function called ExpireDeclarativePage which expires the page for a single node. Here is a quote from SME answering similar question:
There's no formal way to run ExpireDeclarativePage on every node.
Of course, the signal which causes ExpireDeclarativePage could be sent to every node. Or, another idea, perhaps you could build a simple Agent to run ExpireDeclarativePage on every node when it becomes necessary.
What is the business problem you are trying to solve by expiring these pages? Has the data changed? As Kevin suggested, you could create an agent that runs an activity to do that if you have a periodic/predictable time/reason to do this. If this is more of a scenario where something unforeseen happens and you want to flush a dozen nodes simultaneously, you could call the activity via HTTP request and write a shell script to do that. Someone asked about that recently here. https://mesh.pega.com/message/204033#204033 Hopefully that helps.
also, could you please provide your comments on refering to OOTB activity 'FlushDeclarativePage' in class 'Rule-Declare-Pages' called in a Listener rule (maybe a fileListner: executed on need) configured with run on all nodes as start up option makes sense...
May i know what is the feature name in Pega 7 .. currently we are using 7.1.5 and we had a multinode environment in production. when ever required flushing the data page .. i am going each and every individual node .. but it is not good pratice as per Production set up.