Skip to main content

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

Updating dynamic system settings by using a direct connection to the database

Updated on May 11, 2022

To automate updating dynamic system settings by connecting directly to the database, complete the following steps. This method is most commonly done for a stopped instance.

  1. Create one or more .json files that specify the names and new values of the dynamic system settings.
    • The specified dynamic system setting names must be valid.
    • One or more dynamic system settings can be specified in each file.
    • You must specify the setting value, setting name, and owning ruleset for each dynamic system setting to be updated, in the format:
    For example:
  2. In the file, specify the file names that you created in step 1.

    Property name Value
    dass.filePathOne or more path names that specify the files that specify the dynamic system settings to update, delimited by commas and ending with a semicolon. If the path is a directory, then all .json files in that directory will be processed. For example: C://file1.json,C://dir1//file2.json,C://dir2;
  3. Configure the common properties in the 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.
  4. Save and close the file.
  5. To populate the dynamic system settings, run the prpcUtils.bat or script with the updateDASS option, for example: prpcUtils.bat updateDASS
    1. Optional: Pass one or more arguments.

    prpcUtils script argument Value
    connPropFileThe full path to the 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
    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 Updating dynamic system settings by submitting a request to an active instance
  • Next topic Adding MIME types through dynamic system 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us