LinkedIn
Copied!

Table of Contents

Changing the system name from the user interface

Version:

Only available versions of this content are shown in the dropdown

If you have multiple Pega Platform systems, set a distinct system name for each system. For example, you may want to distinguish between development, test, UAT and production systems. Using distinct system names can also help identify the source when rules or data objects move from one system to another.

The option to change the system name is not available for Pega Cloud deployments.

All Pega Platform instances (nodes) that share a single database share the same system name. By default, the system name is pega.

When you use Dev Studio to change the system name, Pega Platform makes the following changes:

  • Creates all required requestor types: App, Batch, Browser, and Portal
  • Creates a system name rule with the specified name
  • Updates the dynamic system setting
  • Updates the system name that appears on the landing page
  1. In the header of Dev Studio, click Configure System Settings System Name .

  2. Enter a new name that meets the following requirements:

    • Starts with a letter
    • Contains only letters, digits, and the underscore character
    • 32 characters or shorter
    • Do not use the reserved system names prpc and iwm except as advised by Global Customer support.
  3. Click Submit

  4. Restart each node in the system.

    1. For each node in the All Affected Nodes list, review the required action.

    2. If the Required Action column for a node is Update prconfig.xml and Restart, update the prconfig.xml file entry Identification/SystemName for that node to reference the new name before restarting the node.

      <env name="Identification/SystemName" value="mycoProd" />
    3. Restart the node.

When you change the system name, Pega Platform 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. The new system name record is created with all the required data requestors even if the current record that is being renamed does not contain all the data requestors. Pega Platform also updates any listeners with the new node IDs.

Then, 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, which may be the source system on which the .zip archive was created, is on the History tab.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.