Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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

Updated on May 11, 2022

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.
  1. Configure the common properties of the prpcUtils.properties file.

    Property name Value
    pega.jdbc.driver.jarPath to the database driver .jar file.
    pega.jdbc.driver.classThe database driver class.
    pega.database.typeDatabase vendor type.
    pega.jdbc.urlURL of your database.
    pega.jdbc.usernameDatabase user name.
    pega.jdbc.password Database password.
    rules.schema.nameIf 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.nameIf you use a split schema, the value for the data schema name.

  2. Configure the system name change property of the prpcUtils.properties file.
    Property name Value
    system.newName The new name for your system
  3. Save and close the prpcUtils.properties file.
  4. Run the prpcUtils.bat or prpcUtils.sh script with the changeSystemName option, for example: prpcUtils.bat changeSystemName
  5. Optional: Pass one or more arguments.

    prpcUtils script argument Value
    connPropFileThe full path to the connection.properties file that includes information for multiple targets.
    driverClassYour JDBC driver class. For example, oracle.jdbc.OracleDriver.
    driverJARLocation of your JDBC .jar file.
    dbTypeDatabase vendor type, such as mssql, udb, oracledate, postgres, and db2zos.
    dbURLJDBC URL to the database.
    dbUserDatabase user name.
    dbPasswordDatabase password.
    archivePathFull path to the archive to be imported or exported.
    propFileThe full path to the properties file, to override the default prpcUtils.properties.
    hfixActionIf manageHotfixes is selected, sets the hotfix operation. Valid values are commit, rollback, generateDDL, install, and scan.
    rulesSchemaThe rules schema.
    dataSchemaThe data schema.
    noFailOnErrorSet to true or false. When enabled, instances that fail to import are skipped and import continues instead of failing.
    UPega user name.
    PPega password.
    accessGroupAccessGroup in which the Rule-Declare-Index of the classes being exposed exists. Applicable for the expose utility if --U or --P are not provided.

  • Previous topic Changing the system name from the user interface
  • Next topic Configuring production-level run-time settings

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us