When and how to change a system name

When and why to change a system name

You can change the system name at any time; changing it promptly after installation is advisable.

The system name appears on the History tab of each rule form and data form.

If your organization has multiple Process Commander systems, giving each a unique name is helpful, especially when rules or data objects are moved from one system to another.

How to change a system name

To change the system name:

1. Open the current System data instance (usually named pega). Click the New toolbar button (), not Save As.

2. Enter a System Name (also called system ID) that starts with a letter and contains only letters, digits, and the underscore character, no longer than 32 characters.

3. Create additional requestor type data instances (Data-Admin-Requestor class) with the new system name as the first key part. Copy each of the existing requestor type instances using the Save As toolbar tool, changing only the first key part  (When initially installed, each system has 4 requestor types.)

4. Next, update the prconfig.xml file entry Identification/SystemName to reference this name. For example:

<env name="Identification/SystemName" value="mycoProd" />

5. Stop and restart the system (all nodes). The new system name takes effect upon restart.

6. Changing the system name changes the node name of all nodes in the system. When the system starts with the new name, it creates new Agent Schedule instances (Data-Admin-Agent class) for each node. Review these new instances and update, if necessary, the access group (on the Security tab) to match the value in the older Agent Schedule instance.

7. The value of the Dynamic System Settings indexing/hostid is a node ID. If full-text searching is enabled on your system, update this Dynamic System Settings with a new node name. (Changes to Dynamic System Setting values take effect only when you log out, or after an interval, typically 10 minutes.)

8. If full-text search is enabled on your system, use the System Management Application to regenerate indexes.

9. When all other steps of the name change is complete, you can delete the Requestor Type instances, the System instance, and Agent Schedule instances that refer to the old name and old node IDs.

Related PDN articles

See the Pega Developer Network article PRKB-25730 When and how to change the system name.

About the System data instance About Requestor Type data instances

SysAdmin category