Close popover
Ryan Taylor (rwtaylor)
Selective Insurance
BPM-Pega Solution Architect
Selective Insurance
rwtaylor Member since 2012 3 posts
Selective Insurance
Posted: September 1, 2016
Last activity: September 29, 2016

Setting different system names in a single env with two Pega nodes sharing DB

Here's the scenario: We are on PRPC 7.1.9 with CSI 7.14 and PegaSurvey 7.1 ML3. The end goal is to email a survey to an external customer to complete. The security team won't allow any external access to core region app servers so, we setup a new VM in the DMZ that shares the Core DB with the main Pega nodes. This was done to allow linking between the Survey work object and the originating work object. 

After exposing all the required ports for hazelcast between DMZ and Core, we've seen library compilation issues and caching issues on the new DMZ VM. Functionality that works find on the Core VMs consistently picks up the wrong rule on the DMZ VM. After some experimentation, we've found that once we run the functionality on the Core VM, it will start working on the DMZ VM as well; presumably because it's now cached properly.

With all the issues, I was thinking it might work better to set the system names for Core and DMZ differently to allow them to work semi-independently while still using the same DB. Based on my research, I can manually specify the system name in the prconfig.xml but in order for it to work properly I'll need to update the prconfig for all the nodes and remove the DSS that's currently setting the name. 

My questions are,

1. Will this change in fact help to resolve the issues? Or is there a better way to do this? 
2. Is that the correct process for separating them out? 


System Administration
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.