I am looking for some feedback as I have not seen anything in the PDN reference this.
I would like to leverage the use of WebSpheres ODR and Dynamic clustering. Has anyone here seen, implemented this with PRPC?
Does PEGA support this configuration?
The reason I want to do this, it redundancy, availability, scalability. We have the ability to simply stop a nodeagent which allows all current sessions connected to it to stay connected, but prevents any new connections form connecting.
I will be happy to elaborate more if you have more questions, but at this point I am only looking for pointers to PEGA support or any known issues doing this.
I know there are some pega internal posts regarding if we support WAS dynamic cluster or not. The short answer is no, we have not yet tested the configuration nor do we officially supports it. It would be an enhancement request if needed. Personally (not officially), I have tried that in GCS non-critical environment, the basic stuff appears to be working but my tests were very limited.
I have been searching but have not had much luck finding any documentation for this. I know in PEGA 7.2 I found this, but we are running 7.1.6 and currently do not have any plans on upgrading for a bit as we JUST upgraded from PEGA 5.4.2 to 7.1.6 last month.
The actual topology varies from enterprise to enterprise. Here is the doc you should follow: https://pdn.pega.com/documents/pega-72-high-availability-guide. Now looking at your chart, besides ODR which I am not aware of any successful deployment, you have a redzone firewall between app server and db server. This should be fine as long as both app server and db server are in the same subnet. Otherwise the performance becomes an issue. One thing you absolutely should avoid (I do not think that is your case, but want to bring out for the benefit of the community) is to host app server and db server in two data centers in spite of 'unlimited' bandwidth.