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

When and how to change the system name

Summary

The system name, or system ID, identifies a single Process Commander system 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 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 Process Commander, its system has the default name (ID) ‘pega’. It helps the organization of your code assets to specify a separate name/ID for each installed system. Unique system names also help clarify the history of your code. For instance, 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 on 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 about AES, see About Autonomic Event Services (AES), Enterprise Edition.

Note: 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. We never manually edit the node IDs.

Suggested Approach

  1. Using the Rules by Type Explorer, navigate to SysAdmin > System (or click the New icon and then select SysAdmin > System). A list of existing system data instances will appear.
  2. To create a new system, click the New toolbar button New button (do not use the Save As option, if it is available).
     
  3. A popup window appears where you can name the new system. Provide a name that
    • starts with a letter
    • contains only letters, digits, and the underscore character
    • is no longer than 32 characters

    In this example, the system name is changed to eDevCo.

  4. Click Create. The System form appears.

    System screen
     
  5. Enter a value in the Production Level field to describe the intended use of this system. The options are
  • 5 = production
  • 4 = preproduction
  • 3 = test
  • 2 = development
  • 1 = experimental

If you are not sure which level is appropriate, enter 1 or 2. For more about production levels, see Production Levels and Access-When Rules.

  1. The License Parameters field of the new instance should match that of the original, so do not change any entry you find in this field.
  2. You can adjust the Short Description in the header, and the Full Description in the History tab. Leave the other fields as you find them. Click Save.
  3. Each system requires at least four Requestor Types: App, Batch, Browser, and Portal. You can copy the existing Requestor Types in the default 'pega' system:
    1. Using the Rules by Type explorer, select SysAdmin > Requestor Type to display the existing Requestor Types.

      Requestor Types
    2. For each of the existing Requestor Types:
      1. Select the Requestor Type.
      2. Click Save As Save As.
      3. Replace the pega system name with the name of the new system, and click Save As. The new Requestor Type is now associated with the new system name.
  4. Edit the prconfig.xml file for this installation, updating the “Identification/SystemName” entry to reference the name of the new system.

    editing prconfig.xml

    For more information, see How to change prconfig.xml settings. Note that in a multi-node system (a cluster) you will need do update the prconfig.xml file for each node.
     
  5. Stop and restart all nodes of the system. The new system name takes effect as the system starts up.
     
  6. Changing the system name automatically changes the node ID of each node in the system. To review the new node IDs, run the standard list view report System-Status-Nodes.SystemNodeDetails.ALL.

    Reviewing nodes
     
  7. When you have completed these steps, you can delete the “pega” related Requestor Type instances, System instance, and Agent Schedule instances to keep your applications clean. However, your applications will not reference the objects related to the older system name even if you leave them in place.
Suggest Edit

33% found this useful

Have a question? Get answers now.

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