Changing the system name by using a direct connection to the database

To automate system name changes, use the command-line tool that uses a direct connection to the database. This is most commonly done for a stopped instance.

The original system name that was set during system installation is specified in the system.name property in the setupDatabase.properties file. Complete the following steps to change the system name in the database.

Configure the common properties of the prpcUtils.properties file.

Property name	Value
`pega.jdbc.driver.jar`	Path to the database driver .jar file.
`pega.jdbc.driver.class`	The database driver class.
`pega.database.type`	Database vendor type.
`pega.jdbc.url`	URL of your database.
`pega.jdbc.username`	Database user name.
`pega.jdbc.password`	Database password.
`rules.schema.name`	If you use a split schema, the value for the rules schema name. If you do not use a split schema, the value for the schema name.
`data.schema.name`	If you use a split schema, the value for the data schema name.

Configure the system name change property of the prpcUtils.properties file.

Property name	Value
`system.newName`	The new name for your system

Save and close the prpcUtils.properties file.
Run the prpcUtils.bat or prpcUtils.sh script with the changeSystemName option, for example: prpcUtils.bat changeSystemName

Optional: Pass one or more arguments.

prpcUtils script argument	Value
`connPropFile`	The full path to the connection.properties file that includes information for multiple targets.
`driverClass`	Your JDBC driver class. For example, oracle.jdbc.OracleDriver.
`driverJAR`	Location of your JDBC .jar file.
`dbType`	Database vendor type, such as mssql, udb, oracledate, postgres, and db2zos.
`dbURL`	JDBC URL to the database.
`dbUser`	Database user name.
`dbPassword`	Database password.
`archivePath`	Full path to the archive to be imported or exported.
`propFile`	The full path to the properties file, to override the default prpcUtils.properties.
`hfixAction`	If manageHotfixes is selected, sets the hotfix operation. Valid values are `commit`, `rollback`, `generateDDL`, `install`, and `scan`.
`rulesSchema`	The rules schema.
`dataSchema`	The data schema.
`noFailOnError`	Set to `true` or `false`. When enabled, instances that fail to import are skipped and import continues instead of failing.
`U`	Pega user name.
`P`	Pega password.
`accessGroup`	AccessGroup in which the Rule-Declare-Index of the classes being exposed exists. Applicable for the expose utility if --U or --P are not provided.