LinkedIn
Copied!

Table of Contents

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

Version:

Only available versions of this content are shown in the dropdown

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:
                  {"dass":[
                  {"pySetting":"DASSValue1","pyPurpose":"DASSName1","pyOwner":"DASS1Owner"}, 
                  {"pySetting":"DASSValue2","pyPurpose":"DASSName2","pyOwner":"DASS2Owner"}]}
                {"dass":[
                    {"pySetting":"200",
                      "pyPurpose":"mobile/search/results/maxRecords",
                      "pyOwner":"Pega-UIEngine"}, 
                    {"pySetting":"true",
                      "pyPurpose":"indexing/notify",
                      "pyOwner":"Pega-RULES"}
                ]}
  2. In the prpcUtils.properties file, specify the file names that you created in step 1.

    Property name Value
    dass.filePath One 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 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.

  4. Save and close the prpcUtils.properties file.

  5. To populate the dynamic system settings, run the prpcUtils.bat or prpcUtils.sh script with the updateDASS option, for example: prpcUtils.bat updateDASS

    1. 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.

Did you find this content helpful?

Have a question? Get answers now.

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