This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.
Close popover

Changing the system name

The system name, or system ID, identifies a single Pega Platform™ instance and forms part of the name of every element of that system. The system name appears on the History tab of every rule and data form that is created for or within that system. A system can have one node or a cluster of many server nodes.

When you install each instance of Pega, its system has the default name (ID) "pega". It helps the organization of your code assets to specify a separate name or ID for each installed system. Unique system names also help to clarify the history of your code. For example, when a module is created in one system and then imported into another, you can track its development more clearly in the History tabs of the module's rules if those two systems have unique names.

The Autonomic Event Services product (AES) produces reports about system performance by system name. If you have multiple unrelated systems that a single AES installation monitors, you need to provide a unique name for each system. For more information about AES, see About Autonomic Event Services (AES), Enterprise Edition.

The system name is the same for all nodes that belong to that system. Each node also has a unique, system-generated node ID that identifies it and that derives in part from its system ID. Do not manually edit the node IDs.

Procedure

Perform the following steps to rename your system:

  1. ​Click Dev Studio > System > Settings > System Name. The System Name landing page displays the current system name and the list of associated nodes.System Name landing page
  2. In the New Name field, enter a name that meets these requirements:
    • Starts with a letter
    • Contains only letters, digits, or the underscore character
    • Contains no more than 32 characters
  3. Click Submit. The Pega 7 Platform performs the following tasks:
    • 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
  4. Stop and restart all nodes of the system. The new system name takes effect when the system starts up.
  5. Run the System-Status-Nodes.SystemNodeDetails.ALL standard report to view the list of affected node IDs.
  6. Delete the “pega” related Requestor Type instances, System instance, and Agent Schedule instances to keep your applications clean.
Your applications do not reference the objects related to the older system name even if these instances are not deleted.

100% found this useful

Have a question? Get answers now.

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