Related terms
Use this tab to change the System Name of your Pega 7 system. A Pega 7 'system' in this context is all Pega 7 instances (nodes) that share a single database and the same system name.
When you use this page to change the system name, Pega 7 clones the current system name record, the node name of the other nodes in the system that use the current name, and all associated Data instances that reference this name and applies the new system name.
If your organization has multiple Pega 7 systems, it is a best practice to set a distinct system name for each of the systems. For example, you may want to distinguish between development, test, UAT and production systems. When you create, or update a rule or a data instance, the current system name is added to the History tab. When you import a ZIP archive containing a rule or data instance, the system name is on the History tab (which may be the source system on which the ZIP archive was created).
Using distinct system names can help identify the source systems when rules or data objects are moved from one system to another. To change the system name:
By default, the system name is pega.
Note: The system names prpc and iwm are reserved; do not use except as advised by Global Customer support.
Pega 7 makes an exact copy of the current system name record, the node name of the other nodes in the system that use the current system name and all associated data instances, including requestor type data instances (Data-Admin-Requestor class), the Dynamic System Settings indexing/hostid, and applies the new system name. Pega 7 also updates any listeners with the new Node IDs.
The table All Affected Nodes on the System Name page lists the nodes whose name will be changed by this action.
If the Required Action column for a node is Update prconfig.xml and Restart, you must update the prconfig.xml file entry Identification/SystemName for that node to reference the new name before restarting the node. For example:
<env name="Identification/SystemName" value="mycoProd" />
Complete this step for each node.
When the system starts with the new name, it creates new Agent Schedule instances for each node. Review these new instances and, if necessary, update the access group on the Security tab to match the value in the older Agent Schedule instance.