Installing hotfixes by using a direct connection to the database
To automate hotfix installation, use the command-line tools by using a direct connection to the database. This is most commonly done for a stopped instance.
- Configure the common properties of 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. - Configure the install properties of the
prpcUtils.propertiesfile.Property name Value hotfix.operationinstallhotfix.dlFilePathThe full path to the hotfix package file. hotfix.bypassSchemaThe default value, false, applies any schema changes automatically. A value oftrueindicates that you have already manually applied the schema changes.hotfix.forceSet only at the request of Pegasystems Global Client Support to skip hotfix validations and force the hotfix data into the system. hotfix.asynctrueorfalse. The default value,true, executes the hotfix operation asynchronously. The system queues the job and returns a JobID to use to get the job status. A value offalseexecutes the operation synchronously. -
Save and close the
prpcUtils.propertiesfile. - Run the
prpcUtils.batorprpcUtils.shscript with the manageHotfixes option, for example:prpcUtils.bat manageHotfixes - 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 Installing hotfixes by submitting a request to an active instance Next topic Rolling back hotfixes