Posted: 1 Mar 2016 0:43 EST Last activity: 2 Mar 2016 6:54 EST
How to set system name in env with 2 PRPC sharing DB.
We have 2 PRPC nodes sharing the DB, and I need to rename system name for each node.
Use OOTB System Setting landing to create a new System Name,
Restart the PRPC node
Apply the new Node ID generated from the System Name in the Search Index Host Node Settin
Now, I used to get errors during saving of a new name in the System Setting landing page, if this does not work I will try below
Create the new System Name
Create new Four Requestor Types
Update DASS to use the new System Name
Restart the node
Apply the new Node ID generated from the System Name in the Search Index Host Node Setting
I noted that DASS PRCONFIG/IDENTIFICATION/SYSTEMNAME/DEFAUL for system name in DB is only one row in DB??? If I update the DASS to a new system name one node, and restart, would that confuse the other node, or should I set an entry in PRConfig 'Identification/SystemName' for each node. OR, the purpose PRCONFIG/IDENTIFICATION/SYSTEMNAME/DEFAUL is transcient (only referred to during startup for each node???
One point 1 - I guess I am new to Pega and the concept of 2 nodes or more sharing the DB (is this called Clustered in Paga?). If so, I also think the System Name should be the same for all nodes (with different nodeID) to represent a logical cluster (tell me if I am not having the right understanding here please).
However, the client somehow intend to use one node (701) for a set of applications and another node (702) used for a different application (along with the agents running on different nodes)
Because we have AES set up recently and it is getting alerts/exceptions from both Node701 and Node702. AES uses System Name to differentiate Alerts/Exceptions from from each node. The system name on each node so far are confusing and so we are thinking of give them a proper name like tmcprdpega701 and tmcprdpega702.
Question1: How would AES handles Node(s) cluster if they are having the same system name?, each node has its own logs
Question2: Where can I read up on this Cluster concept (with the system name)
Please share your thoughts on what is the right things to do for the clustered nodes. I also find it is confusing that my client is purposefully asking users to access certain applications on 701 and others applications on 702.
From what I understand you have more than one application on the same Pega database but want different nodes to be used for different applications. Pega considers all nodes connected to the same PegaRULES DB as one cluster. Note that you can multiple installs of Pega in the same DB in different schemas. So all nodes connected to the same schema for rules and code is one cluster and should have the same system name.
AES uses the system name to identify a cluster and co-relates all the alerts and exceptions generated by this. There are reports in AES to filter data by application. Please refer to the reports tab in the AES dashboard. In AES 7.1.7, you can find the reports here
Posted: 5 years ago
Updated: 5 years ago
Posted: 1 Mar 2016 6:35 EST Updated: 1 Mar 2016 7:13 EST
Are you referring to the Short Description of System or System Node. I thought the dropdown list of system on the top right corner is using system name?? where do you change the node description so that I can tell them apart when I pick a system from dropdown list.