Updating dynamic system settings by using a direct connection to the database
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.
- 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"}]}
- In the
prpcUtils.propertiesfile, 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; - Configure the common properties in the
prpcUtils.propertiesfile.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.passwordDatabase 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. - Save and close the
prpcUtils.propertiesfile. - To populate the dynamic system settings, run the
prpcUtils.batorprpcUtils.shscript with the updateDASS option, for example:prpcUtils.bat updateDASS- Optional: Pass one or more arguments.
prpcUtils script argument Value connPropFileThe full path to the connection.propertiesfile 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, andscan.rulesSchemaThe rules schema. dataSchemaThe data schema. noFailOnErrorSet to trueorfalse. 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